Exploratory Testing

When we find a bug in a system we have to make sure we can isolate it and also reduce the risk that our approach caused the bug, rather than the system having a bug.

TLDR: simple click bots from the JavaScript console can make social media and other sites easier to use

I have been using click from the JavaScript console more to: fill in forms, remove ads, remove popups, etc. In this post I explain the general principles.

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.

TLDR; Do you practice your testing? One way involves picking a random game and exploiting it.

A retrospective of an Exploratory Testing Session with detailed notes and critiques.

TLDR; Because we don’t see many videos showing exploratory testing in action, where people test, and explain why they are testing. I created an up to date video. I encourage you to critique the testing.

Lessons learned from Black Ops Testing - Testing a JavaScript library

On the Black Ops Testing Webinar of 11th May 2015 we tested QA Mail. You can find a write up and watch the webinar replay over on blackopstesting

In this post, I’ll discuss the ‘actual testing’ that I performed on Taskwarrior, and why I think I performed it the way I did. At the end of the post I have summarised some ‘principles’ that I have drawn from my notes.

For the Black Ops Testing Webinar on 22nd September 2014 we were testing Taskwarrior, a CLI application.