Continuous testing in CI/CD in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the main purpose of continuous testing in a CI/CD pipeline?

Continuous testing is a key part of CI/CD. What is its main goal?

A To run tests only after the entire software is deployed to production

B To automatically run tests early and often to catch bugs quickly

C To manually check code quality before merging changes

D To delay testing until all features are complete

💡 Hint

Think about when tests should run to find problems fast.

Continuous testing means running automated tests frequently during development to find bugs early, not waiting until deployment.

💻 Command Output

intermediate

What is the output of this Jenkins pipeline stage running tests?

Given this Jenkinsfile snippet, what will be the output if tests fail?

Testing Fundamentals

stage('Test') {
  steps {
    sh 'pytest tests/'
  }
}

A The pipeline stops and marks the build as failed

B The pipeline continues to deploy even if tests fail

C The pipeline ignores test results and passes

D The pipeline retries tests indefinitely

💡 Hint

How does Jenkins treat shell command failures by default?

In Jenkins, if a shell command like 'pytest' fails (non-zero exit), the pipeline stage fails and stops further steps.

🔀 Workflow

advanced

Order the steps in a typical continuous testing workflow in CI/CD

Arrange these steps in the correct order for continuous testing in a CI/CD pipeline.

A 2,3,1,4

B 3,2,1,4

C 2,1,3,4

D 1,2,3,4

💡 Hint

Think about what happens first: code push or pipeline trigger?

The developer pushes code, then the CI server triggers the pipeline, which runs tests, then reports results.

❓ Troubleshoot

advanced

Why might tests not run automatically in a CI/CD pipeline?

You set up a CI/CD pipeline but notice tests are not running after code pushes. What could cause this?

A The code repository is empty

B The CI/CD server is offline permanently

C The test commands are missing or incorrectly specified in the pipeline config

D The developer forgot to write any tests

💡 Hint

Check the pipeline configuration for test steps.

If the pipeline config does not include commands to run tests, tests will not execute automatically.

✅ Best Practice

expert

Which practice best improves test reliability in continuous testing?

In continuous testing, which practice helps ensure tests give consistent results?

A Running tests only on developer machines

B Running tests manually after deployment

C Skipping tests that sometimes fail randomly

D Using isolated test environments that reset before each run

💡 Hint

Think about how to avoid test failures caused by leftover data or state.

Isolated, clean test environments prevent interference from previous runs, improving test reliability.