Entry and exit criteria in Testing Fundamentals - Framework Patterns

Framework Mode - Entry and exit criteria

Folder Structure for Entry and Exit Criteria Management

  project-root/
  ├── docs/
  │   ├── entry_criteria.md       # Document defining entry criteria
  │   ├── exit_criteria.md        # Document defining exit criteria
  │   └── test_plan.md            # Overall test plan including criteria
  ├── tests/
  │   ├── test_cases/             # Automated and manual test cases
  │   └── test_suites/            # Grouped test suites
  ├── reports/
  │   └── test_reports/           # Test execution reports
  ├── config/
  │   └── environment_settings.yaml  # Environment and criteria related configs
  └── tools/
      └── criteria_checker.py    # Scripts/tools to verify criteria compliance
  

Test Framework Layers for Entry and Exit Criteria

• Documentation Layer: Holds clear, agreed-upon entry and exit criteria documents.
• Test Planning Layer: Integrates criteria into test plans and schedules.
• Test Execution Layer: Runs tests only after entry criteria are met; monitors exit criteria during and after tests.
• Verification Layer: Tools or scripts that check if criteria are fulfilled before moving to next phase.
• Reporting Layer: Reports status of criteria compliance alongside test results.

Configuration Patterns for Managing Entry and Exit Criteria

• Centralized Criteria Files: Store criteria in version-controlled markdown or YAML files for easy updates and sharing.
• Environment Flags: Use config flags to indicate if entry criteria are met (e.g., database ready, build stable).
• Automated Checks: Scripts that read config and verify criteria automatically before tests start.
• Credentials and Access: Ensure access permissions are configured before testing begins as part of entry criteria.

Test Reporting and CI/CD Integration for Entry and Exit Criteria

• Pre-Test Checks: CI pipelines verify entry criteria before running tests; if not met, pipeline stops with clear message.
• Post-Test Validation: Exit criteria status included in test reports to confirm readiness for release or next phase.
• Dashboard Integration: Show criteria compliance status on dashboards for team visibility.
• Notifications: Automated alerts if criteria are not met to prompt corrective actions.

Best Practices for Entry and Exit Criteria in Test Frameworks

1. Define Clear and Measurable Criteria: Use simple, specific conditions everyone understands.
2. Keep Criteria Up to Date: Review and update criteria regularly as project evolves.
3. Automate Verification: Use scripts or tools to check criteria automatically to avoid human error.
4. Integrate Criteria Checks in CI/CD: Make criteria gating part of automated pipelines to ensure quality gates.
5. Communicate Criteria Status: Share entry and exit criteria results clearly with all stakeholders.

Self-Check Question

Where in this folder structure would you add a new script that automatically verifies if the entry criteria are met before starting tests?

Key Result

Entry and exit criteria ensure testing starts and ends only when agreed conditions are met, improving quality and predictability.

Practice

1. What is the main purpose of entry criteria in software testing?

easy

A. To fix bugs found during testing

B. To decide when testing can stop

C. To list all test cases

D. To decide when testing can start

Solution

1. Step 1: Understand the definition of entry criteria

   Entry criteria are conditions that must be met before testing begins.

2. Step 2: Differentiate entry from exit criteria

   Exit criteria decide when testing ends, not when it starts.

3. Final Answer:

   To decide when testing can start -> Option D

4. Quick Check:

   Entry criteria = start testing [OK]

Hint: Entry criteria = conditions to start testing [OK]

Common Mistakes:

• Confusing entry criteria with exit criteria
• Thinking entry criteria fix bugs
• Assuming entry criteria list test cases

2. Which of the following is a correct example of an exit criteria statement?

easy

A. All planned test cases have been executed

B. Test environment is set up and ready

C. Testers have received training materials

D. Requirements documents are being reviewed

Solution

1. Step 1: Identify exit criteria characteristics

   Exit criteria define when testing can stop, such as completing all planned tests.

2. Step 2: Evaluate each option

   Options A, C, and D relate to preparation or start, not finishing testing.

3. Final Answer:

   All planned test cases have been executed -> Option A

4. Quick Check:

   Exit criteria = finish testing [OK]

Hint: Exit criteria = conditions to stop testing [OK]

Common Mistakes:

• Mixing setup tasks with exit criteria
• Choosing entry criteria as exit criteria
• Ignoring completion of test cases

3. Consider this scenario: A test team starts testing only after the test environment is ready and requirements are frozen. They stop testing when all critical bugs are fixed and test cases executed. Which statements about entry and exit criteria are true?

medium

A. Entry criteria include environment readiness and frozen requirements; exit criteria include bug fixes and test completion

B. Entry criteria include bug fixes; exit criteria include environment readiness

C. Entry criteria include test completion; exit criteria include frozen requirements

D. Entry criteria and exit criteria are the same in this scenario

Solution

1. Step 1: Identify entry criteria in the scenario

   Testing starts after environment is ready and requirements are frozen, so these are entry criteria.

2. Step 2: Identify exit criteria in the scenario

   Testing stops when critical bugs are fixed and test cases executed, so these are exit criteria.

3. Final Answer:

   Entry criteria include environment readiness and frozen requirements; exit criteria include bug fixes and test completion -> Option A

4. Quick Check:

   Entry = start conditions, Exit = stop conditions [OK]

Hint: Entry = start conditions; Exit = stop conditions [OK]

Common Mistakes:

• Swapping entry and exit criteria
• Ignoring bug fixes as exit criteria
• Confusing frozen requirements as exit criteria

4. A test manager wrote the following exit criteria: "All test cases executed, all bugs fixed, and test environment cleaned." Which part is incorrect or problematic?

medium

A. All test cases executed should not be part of exit criteria

B. All bugs fixed is not necessary for exit criteria

C. All test cases executed is irrelevant for exit criteria

D. Exit criteria must include test environment setup

Solution

1. Step 1: Analyze each exit criteria item

   All test cases executed is a valid exit criterion. Test environment cleaned is usually a post-testing task, not exit criteria.

2. Step 2: Consider bug fixing in exit criteria

   Requiring all bugs fixed is often unrealistic; exit criteria usually require critical bugs fixed, not all.

3. Final Answer:

   All bugs fixed is not necessary for exit criteria -> Option B

4. Quick Check:

   Exit criteria need critical bug fixes, not all bugs [OK]

Hint: Exit criteria need critical bug fixes, not all bugs [OK]

Common Mistakes:

• Assuming all bugs must be fixed to exit testing
• Confusing cleanup tasks with exit criteria
• Ignoring importance of test case execution

5. A project team defined entry criteria as "Requirements document approved, test environment ready, and test data prepared." Exit criteria are "All test cases executed, 95% of test cases passed, and all critical defects resolved." During testing, 90% of test cases passed, but all critical defects were fixed. What should the team do according to these criteria?

hard

A. Restart testing because entry criteria are not met

B. Stop testing because all critical defects are fixed

C. Continue testing until 95% pass rate is reached

D. Ignore pass rate and focus on test environment readiness

Solution

1. Step 1: Review exit criteria conditions

   Exit criteria require 95% test cases passed and all critical defects fixed.

2. Step 2: Compare actual results with exit criteria

   Only 90% passed, which is below 95%, so exit criteria are not met yet.

3. Final Answer:

   Continue testing until 95% pass rate is reached -> Option C

4. Quick Check:

   Exit criteria must be fully met before stopping [OK]

Hint: Meet all exit criteria before stopping testing [OK]

Common Mistakes:

• Stopping testing early when pass rate is low
• Ignoring pass rate in exit criteria
• Confusing entry criteria with exit criteria