exploratory testing
3 Reasons Exploratory Testing Is Great for Agile Teams Specification-based testing is critical for determining whether a user story is “done done.” But that doesn’t ensure a positive user experience. Coherence, comprehension, and usability are beyond the scope of automated functional testing. Here are three reasons agile teams should embrace exploratory testing. |
||
Finding a Middle Ground between Exploratory Testing and Total Automation The automator wants to get rid of human exploration—they want a robot to cut down a forest and stack the wood. The explorer, on the other hand, sees tools more like a chainsaw—they allow humans to go ten times faster, but a human is still driving the process. Finding a middle ground is the best test strategy. |
||
Integrating Exploratory Testing into Product Design Exploratory testing, or ET, is a good fit for agile processes, can be done by any member of the dev/test team, and helps develop applications that map to customers' needs. Kevin Dunne writes how with increased use of ET, testing becomes an intellectual pursuit driving product quality and agility. |
||
Scalability of Tests—A Matrix Hans Buwalda highlights the scalability of unit, functional, and exploratory tests—the three kinds of tests used to verify functionality. Since many automation tools and strategies traditionally focus on functional testing, Hans provides some strategies to make functional testing more manageable. |
||
Automation: Testing or Checking? Interactive exploratory testing and organized automated testing seem to be on opposing ends of a spectrum, but much of that depends on how you apply them. Automated tests don't have to be shallow and boring. You can still explore, learn, and create good tests. Read on for more from Hans Buwalda. |
||
Target's Website Snafu Suggests More Exploratory Testing Target recently found itself in the news over a mislabeled product on its website that generated embarrassing results. The website snafu proves the importance of having an exploratory test team that manually tests in a production environment. |
||
Use Session-Based Testing to Structure Exploratory Testing Session-based testing is a framework to support exploratory testing. Brendan Quinn provides an introduction to session-based testing—from its creation by James and Jonathan Bach to project tools that can assist with session-based testing. |
||
Does Exploratory Testing Randomize Your Agile Test Efforts? Test teams have come to rely on exploratory testing more than ever before to help achieve the required test coverage. While there are clear benefits of adopting exploratory testing in an agile workspace, is it really adding to the randomization that might already exist in the agile environment? |