The GUI-level regression automation testing is the most common approach to test automation, but it is not the only one and it has serious limitations.
The GUI-level regression automation is not automated testing. It will not automate very much of the testing process at all. The following are the some of the tasks,which shows who does them:
* Analyzing the specification and other docs for ambiguity or other indicators of potential error - Done by humans
* Analyzing the source code for errors - Humans
* Design test cases - Humans
* Create test data - Humans
* Run the tests the first time - Humans
* Evaluate the first result - Humans
* Report a bug from the first run - Humans
* Debug the tests - Humans
* Save the code - Humans
* Save the results - Humans
* Document the tests - Humans
* Build a traceability matrix (tracing test cases back to specs or requirements) - Done by humans or by another tool (not the GUI tool)
* Select the test cases to be run - Humans
* Run the tests - The Tool does it
* Record the results - The Tool does it
* Evaluate the results - The Tool does it, but if there’s an apparent failure, a human re-evaluates the test results.
* Measuring the results for example performance measures - Done by humans or by another tool.
* Report errors - Humans
* Update and debug the tests - Humans
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment