CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/exploratory-tours-reference

Pure-reference catalog of the seven exploratory testing tours from Whittaker's Exploratory Software Testing (2009): Feature, Money, Landmark, Intellectual, Bad-data, Configuration, and Garbage-collector's, each a themed mission with the signal it surfaces and a worked example. Use as the menu a charter author picks session themes from. Distinct from the mnemonic catalogs sfdpot-exploratory-heuristic (what to vary) and hiccupps-f-heuristic (oracles), and from session-based-test-management-reference, which manages the sessions.

71

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

tour-anti-patterns.mdreferences/

Tour anti-patterns

Deep reference for exploratory-tours-reference SKILL.md. Failure modes that turn a tour from a focusing lens into wasted session time, with the fix for each.

Anti-patternWhy it failsFix
Picking all 7 tours for one sessionTester touches each superficially; no depth.1-3 tours per 90-min session.
Money tour without monetary fieldsThe tour wastes time on "verify nothing changed."Pick tours per the feature; not all features need every tour.
Garbage collector's tour without a sitemapTester misses pages; coverage gaps invisible.Use the team's sitemap / docs as the seed list.
Treating a tour as a checklistTour is a heuristic; rigid stepwise application defeats the exploration.Tester adapts mid-tour as they learn (per the exploratory definition).
Bad-data tour with random inputsRandom isn't useful; structured pathological inputs are.Use canonical payloads (malicious-payload-bank).
Intellectual tour without a domain expert pairTester misses the actual complexity; tour is shallow.Pair with someone who knows the domain.
One tour run per release without rotationThe same tour by the same tester catches the same bugs (or none).Rotate which tours run, which testers, what scope (Picking section).

SKILL.md

tile.json