How to Prioritize What to Test

It can be intimidating for inexperienced software development teams embarking on their test automation journey for an existing code base. There is so much to test, and so many ways to test. You can often see teams stuck with debating on where to start software testing and what tools to use and best practices:
WWe should start from unit tests”
“No, integration tests are better!”
“Should we use tool A or tool B?”

I see this play out all the time, and I’ve been there before. And the worst that could happen is decision paralysis and inaction. The bigger question really is “What to test?” My rule of thumb is “”Start with the scariest code””. I’ll share with you my framework for evaluating the ROI of writing a test for a feature and prioritizing what to test.

Video producer: