“Draw the software testing life cycle top-down: requirements review, test planning, test case design, test environment setup and test execution. If defects are found, log and fix them and retest the fix; then check the exit criteria, and either add test cases for another cycle or write the test closure report.”
Read the decisions behind it.
The main path runs top-down in the order the phases happen, from requirements review to test execution.
A single "Defects found?" decision sends failures through logging, fixing and retesting before the exit check.
Both paths meet at "Exit criteria met?", so every cycle ends with the same release question.
An unmet exit criterion ends in "run another cycle" rather than a back-arrow, which keeps the chart readable.
Use it to explain a repeatable software test lifecycle. Use BPMN when roles, handoffs, and events must be formalized.
Other examples in this family.
Common questions
What is a software testing process diagram?
It is a visual workflow of test preparation, execution, defect handling, and release readiness checks.
How do I make a testing process diagram?
Map the testing stages in order and add decision branches for failures, retesting, and exit criteria.
How do I read a testing feedback loop?
It means a failed test is fixed and retested before the team can continue toward closure.
Is a template different from an example?
A template is editable for your release process; an example records the process used by one team.
Do I need an account?
Yes, a free one. No card is asked for.