← Back to Insights Quality Assurance · Exploratory Testing

Exploratory Testing: Definition, Process and Test Charter Example

· Ramin Amini

Exploratory testing is a test approach in which testers design, execute and evaluate tests while they are testing. What they learn about the software feeds directly into their next test ideas. This article shows how exploratory tests differ from scripted tests, when they pay off and how a test session with a test charter works in practice.

What is exploratory testing? Definition

The ISTQB glossary describes exploratory testing, in essence, as an approach in which tests are designed and executed dynamically. They are based on the tester's knowledge, the exploration of the test object and the results of previous tests. In the Certified Tester Foundation Level 4.0 syllabus, exploratory testing is one of the experience-based test techniques.

Two related terms come up again and again:

Exploratory testing is therefore not random clicking. It has a clear mission, a fixed time frame and a documented result. Only the route the tester takes within this frame is left open.

Exploratory vs. scripted testing

In scripted testing, test cases are written in advance: preconditions, steps, expected result. During execution, the tester works through these steps. This ensures repeatability and clear coverage of the requirements. How such test cases are structured is shown in the article How to write test cases.

In exploratory testing, test design and execution happen at the same time. The tester reacts to what they see. If an error message looks odd, they follow it up immediately. If they notice a gap in the logic, they try out variants nobody thought of when the test cases were written.

The two approaches are not opposites. In practice, they complement each other:

One possible approach in a project: core processes are covered by test cases and regression tests. New features and high-risk areas also get exploratory sessions. Which areas these are follows from a risk assessment, as described in the article on risk-based testing.

When exploratory tests pay off

Exploratory testing is less suitable as the only approach when evidence for every single requirement is required, for example in regulated systems or contractual acceptance. There you need traceable test cases linked to the requirement. Exploratory sessions can complement them, but not replace them.

How an exploratory test session works in 5 steps

1. Write the test charter

The charter defines which area is investigated, with which goal and with which resources. It fits on half a page. A proven format is: "Explore [area] with [resources] to discover [risks or information]."

2. Set the time box

A session runs without interruption, usually 60 to 120 minutes. Email, chat and meetings stay off during this time. The time box forces focus on the goal of the charter.

3. Execute and take notes

The tester explores the feature and keeps notes throughout: what they checked, with which data, what they noticed and which questions remain open. Screenshots and short screen recordings help with reproducing issues later. If they come across interesting topics outside the charter, they note them as ideas for another session.

4. Write defect reports

Defects found are recorded as defect reports right after the session: environment, steps, expected and actual result, severity. This turns an observation into a task the development team can work on.

5. Debriefing

The tester and the test manager or product owner briefly discuss the results. What was covered, what was not? Which risks remain? Is another session needed, or new test cases? The debriefing turns individual sessions into a manageable test activity.

Test charter example: web shop checkout

Documentation and traceability

A common objection is that exploratory tests are not traceable. That is only true if nothing is recorded. With little effort, you get reliable documentation:

This makes it possible to show later which areas were checked, when and how. How such evidence can be structured is described in the article on the test log.

Common mistakes in exploratory testing

Exploratory tests with external support

Especially before a release, there is often no time internally for an independent view. An external tester brings experience with typical defect patterns and looks at the software from an independent perspective. As a software testing service provider in Hamburg, we plan exploratory sessions, combine them with test cases and document the results in a traceable way. We work remotely, hybrid or on site, in Hamburg and across Germany.

Conclusion

Exploratory testing uncovers defects nobody thought of when writing the test cases. It needs a clear test charter, a fixed time box, ongoing notes and a debriefing. Combined with test cases and manual testing, it creates a test approach that covers known requirements and makes unknown risks visible. If you are looking for support, you can find our offer under Software Testing & Quality Assurance in Hamburg.

Frequently asked questions about exploratory testing

Is exploratory testing the same as ad hoc testing?

No. Ad hoc tests are performed informally, without prior test analysis and test design and usually without documentation. Exploratory testing has a test charter with a clear mission, a fixed time box and notes that lead to defect reports and a session report. This keeps a traceable record of what was checked.

How long does an exploratory test session last?

60 to 120 minutes without interruption is common. Shorter sessions are often not enough to dig deeper into a feature. Longer sessions reduce concentration. You set the exact duration in the test charter.

Who should carry out exploratory tests?

Ideally testers with experience in test techniques and knowledge of the business domain. An independent view helps, meaning someone who did not build the feature themselves. Business users can also provide valuable input in joint sessions if an experienced tester leads the session.

Exploratory testing for your project

We plan and run exploratory test sessions, connect them with your test cases and deliver traceable results up to a release recommendation.

Book an initial consultation

More about our service: Software testing & quality assurance in Hamburg →