Observation vs Interrogation

5 minute read - Exploratory Testing

TLDR; Observation in real time. Interrogation after the act. Bringing Interrogation closer to Observation can help detect issues during a process. The depth of Observation and Interrogation changes depending on our knowledge of the system and technology. And we may not be done, if our observation was limited.

When I test I make a distinction between Observation and Interrogation and I’m going to explain what that means, and show you hands on example of how that distinction helps me improve my testing and the scope of of my testing.


What does it take to find bugs?

7 minute read - Exploratory Testing

TLDR; Testing uses models to target the system, and our information is constrained by the models we use and build. We can introduce variation to increase the possibility of finding information related to bugs. We have to take care not to develop false confidence.


Example of modelling an application flow as a diagram for Software Testing

7 minute read - Exploratory Testing Modelling

TLDR; An example of modelling the application flow of a simple functionality. Modelling helps think through coverage and test ideas and think about what next for your testing.

I chose the very simple I Feel Lucky functionality on Google to use as an example application for modelling to support exploratory testing. I recorded the modelling session and explained my thought processes as I went.


Exploratory Testing Clean Recon Live Example

2 minute read - Exploratory Testing

TLDR: clean recon - using the app to provide knowledge about the app

Using The Pulper v 1.2 I recorded a live recon session to try and create an example of note taking, model building, risk identification and next action identification.

You can repeat the exercise for yourself and see how you get on.