Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control, and test reporting functions.
Why Automate Testing?
Manual Testing costs too much, takes too much time, does not help them build the product.
Can we do without automation? Yes, of course—if time is abundant and your client (or boss) is NOT on your tail for the application's next release.
Automated testing IS NOT a total replacement for manual testing.
To Automate or Not to Automate.
- Pick a good time to start automating.
- Not all testing approaches are suitable to automate.
- Suitable: Acceptance, Compatibility, Load, Volume or Capacity, Performance and Reliability, Structural testing, Regression, Exception or Negative testing.
- Not suitable: Installation and setup, Configuration and Compatibility, Documentation and help, Error handling and Recovery, Localization, Usability, and any other that relies heavily on human judgment.
- Make automation only a supplement to a testing project.
- Do some comparison of Automated vs. Manual Testing.
How Much Does it Cost?
The total cost needs to consider the costs of numerous resources undertaking a testing project.
Person hours to test
Bugs found by the customers are much more expensive than if the same bugs are found during development.
Rex Black's cost of testing—no testing, manual testing and automated testing.
Automation gives the client higher return on investment (ROI) than manual testing, while no testing at all brings no benefit in the long haul.
No comments:
Post a Comment