A situation many testers can relate to: you land in the middle of an ongoing project. There are some tests made by a previous tester, but how good are they? How do you evaluate the value of an inherited testset? How do you see if you are missing something or if you are overtesting things? How to choose what to automate? What to put in a regression testset? What to test first when under time pressure?
Next to that, in the current way of working with Agile and DevOps you are often the only tester in the team, so it’s up to you to create a test strategy. To show the value of testing and all the considerations you take into account when building your test set and test strategy.
In this talk I will present the simple steps of the OSRS (Overview-Score-Reflect-Strategy) heuristic designed specifically to help with all the above questions. With these steps you can look back and evaluate what you have, but you will also look forward, building a test strategy for future changes. I also invite you to take your whole team along in each of the steps, because quality is a team effort, but you can be firmly in the lead!