Why the f**k that we still write test cases manually? I haven’t heard of the single person at work that loves read them or review them. I know it’s essential to test software, but how useful to write test cases?
So, let’s look at all the key stakeholders when developing software:
Product Manager – How often they review the test cases in details?
They don’t care as long as they know their requirements have tests coverage.
Project Manager – They don’t care, as long as you tell them when testing completes.
Developers – They don’t care, genuinely don’t care.
QA – Only yourself care about your own cases, but you don’t read them yourself anyway because you already know how to run those cases right off your head.
Developers/Managers – They don’t care, they probably don’t know if there is a test management system existed anyway
QA Leads/Managers – They might review them (sometimes). But often, they don’t care as long as they know there are test coverage
The only time people will ask for test cases in details is when something break in production, people (
Now, let’s plug in some numbers, assuming QA spends ~15% write new test cases, and modify existing test cases, (6 hours per week, 312 hours per year) spends ~20% automating test cases, (8 hours per week, 416 hours per year) and production major issues happen ~5% of time (assuming 20 releases per year).
And assuming the cost:
- Writing test case per hour cost: $15
- Writing automation test case per hour cost: $45
The saving of not writing test cases:
- $4680 saved from writing test cases, OR
- We can add 104 hours of automation time, AND
- by adding 104 hours to automation (25% increase), which will now lower the percentage that major production issues happen to 3.75%
I will take this saving anytime. So, why we still f**king write test cases?
(To be continue…)
This is very true and love your cost calculation!