Friday, 6 December 2013

Rules for automation


Test automation is increasing in popularity over the years because of increasing competition and less time and money to invest on large teams to make sure that application work as they are expected. But, automation can only be fruitful for quality and expected behaviour if they have been implemented in the right way. Below the rules we can apply to any form of automation testing but need to be adhered to especially when creating automation scripts for UI automation: 

Ø  Tests should always have a known starting point. In the context of Web UI automation, this could mean launching browser with a certain page to start.

Ø  Tests should not have to rely on any other tests to run. If a test is adding something, do not have a test to delete it. This is to ensure that if something goes wrong in one test case, it will not mean you to have lot of unnecessary failures to check.

Ø  Tests should only test one thing at a time.

Ø  Tests should clean up after themselves.

No comments:

Post a Comment