What are the test cases for elevators
5 steps to estimating the cost of test automation projects
- Division of the test cases into complexity classes "simple" / "medium" / "complex"
- Automate two sample test cases of each complexity class
- Determination of minimum and maximum times for each complexity class
- Extrapolation of the determined times to all test cases for the best-case and worst-case
- Add a surcharge for additional effort factors (coordination, setup, debugging, etc.)
In the end, you get a good estimate of the effort. For the automation, the test cases are prioritized and implemented according to this priority. Here is an example:
Step 1: Divide the test cases to be automated into complexity classes
Let's assume we have 300 test cases in the test plan that we want to automate:
|Easy||no special controls, no special setup / teardown functions, just a few steps||120|
|medium||Setup / teardown necessary, many steps, but easy to automate with tools||100|
|Heavy||Complex processes, a lot of steps, automation very expensive||80|
This classification of the test cases requires a lot of experience. Step 2: Automate two sample test cases of each complexity class
Two test cases are automated from each complexity class and the time required is measured:
|category||Test case 1||Test case 2|
|28 minutes||14 minutes|
|medium||58 minutes||42 minutes|
|Heavy||110 minutes||164 minutes|
In addition, insights such as the following result from the implementation:
- For complex test cases, a lot of discussion is needed to clarify the test steps.
- Image-based testing has to be used again and again.
- Automation is entirely possible with the NNN tool.
- SQL scripts are usually sufficient for setup / teardown.
These findings are taken into account in step 5 when calculating the markup.
Step 3: Define minimum and maximum times for each complexity class
|15 minutes||30 minutes|
|medium||30 minutes||60 minutes|
Step 4: extrapolation of the effort for the automation of all test cases
|15 x 120 = 1,800 minutes (30 h)||30 x 120 = 3,600 minutes (60 h)|
|medium||30 x 100 = 3,000 minutes (50 h)||60 x 100 = 6,000 minutes (100 h)|
|Heavy||100 x 80 = 8,000 minutes (133 h)|
200 x 80 = 16,000 minutes (266 h)
|total||12,800 minutes (213 h)||26,600 minutes (426 h)|
Step 5: Add a surcharge for additional effort factors
However, the above costs are only the net programming costs for the test cases. There are also other activities depending on the project and your process:
- Clarification of unclear test case descriptions
- Coordination and coordination
- Deployment of the test cases to the test infrastructure
- For longer projects: ongoing adjustments of already automated test cases to the progress of the ongoing product development
- Technical difficulties
For these factors you should calculate a 25-75% surcharge depending on the project situation. In our case we calculate with 40%:
|programming||213 h||426 h|
|+ Surcharge (40%)||+85 h||+170 h|
|= Sum||= 298 h (approx. 37 days)||= 596 h (approx. 74 days)|
Overall, this results in an effort between 37 and 74 man-days for the automation of the 300 defined test cases. Experience shows that the final value is closer to the upper limit than the minimum.
The procedure shown here assumes that
- the test cases are already defined.
- the test environment is available and stable.
- all contact persons have sufficient time.
- the test automakers are familiar with the automation tools.
If this is not the case, a higher surcharge must be taken into account in step 5.
Test automation is software development. The effort involved in such projects can be correspondingly large. In order to assess these, careful and structured methods are necessary. It is best to start with a small proof of concept and calculate the total effort from the results, taking into account surcharges for coordination, changes and project risk. This way you can avoid surprises and get the maximum benefit from the automation of your test cases!
- Do we really NEED Business English
- Why should you be afraid of anything?
- What income is considered bad in Seattle?
- What is sentence diagram
- Why does Toyota make such terrible cars
- What is a SEBS polymer
- How can I stop being submissive?
- What is a monthly credit card statement
- What's your most common excuse
- Why did Twitter add direct messages
- Which elements connections form the black holes
- Election campaign management system
- How does meditation affect sleep?
- Where can I find resume advice
- What can traditional religions learn from startups?
- What is the anti-corruption law
- Can a woman abuse a child
- Which is better Capegemini or HCL
- Technological development wars begins
- Pink Floyd is a good band
- What is the energy of a seesaw
- What are the ingredients of Cerelac
- Why don't the remnants blame themselves for Brexit
- Chemistry came from alchemy