Discovery

Discovery is the first phase of the Cycle Testing Process. It asks the question, "What are the behaviors to test?" Discovery is an activity of learning. Software systems are often very complex – sometimes more complex than any one person can individually comprehend! Teams need time to figure out all the behaviors in the system and determine how they should work.

While behaviors are still being designed, Discovery can be done with the Three Amigos (business, development, and testing roles) getting together to do activities like Story Mapping and Example Mapping. If behaviors are already implemented, and tests are being automated to increase regression coverage, Discovery could be time to explore the system, review documentation, and ask questions.