Tomte has asked for the wisdom of the Perl Monks concerning the following question:
I find myself in the uncomforting situation of being responsible for an angry customer, because a colleague updated a webapp without checking it's functionality, as part of a complete site-update.
I'm responsible, because I commited changes that broke the app (the last step in a whole bunch of steps didn't work anymore).
I thought about using webchat to do the automation, as it seems the only viable framework for such things except for 'roling my own'.
What is your experience with this module? It seems to be unmaintained, as there's not a change in well over a year; in most cases, this didn't matter, but you never know
Is it useful/feasible to test complex webapps with this tool?
What do you use? Someone with a kick in the right direction?
regards,
tomte
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: WebApplication test-automation
by adrianh (Chancellor) on Feb 18, 2003 at 09:36 UTC | |
by tomhukins (Curate) on Feb 18, 2003 at 14:37 UTC | |
by Tomte (Priest) on Feb 18, 2003 at 09:41 UTC | |
Re: WebApplication test-automation
by knowmad (Monk) on Feb 18, 2003 at 14:00 UTC | |
Re: WebApplication test-automation
by Corion (Patriarch) on Feb 18, 2003 at 14:33 UTC |