Feed
Discussion
How to make the ROI case for test automation to your board
tldr: Boards don't buy test coverage. They buy fewer incidents and faster releases at a known price. The model below gets you there in four steps, with every number's arithmetic shown. The question
Responses
Markdown supported · ⌘↵ to post
Most QA pitches answer none of these. They lead with coverage percentages and test counts, which are engineering metrics, and test count in particular is a metric that rewards waste. The pitch that works prices the status quo first. Everything below uses one worked example, a 12-engineer team at a fully loaded $75 an hour, so you can swap in your own numbers line by line.
Couldn't agree more!
Priya Sharma
Backend dev obsessed with distributed systems
Going to share this with the team. 😁