Exploratory testing can be expressed in many different ways. There is no one representation of the entire concept of exploratory testing. Exploratory testing is an umbrella term. That is the reason why this concept is so hard to understand at a glance. Let’s have a closer look at how we approach it.
Exploratory Testing Tours
Tour testing, in rough terms, provides a tool for writing a session charter, helping you to plan the goals of your exploratory test. A testing tour enriches a session with content by providing clear goals within a manageable and comprehensible scope. A testing tour is an exploration organized around a theme – it is not just about taking a test case and calling it a tour. It’s the entire metaphor. Testing tours are strategies and patterns used to uncover certain kinds of defects.
Think of touring as a structured brainstorming approach, excellent for surfacing a collection of ideas that you can then explore in depth, one at a time. Testing tours focus on the intent rather than the separate features of a product.
Popular tours include the Supermodel tour, the Museum tour, the Money tour, the Couch Potato tour, and the FedEx tour.
As an example, let’s have a closer look on one of them: the so-called FedEx tour.
The FedEx Tour
FedEx is an icon in the package-delivery world. They pick up packages, move them around their various distribution centers, and send them to their final destination. Now then, instead of packages moving around the planet through the FedEx system, think of data moving through your application.
During this tour, you must concentrate on this data. Try to identify inputs that are stored and follow them around the application. For example, when an address is entered, ask yourself these questions: Where is it displayed? What features consume it? Is the data manipulated as it moves through the application? If it is used as a billing address, make sure you exercise that feature.
If it is used as a shipping address, make sure you use that feature. If it can be updated, update it. Does it ever get printed, purged, or processed? If so, then do it. Try to find every feature that touches the data so that, just as FedEx handles their packages, you are involved in every stage of the data’s lifecycle to make sure that data flows consistently through your application.
Webinar: Exploratory Testing Tours + Other Exploratory Testing Strategies.
For more details on exploratory testing tours, including tips for choosing among exploratory testing strategies (session-based, tour-based, polychrome, etc.), watch the on-demand webinar, Transform Your Agile Processes with a New Approach to Exploratory Testing. You’ll get a detailed look at how to:
- Introduce exploratory testing into agile sprints and continuous delivery processes
- Apply exploratory testing in a way that complements and accelerates your existing testing strategy
- Plan and coordinate exploratory testing involving a variety of team member perspectives
How can you ensure that you and your team help the organization achieve its objectives? Continuous Testing will be key. By Continuous Testing, we don’t just mean “Test Automation.” We mean the process of executing automated tests as part of the software delivery pipeline in order to obtain feedback on the business risks associated with a software release candidate as rapidly as possible.
Watch the Preparing for DevOps Testing on-demand webinar to explore why Continuous Testing is essential for DevOps. You’ll learn:
- What Continuous Testing requires from the DevOps tester
- The steps you can take to ensure that you’re prepared for this transformation
- How the role of QA can and should shift from the reactive role of validating requirements to a more proactive “quality engineering” role that involves protecting and optimizing the business
Reality Check: The Role of Manual Testing in DevOps Testing
DevOps practices have helped enterprise organizations meet demands to deliver new software faster. But if this newfound speed is at the expense of software quality, the result can put the business at considerable risk. Testing practices and DevOps testing tools have been evolving to keep up with this new pace, often starting with the reduction of manual testing.
Does that mean that manual testing has no place at all in testing practices of the future? Would enterprise organizations eliminate manual testing entirely if they could? Watch the Reality Check- Role of Manual Testing in DevOps on-demand webinar to see why the adoption of DevOps won’t mean the death of manual testing.
You will learn:
- The changing role of manual testing and UI test automation
- What teams can do to meet required levels of testing, without compromising on speed
- What these changes mean for testing service providers
Exploring software testing tools? Try the industry leader for GUI/API testing, exploratory testing, test data management, risk-based testing, and more. Read more.
From Manual Testing To Continuous Testing [Webinar Recap]
Expectations for Continuous Testing are making test automation even more vital—and, in many senses, more challenging. How can manual testers meet these new demands? Read more.
What Is Continuous Testing
What is Continuous Testing, what does it mean for Continuous Testing in DevOps, Agile, Continuous Integration & Continuous Delivery, and how is it different than QA test automation? Read more.