How can you show impact for leading testing initiatives?
There are many directions you can take testing, but just want to understand how to frame the right mindset of "proving" impact for a concept where success is that you prevented or saved risk from the company (no one will know about it essentially if you do your job well).
![Senior Software Engineer [E5] at Meta company logo](/_next/image/?url=https%3A%2F%2Ffirebasestorage.googleapis.com%2Fv0%2Fb%2Ftech-career-growth.appspot.com%2Fo%2Fcompany_logos%252Fmeta.jpeg%3Falt%3Dmedia%26token%3Da7a5bcc0-e178-4b5b-b71e-09bf6c6aefae&w=48&q=75){kind=small}
![Entry-Level Software Engineer [L3] at Google company logo](/_next/image/?url=https%3A%2F%2Ffirebasestorage.googleapis.com%2Fv0%2Fb%2Ftech-career-growth.appspot.com%2Fo%2Fcompany_logos%252Fgoogle.jpeg%3Falt%3Dmedia%26token%3D780356ef-3efc-4728-9eb4-d909b75bb4a6&w=48&q=75){kind=small}
Discussion
(2 comments)- 1
6 months agoTech Lead @ Robinhood, Meta, Course HeroYou have nailed the difficulty behind measuring the impact of automated testing. That being said, it's definitely measurable (just hard to do so):
- Number of regressions prevented
- Severity of regressions prevented
- Overall bug load movement (look at oncall/SEVs too)
#1 and #2 require manual labeling unfortunately.
You can go into a lot more depth here: "What do mobile testing strategies look like at top tech companies?"
- 06 months agoEng @ Taro
If you are building out a new testing initiative, it's helpful to gather all of the previous incidents to show that your new initiative could have helped to prevent ~60% of the previous issues.
Moving forward, it's helpful to get a benchmark for how many incidents and their severity before your testing initiative. Then, you can track to see whether the number of incidents and their severity have gone down.
