Pipeline stages and test gates in Testing Fundamentals - Test Execution Trace

Test Overview

This test simulates a software delivery pipeline with multiple stages and test gates. It verifies that the pipeline stops if a test gate fails, ensuring only quality code moves forward.

Test Code - PyTest

Testing Fundamentals

class Pipeline:
    def __init__(self):
        self.stages = []

    def add_stage(self, name, test_gate):
        self.stages.append({'name': name, 'test_gate': test_gate})

    def run(self):
        for stage in self.stages:
            print(f"Running stage: {stage['name']}")
            if not stage['test_gate']():
                print(f"Test gate failed at stage: {stage['name']}")
                return False
        return True

# Define test gates

def unit_tests():
    # Simulate unit tests passing
    return True

def integration_tests():
    # Simulate integration tests passing
    return True

def e2e_tests():
    # Simulate end-to-end tests failing
    return False

# Setup pipeline
pipeline = Pipeline()
pipeline.add_stage('Build', unit_tests)
pipeline.add_stage('Integration', integration_tests)
pipeline.add_stage('E2E', e2e_tests)

# Run pipeline
result = pipeline.run()
assert result == False, "Pipeline should fail due to E2E test gate failure"

Execution Trace - 5 Steps

Step	Action	System State	Assertion	Result
1	Initialize pipeline and add stages with test gates	Pipeline has 3 stages: Build, Integration, E2E with respective test gates	—	PASS
2	Run pipeline: execute 'Build' stage test gate (unit_tests)	Unit tests simulated as passing	unit_tests() returns True	PASS
3	Run pipeline: execute 'Integration' stage test gate (integration_tests)	Integration tests simulated as passing	integration_tests() returns True	PASS
4	Run pipeline: execute 'E2E' stage test gate (e2e_tests)	E2E tests simulated as failing	e2e_tests() returns False	PASS
5	Pipeline stops due to failed E2E test gate	Pipeline run returns False indicating failure	assert result == False	PASS

Failure Scenario

Failing Condition: If a test gate returns False, pipeline should stop and return False

Execution Trace Quiz - 3 Questions

What happens when the E2E test gate fails in the pipeline?

A The pipeline retries the E2E tests automatically

B The pipeline stops and returns failure

C The pipeline ignores the failure and continues

D The pipeline skips the E2E stage and finishes

Key Result

Use test gates in pipeline stages to automatically stop the process when quality checks fail, preventing faulty code from progressing.

Practice

1. What is the main purpose of test gates in a software delivery pipeline?

easy

A. To write new test cases for the software

B. To check if tests pass before moving to the next stage

C. To deploy the software to production automatically

D. To monitor user feedback after release

Solution

1. Step 1: Understand the role of test gates

   Test gates act as checkpoints that verify if tests have passed successfully before allowing the pipeline to continue.

2. Step 2: Differentiate from other pipeline actions

   Deploying software or writing tests are separate activities, not the main function of test gates.

3. Final Answer:

   To check if tests pass before moving to the next stage -> Option B

4. Quick Check:

   Test gates = verify tests pass [OK]

Hint: Test gates stop pipeline if tests fail [OK]

Common Mistakes:

• Confusing test gates with deployment steps
• Thinking test gates create tests
• Assuming test gates handle user feedback

2. Which of the following is the correct order of pipeline stages in a typical CI/CD pipeline?

easy

A. Test -> Build -> Deploy -> Release

B. Release -> Build -> Test -> Deploy

C. Deploy -> Build -> Test -> Release

D. Build -> Test -> Deploy -> Release

Solution

1. Step 1: Recall standard pipeline flow

   The usual order is to first build the software, then run tests, deploy to an environment, and finally release to users.

2. Step 2: Match options to this order

   Build -> Test -> Deploy -> Release matches this sequence exactly.

3. Final Answer:

   Build -> Test -> Deploy -> Release -> Option D

4. Quick Check:

   Build before Test before Deploy [OK]

Hint: Build comes before testing in pipelines [OK]

Common Mistakes:

• Swapping build and test stages
• Deploying before testing
• Releasing before deployment

3. Consider this simplified pipeline code snippet:

stages:
  - build
  - test
  - deploy

test_gate:
  stage: test
  condition: tests_passed == true
  action: continue_pipeline

If tests_passed is false, what happens next?

medium

A. Pipeline stops and does not proceed to deploy

B. Pipeline skips test stage and goes to deploy

C. Pipeline continues to deploy regardless

D. Pipeline restarts from build stage

Solution

1. Step 1: Analyze the test gate condition

   The test gate checks if tests_passed == true. If false, the condition fails.

2. Step 2: Understand pipeline behavior on failed test gate

   When the condition fails, the pipeline stops and does not continue to the deploy stage.

3. Final Answer:

   Pipeline stops and does not proceed to deploy -> Option A

4. Quick Check:

   Failed test gate = pipeline stops [OK]

Hint: Failed test gate stops pipeline flow [OK]

Common Mistakes:

• Assuming pipeline skips tests
• Thinking pipeline restarts automatically
• Believing deploy runs despite failed tests

4. You have this pipeline snippet:

stages:
  - build
  - test
  - deploy

test_gate:
  stage: test
  condition: tests_passed
  action: continue_pipeline

But the pipeline always proceeds even when tests fail. What is the likely error?

medium

A. The condition should explicitly check for true, e.g., tests_passed == true

B. The deploy stage is missing

C. The build stage is not defined

D. The test gate action should be 'stop_pipeline' instead of 'continue_pipeline'

Solution

1. Step 1: Examine the test gate condition

   The condition uses tests_passed alone, which may not evaluate correctly if it's not a boolean.

2. Step 2: Correct the condition syntax

   Explicitly checking tests_passed == true ensures the gate only passes when tests truly pass.

3. Final Answer:

   The condition should explicitly check for true, e.g., tests_passed == true -> Option A

4. Quick Check:

   Explicit condition check fixes gate logic [OK]

Hint: Use explicit boolean checks in test gates [OK]

Common Mistakes:

• Ignoring condition syntax errors
• Assuming missing stages cause gate failure
• Confusing action names in test gates

5. A pipeline has these stages:

1. Build
2. Unit Test
3. Integration Test
4. Deploy

Test gates are set after Unit Test and Integration Test stages. If the Integration Test gate fails, what should happen to ensure safe deployment?

hard

A. Deploy only if Unit Test gate passed, ignoring Integration Test

B. Skip Integration Test and deploy anyway

C. Stop the pipeline and prevent deployment

D. Restart the pipeline from Build stage automatically

Solution

1. Step 1: Understand test gate purpose after Integration Test

   The gate ensures that integration tests pass before deployment to avoid faulty releases.

2. Step 2: Determine correct pipeline behavior on gate failure

   If the Integration Test gate fails, the pipeline must stop to prevent deploying broken software.

3. Final Answer:

   Stop the pipeline and prevent deployment -> Option C

4. Quick Check:

   Failing test gate = stop deployment [OK]

Hint: Failing integration tests block deployment [OK]

Common Mistakes:

• Ignoring integration test failures
• Assuming automatic pipeline restart
• Deploying despite failed test gates