5 Rules for Successful Test Automation

Page 1

5 Rules for Successful Test Automation Utilize test automation to take the development endeavour where humans cannot go, and enhance the testing of good testers. Regardless of the area's history, some CIOs and supervisors anticipate test automation to fully automate all merchandise testing, magically produce 100 percent code coverage and capture all bugs. And of course, a secret belief that they can fire all of the talented people and hire a chimp. 1. Automation reflects a process; it does not replace it Don't confuse test automation with vendor tools. However good they are -- and we really do like to think that Functioned illustrates the greatest possible options! -- Any tool can only assist you to improve a procedure. Or consider carpentry: Power tools aid a carpenter build a house quicker than with hand gear, but she does not simply sit back and watch the tools construct the home by themselves. Rather, approach test automation as a means to test software for conformance to the QA criteria by which you assess applications as ready to discharge. The tools enable you to submit input, catch output, and compare it against a baseline. To put it differently, test automation tools only automate a procedure you (we hope) have set up. That is the danger and the chance. Automating a good process demonstrates how good that process is. 2. It is another development endeavour Treat the test-automation project like any other development project. That means putting together specifications on what it will and won't do, how the code/modules are designed, and so on. The automation needs to be planned, controlled, tracked, and supported just like a real application development endeavour.


Turn static files into dynamic content formats.

Create a flipbook
Issuu converts static files into: digital portfolios, online yearbooks, online catalogs, digital photo albums and more. Sign up and create your flipbook.
5 Rules for Successful Test Automation by Serena Gray - Issuu