4.6Integrating Exploratory Findings into the Test Process

Exploratory testing does not exist in isolation. Its findings should feed into other testing activities:

From Exploration to Automation

When an exploratory session discovers a bug:

1. File the bug report
2. After the fix, write an automated regression test for that specific scenario
3. The automated test ensures the bug never returns
4. The exploratory session moves on to discover new issues

This creates a virtuous cycle: exploration finds new bugs, automation prevents recurrence, exploration continues to find new things.

From Exploration to Test Cases

When exploration reveals an important scenario that was not in the scripted test suite:

1. Document the scenario as a formal test case
2. Add it to the regression suite
3. Update the charter list to reflect that the area now has scripted coverage

From Questions to Requirements

When exploration raises questions about expected behavior:

1. Document the question in the session report
2. Bring it to the product owner or developer
3. The answer becomes a documented requirement
4. Write a test case for the clarified requirement