While Exploratory testing is flexible and can be utilized in various testing settings, it helps when a schedule can be put in place to maximize the output of each Exploratory run. The primary structure of your Exploratory run schedule will typically emerge after several runs.
A feature-centric Exploratory schedule, like the name implies, is built around a specific feature. Exploratory runs in feature-centric schedules can either be proactive or retroactive in approach, and typically feature a recently-developed feature that has not had substantial regression coverage built around it.
- Freshly developed features can be quickly tested with little effort
- Uncovered issues can be addressed while developers are still familiar with code
- Tests generated can be used as guideposts around where to start building regression coverage.
Sample Run Structure:
1st Run - Bug-finding Feature A
2nd Run - Bug-finding Feature A/Test-creation Feature A
3rd Run - Test Creation Feature A
4th Run - Test Creation Feature A/Bug-finding Feature B
Release-oriented Exploratory schedules are built around feature release timelines. Typically, these exploratory runs are approached retroactively, while a feature is in an alpha or beta release stage.
- uncovers edge case issues before a feature is made generally available
- Testing can simulate what end-users would encounter if the feature was live
- an easy temperature check about whether a feature is ready to be customer-facing
Typical Run Structure
1st Run: Bug-finding A (alpha release)
2nd Run: Bug-finding A (beta release)
3rd Run: Test-creation A (general release)
4th Run: Test-creation A (general release)
All Exploratory schedules will necessarily differ based on your testing needs. For help on determining the best schedule for you, please contact your Rainforest CSM or reach out to us at firstname.lastname@example.org.