In the last post, we elaborated on fifteen brainstorming test idea challenges using this excellent paper: Bug Taxonomies: Use Them to Generate Better Tests [Vijayaraghavan, Kaner]. In today’s post, we will brainstorm test ideas without any taxonomy on a real example, and then we will analyze the session reports using SF DEPOT software testing taxonomy. Many thanks to Marcel, who sublimed this great resource on his blog, That’s the buffet table.
The application under test is Sentry. Sentry’s application monitoring platform helps every developer diagnose, fix, and optimize their code’s performance. The product area is the Issues feature. This is the Sentry core part where users could analyze application errors in great detail.
Session Without Testing Taxonomy
This is our first charter:
Charter duration is 15 seconds. I am a tester with 17 years of software testing experiencw. Since 2014 I have all three AST BBST Course Certificates. Along with that, I am an AST BBST instructor. And I am going to miss a lot of test ideas without using a taxonomy 🙂
This is my report with ideas that I managed to create in fifteen minutes without any software testing taxonomy:
SF DEPOT Testing Taxonomy
Let’s analyze this session, using SF DEPOT software testing taxonomy. Here is a mind map that explains SF DEPOT:
In my fifteen-minute session, my testing ideas heat map was concentrated on the Business Functions part. This is 1/46% of testing ideas that we would get by just following SF DEPOT taxonomy.
If you think that you are stuck with test ideas, just Google test idea taxonomies and map them to the context of your project.