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
Saturday, July 4, 2009
Regression Test Automation Software
The Test automation software may be falls into a number categories, such as code analysis, regression testing, and load testing software. The software is used for Windows based applications and mainly used to do Unit Testing, Regression Testing, Functional Testing and System Testing.
The Regression test software requires an understanding of the Windows GUI interface composed of Text and Objects. Modern tools consists of essential components and associated
automated testing methodologies. As the development technologies have evolved so have automated test tools.
The development environment, test requirements, test methodologies and skill level should be the basis for selecting a particular product.
The Regression test software requires an understanding of the Windows GUI interface composed of Text and Objects. Modern tools consists of essential components and associated
automated testing methodologies. As the development technologies have evolved so have automated test tools.
The development environment, test requirements, test methodologies and skill level should be the basis for selecting a particular product.
Uses of Regression Tesing
Software Regression testing is used not only for testing the correctness of a program, but it is also used for tracking the quality of its output.
For example, in the design of a compiler, the regression testing should track the code size, simulation time and time of the test suite cases.
For example, in the design of a compiler, the regression testing should track the code size, simulation time and time of the test suite cases.
Saturday, June 27, 2009
Regression testing
Regression testing
After a defect has been identified and fixed, the software should be retested to make sure that the original defect has been successfully removed. This is called as confirmation. Debugging is a program oriented development activity, not a testing activity.
The Software Regression testing is the repeated testing of an already tested program, after modification, to discover any defects introduced or uncovered as a result of the change(s). The defects may be either in the software being tested, or in other related or unrelated software component.
Regression testing will be performed when the software, or its environment, is changed. The extent of software regression testing is based on the risk of not finding defects in software that was working previously.
Tests should be done repeatable if they are to be used for confirmation testing and to assist regression testing.
The software Regression testing can be performed at all test levels, and applies to functional, non-functional and structural testing.The software Regression test suites are run many times and generally evolve slowly, so regression testing is a strong candidate for automation.
After a defect has been identified and fixed, the software should be retested to make sure that the original defect has been successfully removed. This is called as confirmation. Debugging is a program oriented development activity, not a testing activity.
The Software Regression testing is the repeated testing of an already tested program, after modification, to discover any defects introduced or uncovered as a result of the change(s). The defects may be either in the software being tested, or in other related or unrelated software component.
Regression testing will be performed when the software, or its environment, is changed. The extent of software regression testing is based on the risk of not finding defects in software that was working previously.
Tests should be done repeatable if they are to be used for confirmation testing and to assist regression testing.
The software Regression testing can be performed at all test levels, and applies to functional, non-functional and structural testing.The software Regression test suites are run many times and generally evolve slowly, so regression testing is a strong candidate for automation.
Subscribe to:
Posts (Atom)