Automated GUI Testing - Add the missing link

ClosingTheAutomatedTestingLoopWithAutomatedGuiTesting

Can GUI testing be reduced? Yes.

Can GUI testing be eliminated? No.

There are 2 areas where GUI testings are needed:
1. Customer acceptance
By automate them, we can bring the acceptance team and development team closer.

2. Older systems where acceptance testing procedures are the only thing we have.
Automated, at least get one feedback mechanism for the refactoring to start.

GUI testing require special tools and skills.

How do we close the final missing link in the automated testing?

What patterns we can use to reduce GUI testing?

Can GUI testing be provided as a service?



The original document is available at http://sdtconf.com/wiki/tiki-index.php?page=ClosingTheAutomatedTestingLoopWithAutomatedGuiTesting

Show php error messages