Test Cycle
A test cycle is a complete execution of planned testing activities performed for a specific release, iteration, or testing objective.
“An instance of the test process against a single identifiable version of the test object.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Test Cycle?
Each test cycle includes planning, execution, defect management, retesting, and reporting before moving to the next cycle.
Defined timeframe: Covers a specific testing period.
Repeatable process: Multiple cycles may occur during a project.
Release support: Helps organize testing activities.
Real World Example
A regulated product team is preparing a release where Test cycle appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Test cycle as interchangeable with nearby ISTQB terms. That makes test scope blurry and can lead to weak evidence for the release decision.
The tester anchors the discussion in the official definition, asks where the concept appears in the product, and designs examples that show the difference between Test cycle and similar ideas.
The page becomes useful in practice because Test cycle is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Test cycle in the context of ISTQB terminology?
Question 2
A tester needs to explain Test cycle to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Test Cycle. Test your understanding with topic-specific questions in our Mock Exams.