My style of exploratory testing

Hello all. I would like to share how I am doing exploratory testing so that if you find it useful, you can take this as an idea to practice exploratory testing.

During grooming meetings and acceptance criteria discussions, I will prepare some questions before the meeting and ask them during the meetings. Also, I will identify the potential risks and highlight those during the meetings. On the fly, I will note down the test ideas for the corresponding user story.

Once I started testing a user story, I am taking acceptance tests defined for the user story and the test ideas noted during the meetings as a starting point. When I started from there, I timebox my testing work and note down the questions and test ideas that I get during a test session. I perform timebox sessions for a maximum of one hour.

I will pause the test session, review my notes and look at those questions and test ideas. I will start my further testing sessions with those questions and test ideas. Once I didn’t get any test ideas and questions, I will stop my testing. Sometimes I use the Heuristics Test Strategy model as a resource for triggering test ideas and for finding bugs in the software.

Each testing session, I will note down the bugs found and collectively I report those bugs to developers. Like this, I am practising exploratory testing. Hope you find my short article useful. If you have any interesting ways to practice exploratory testing, don’t hesitate to share them with me. In future, there will be a series of articles regarding examples for practising exploratory testing.


Discover more from Bj Testing Talks

Subscribe to get the latest posts sent to your email.


Leave a comment