Exploratory Testing Loop

A simple, repeatable cycle that structures an exploratory testing session so that people without a testing background can follow it. A common shape is: generate initial test ideas within a short time limit, take a first look at the change, refine the test ideas based on what was seen, then go deeper, repeating as needed. Keeping the loop simple at first lowers the barrier for developers and others to take part, with extra concerns such as testability added only once the basic rhythm is comfortable.

For example: spending ten minutes on test ideas before opening the feature; doing a quick reconnaissance pass and then refining charters; or adding a side list of testability problems once the team is used to the core loop.