Link to the Show / Show Notes
Today we're very fortunate to be joined by exploratory testing guru James Bach. He's an accomplished QA expert, who trains and consults through his companySatisfice. He's also one of the authors ofLessons Learned in Software Testing: A Context-Driven Approach. As you might guess, Wolfgang and James talk about exploratory testing.
Today's session runs a little bit long at 25 minutes, but we're sure you'll find it interesting enough to stick with it. This is also our first phone interview. We were a little concerned about audio quality issues, but it turned out pretty well.
Here are a few quotes from today's conversation:
"This idea that 'why don't we just figure out all the tests, and then we'll write them down and then we'll do all those tests' is a formula for bad or at best mediocre testing."
"Testing textbooks seem to have very little say about how test projects really do work or really can work. I saw a lot of folklore and mythology but when I tried to use them, I found that it didn't work on the commercial software projects that I wasn't part of."
"Exploratory testing is simply what happens when I place something in front of you and say 'test this right now'. When people respond to that, they're doing exploratory testing. It's simultaneous learning, test design and test execution."
Links for this conversation's topic:
Technorati Tags:jamesbach,qa,podcast,software,qualityassurance,programming,exploratorytesting
RSS Feed
