Please enable JavaScript.
Coggle requires JavaScript to display documents.
Test Automation Business Case - Coggle Diagram
Test Automation Business Case
Benefits
Increase the release and deployment frequency: Deliver SW to clients faster:
How
Quantification
Key Assumptions
Categorise: new products, products enhancements, new features, changes, fixes??
Better quality of WL SW
How
Testing coverage % is increased
As testing is "at no cost" and immediate, SW is tested more times throughout the development lifecycle
Key assumptions
Avg increase of testing coverage per type of sw delivery (project, change....)
Quantification
Less number of incidents in production
Investments
Automation of manual test cases
Training
Tooling
Manual debt
Recurring costs
Maintenance costs
How will test automation evolve?
Types of tests in scope
External benchmarks
Look for CI devops research: Mr Coppus and Pim
Approach
We need an excel sheet with key assumptions, calculations and scenarios
AS IS and forecast
Number of test cases per test ypes
Expected evolution of new number of test cases per test types in the next X years
Penetrateion of test automation per test type in the next years
What is the relationship between test automation and release frequency? How they will both evolve?
Overall assumptions/raw data
Should we assume that test automation will not free-up capacity as all this extra capacity will be reinvested to test more and better?
AS IS: Test coverage %
Major releaess, minor releases and patches per application per year
Cost of fixing an incident in production
Number of incidents per application per year
Number of incidents found in test in the as is and in the to be, take into account the coverage increase
How do we quantify the additional releases per year in terms of extra revenue?