Industrial Strength Exploratory Testing – part 4

Continuing from the previous post, here is our last myth: Myth 3: Bugs found through exploratory testing are hard to reproduce Testers have to remember exactly what steps they did and note it down in detail when they find a defect. The stated problem is that with no pre-scripted steps in exploratory testing, the onus…

1

Industrial Strength Exploratory Testing – part 3

Let’s pick up mythbusting from where we left off Myth 2: There is no way to measure exploratory testing I have heard this often from test managers – “how do we measure testers’ productivity in exploratory testing?” Scripted testing allows for measuring rate of tests executed per hour, test pass progress percentage etc. but how…

5

Industrial Strength Exploratory Testing – part 2

In the last part, I introduced exploratory testing and looked at some advantages of employing exploratory testing. In this part, let’s look at a few myths surrounding exploratory testing and try to debunk some of these. Myth 1: “Exploratory testing is ad-hoc, monkey testing” Exploratory testing is NOT random, undirected testing. On the contrary, unlike…

2

Exploratory testing – introduction

I have been meaning to put together a series of blog posts on exploratory testing – how exploratory testing can help make your testing more lightweight, illustrate some of our own experiments with doing exploratory testing on my team and of course, write about the exploratory testing tools we are building in Visual Studio as…

2

Exploratory testing with Visual Studio Test Pro

Exploratory testing(ET) as defined by Bach is simultaneous learning, test design and execution. It is a scientific style of testing that is very effective at finding defects early and fast. Yet, we don’t have specific test tools that support testers doing ET. Most test tools focus on scripted testing and test design. This post describes…

3