When to automate?
A test automation program should be considered when key program factors indicate the overall development program is not meeting expectations and there are no cost-effective alternatives to test automation. The key indicators from a program objective would be:
- Quality objectives are not being met
- Defect escape velocity into production is deemed unacceptable.
- Target deployment velocity is not being met because testing is perceived as a bottleneck
- Testing is not being completed within the assigned timeframe
These factors are often experienced by the project team at the same time -- basically the test group has reached its testing capacity. When this happens, the leadership team has two alternatives: grow the manual testing team or launch a test automation proof-of-concept (POC) to determine if automation can address the testing deficit.It should be noted that testing is often not the “true” bottleneck, but as long as it is perceived as the bottleneck other systemic quality issues will not be addressed. Test automation is one way to remove the perception of a testing bottleneck empowering the testing team while allowing the program to focus on other systemic quality issues -- for example the initial quality of the code.
How to implement a test?
No comments:
Post a Comment