Why CI/CD integrates testing into delivery in Testing Fundamentals - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is testing integrated into CI/CD pipelines?

In a CI/CD pipeline, why is testing included as part of the delivery process?

A To delay the release process and add more steps

B To catch bugs early and prevent faulty code from reaching production

C To increase manual work for developers

D To reduce the number of automated checks

💡 Hint

Think about how early detection of problems affects software quality.

Testing in CI/CD helps find errors quickly, so developers can fix them before the code reaches users. This improves software quality and speeds up delivery.

💻 Command Output

intermediate

Output of a failed test in CI pipeline

What will be the output if a unit test fails during a CI pipeline run?

Testing Fundamentals

pytest tests/test_example.py

A Pipeline continues without any message

B Pipeline ignores test results and deploys code

C Test passed message and pipeline stops

D Test failed message with error details and pipeline stops

💡 Hint

Consider what happens when tests fail in automated pipelines.

When a test fails, the CI pipeline shows the failure message with details and usually stops further steps to prevent bad code deployment.

🔀 Workflow

advanced

Order of steps in CI/CD with testing

Arrange the following steps in the correct order for a CI/CD pipeline that includes testing.

A 4,2,1,3

B 4,1,2,3

C 2,4,1,3

D 4,2,3,1

💡 Hint

Think about what happens first when a developer pushes code.

First, code is committed. Then the app is built. After building, tests run to verify the build. If tests pass, deployment happens.

❓ Troubleshoot

advanced

Why did deployment happen despite test failures?

A CI/CD pipeline deployed code even though some tests failed. What is the most likely cause?

A Tests passed but deployment failed

B Tests were not included in the pipeline

C The pipeline was configured to ignore test failures

D The code was manually deployed bypassing the pipeline

💡 Hint

Check pipeline settings about test results.

If the pipeline ignores test failures, it will continue deployment even if tests fail, which is risky.

✅ Best Practice

expert

Best practice for testing in CI/CD pipelines

Which practice best ensures reliable testing in a CI/CD pipeline?

A Run tests in isolated environments with fresh data each time

B Skip tests for minor code changes to speed up delivery

C Run tests only once a month to save resources

D Run tests manually after deployment

💡 Hint

Think about consistency and reliability in testing.

Running tests in isolated environments with fresh data prevents interference and ensures consistent results, which is a best practice.

Practice

1. Why is testing integrated into the CI/CD pipeline?

easy

A. To avoid writing code

B. To slow down the delivery process

C. To increase manual work for developers

D. To find problems early and improve software quality

Solution

1. Step 1: Understand the purpose of CI/CD testing

   Testing in CI/CD helps catch bugs early before software reaches users.

2. Step 2: Recognize the benefit of early problem detection

   Finding issues early improves software quality and reduces costly fixes later.

3. Final Answer:

   To find problems early and improve software quality -> Option D

4. Quick Check:

   Early testing = better quality [OK]

Hint: Testing in CI/CD finds bugs early to improve quality [OK]

Common Mistakes:

• Thinking testing slows delivery
• Believing testing is optional
• Assuming testing increases manual work

2. Which of the following is the correct way to add a test stage in a CI/CD YAML pipeline?

easy

A. steps:
- build
- deploy
- test

B. stages:
- build
- test
- deploy

C. jobs:
- deploy
- test
- build

D. phases:
- test
- build
- deploy

Solution

1. Step 1: Identify correct CI/CD pipeline syntax

   Most CI/CD tools use 'stages' to define order: build, test, deploy.

2. Step 2: Check the order of stages

   Testing should come after build and before deploy for proper flow.

3. Final Answer:

   stages: - build - test - deploy -> Option B

4. Quick Check:

   Stages order: build, test, deploy [OK]

Hint: Stages define order: build, test, then deploy [OK]

Common Mistakes:

• Mixing steps and stages keywords
• Placing test after deploy
• Using unsupported keywords like phases

3. In a CI/CD pipeline, why is it important to run automated tests before deployment?

easy

A. To increase manual testing effort

B. To delay the deployment process intentionally

C. To catch bugs early and prevent faulty code from reaching users

D. To skip code reviews

Solution

1. Step 1: Understand the role of automated tests in CI/CD

   Automated tests verify code correctness quickly and reliably before deployment.

2. Step 2: Recognize the impact on software quality and user experience

   Running tests early prevents bugs from reaching users, improving reliability.

3. Final Answer:

   To catch bugs early and prevent faulty code from reaching users -> Option C

4. Quick Check:

   Tests before deploy = fewer bugs in production [OK]

Hint: Tests before deploy catch bugs early [OK]

Common Mistakes:

• Thinking tests delay deployment on purpose
• Confusing automated tests with manual effort
• Believing tests replace code reviews

4. Consider this simplified CI/CD pipeline snippet:

stages:
  - build
  - test

build_job:
  stage: build
  script:
    - echo "Building..."
test_job:
  stage: test
  script:
    - exit 1

What will happen when this pipeline runs?

medium

A. The build job runs, then the test job fails, stopping the pipeline

B. Both build and test jobs succeed

C. The test job runs before the build job

D. The pipeline ignores the test job failure and continues

Solution

1. Step 1: Analyze job order by stages

   Build stage runs first, then test stage runs after build completes.

2. Step 2: Check test job script

   Test job script exits with code 1, which means failure.

3. Final Answer:

   The build job runs, then the test job fails, stopping the pipeline -> Option A

4. Quick Check:

   Failing test stops pipeline [OK]

Hint: Exit code 1 means test failure stops pipeline [OK]

Common Mistakes:

• Assuming test runs before build
• Thinking pipeline ignores failures
• Believing all jobs always succeed

5. A CI/CD pipeline has this test stage:

test_job:
  stage: test
  script:
    - pytest tests/
  only:
    - main
    - develop

Why might tests not run on a feature branch?

medium

A. Because the 'only' keyword limits runs to 'main' and 'develop' branches

B. Because pytest is not installed

C. Because the test stage is missing

D. Because the script syntax is incorrect

Solution

1. Step 1: Understand 'only' keyword effect

   'only' restricts job runs to specified branches: main and develop.

2. Step 2: Check branch context

   Feature branches are not listed, so tests won't run there.

3. Final Answer:

   Because the 'only' keyword limits runs to 'main' and 'develop' branches -> Option A

4. Quick Check:

   'only' limits branches [OK]

Hint: 'only' controls which branches run jobs [OK]

Common Mistakes:

• Assuming tests run on all branches
• Blaming missing pytest without checking config
• Ignoring branch filters in pipeline