CTFL 5.1.3: Compare and contrast entry criteria and exit criteria
K2Syllabus section 5.1.3
3 original PrepBench practice questions for learning objective 5.1.3 of the CTFL 4.0 syllabus. Try the examples below and check each answer against its syllabus reference.
Practice questions
Question 1
Which of the following is an example of an ENTRY criterion for test execution?
- All planned tests have been executed
- The defect backlog contains no critical open defects
- The test environment is available and configured
- The test completion report has been approved
Show answer
- All planned tests have been executedHaving executed all planned tests is an exit criterion, not an entry condition.
- The defect backlog contains no critical open defectsA clean critical-defect backlog is an exit criterion for completing testing.
- Correct answer: The test environment is available and configuredA ready, configured test environment is a precondition — an entry criterion.
- The test completion report has been approvedApproval of the completion report happens at the end, so it is an exit criterion.
Entry criteria define preconditions for starting an activity — e.g. testable requirements available, environment ready, test data prepared. Executed tests, defect thresholds, and achieved coverage are typical exit criteria.
Syllabus section 5.1.3
Question 2
Which of the following is a typical EXIT criterion for a test level?
- The test environment has been fully set up and configured for use
- The testers needed for the level have all been hired
- The requirements have all been reviewed and baselined first
- The planned coverage has been achieved and unresolved defects are within the agreed limit
Show answer
- The test environment has been fully set up and configured for useA ready environment is a precondition — an entry criterion, not an exit criterion.
- The testers needed for the level have all been hiredHaving testers in place is an entry condition, not a measure of completion.
- The requirements have all been reviewed and baselined firstBaselined requirements are an entry criterion for starting, not finishing.
- Correct answer: The planned coverage has been achieved and unresolved defects are within the agreed limitAchieved coverage with unresolved defects within the agreed limit is a typical exit criterion.
Exit criteria define when an activity can be declared complete: e.g. planned tests executed, coverage targets achieved, unresolved defects within thresholds. Environment availability and baselined requirements are entry criteria.
Syllabus section 5.1.3
Question 3
An Agile team maintains two checklists: one that a user story must satisfy before development and testing start, and one that it must satisfy before it counts as releasable. What are they called?
- Definition of Done for the first and Definition of Ready for the second
- Entry criteria for the first and the test completion report for the second
- Both are the Definition of Ready, applied at two different points
- Definition of Ready for the first and Definition of Done for the second
Show answer
- Definition of Done for the first and Definition of Ready for the secondThis reverses the two: Ready gates the start, Done gates releasability.
- Entry criteria for the first and the test completion report for the secondThe second checklist is a set of criteria, not a report produced at the end.
- Both are the Definition of Ready, applied at two different pointsThe two checklists gate different points and have different names.
- Correct answer: Definition of Ready for the first and Definition of Done for the secondDefinition of Ready to start, Definition of Done to be releasable.
In Agile software development, exit criteria are often called the Definition of Done, defining the team's objective metrics for a releasable item. The entry criteria that a user story must fulfil before development and/or testing activities start are called the Definition of Ready.
Syllabus section 5.1.3
Original PrepBench practice material, not official exam questions or exam dumps. PrepBench is independent and is not affiliated with or endorsed by ISTQB®.