Continuous testing in CI/CD in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to run tests automatically after each code commit.

Testing Fundamentals

pipeline {
  stages {
    stage('Test') {
      steps {
        sh '[1]'
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Anpm start

Bnpm test

Cnpm install

Dnpm run build

Attempts:

3 left

💡 Hint

Common Mistakes

Using build or start commands instead of test commands.

Forgetting to run tests in the pipeline.

The npm test command runs the test scripts defined in your project, enabling continuous testing in the CI/CD pipeline.

2fill in blank

medium

Complete the code to specify the testing stage in a Jenkinsfile.

Testing Fundamentals

stage('Test') {
  steps {
    [1] 'pytest tests/'
  }
}

Drag options to blanks, or click blank then click option'

Ash

Becho

Cbat

Dinput

Attempts:

3 left

💡 Hint

Common Mistakes

Using echo which only prints text.

Using input which waits for user input.

The sh step runs shell commands in Jenkins pipelines, which is used here to run pytest tests.

3fill in blank

hard

Fix the error in the GitHub Actions workflow to run tests on push.

Testing Fundamentals

on: [push]
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Run tests
        run: [1]

Drag options to blanks, or click blank then click option'

Anpm test

Bnpm deploy

Cnpm build

Dnpm start

Attempts:

3 left

💡 Hint

Common Mistakes

Using npm build which builds the project but does not test.

Using npm start which runs the app but not tests.

The correct command to run tests is npm test. Other commands do not run tests.

4fill in blank

hard

Fill both blanks to create a Python dictionary comprehension that includes only tests with names starting with 'test_'.

Testing Fundamentals

test_dict = {test: result for test, result in test_results.items() if test [1] '[2]'}

Drag options to blanks, or click blank then click option'

Astartswith

Btest_

Cendswith

Dcontains

Attempts:

3 left

💡 Hint

Common Mistakes

Using endswith or contains which do not match the requirement.

Forgetting to put quotes around the string 'test_'.

The startswith method checks if the test name begins with 'test_'. This filters only test results for tests starting with that prefix.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps uppercase test names to their results if the result is 'passed'.

Testing Fundamentals

passed_tests = [1]: [2] for [3], result in test_results.items() if result == 'passed'

Drag options to blanks, or click blank then click option'

Atest.upper()

Bresult

Ctest

Dtest.lower()

Attempts:

3 left

💡 Hint

Common Mistakes

Using test.lower() instead of uppercase.

Mixing up keys and values in the comprehension.

This comprehension creates a dictionary where keys are uppercase test names and values are the results, but only for tests that passed.

Practice

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

easy

A. To automatically run tests on every code change

B. To manually test software after deployment

C. To delay testing until the final release

D. To only test code on the developer's machine

Solution

1. Step 1: Understand continuous testing concept

   Continuous testing means running tests automatically during the CI/CD process.

2. Step 2: Identify the purpose in CI/CD

   Its goal is to catch bugs early by testing every code change automatically.

3. Final Answer:

   To automatically run tests on every code change -> Option A

4. Quick Check:

   Continuous testing = automatic tests on code changes [OK]

Hint: Continuous testing means tests run automatically every change [OK]

Common Mistakes:

• Thinking testing is manual only
• Believing tests run after deployment
• Assuming testing happens only once at release

2. Which of the following is the correct syntax to run tests in a simple CI pipeline using a shell command?

easy

A. sh tests.sh

B. run tests.sh

C. execute tests.sh

D. start tests.sh

Solution

1. Step 1: Recall shell command syntax

   To run a shell script, the correct command is 'sh scriptname.sh'.

2. Step 2: Check each option

   sh tests.sh uses 'sh tests.sh' which correctly runs the script. Others are invalid shell commands.

3. Final Answer:

   sh tests.sh -> Option A

4. Quick Check:

   Shell script run = sh script.sh [OK]

Hint: Use 'sh script.sh' to run shell scripts in pipelines [OK]

Common Mistakes:

• Using 'run' or 'start' which are not shell commands
• Forgetting to use 'sh' before script name
• Confusing shell commands with other languages

3. Given this CI pipeline snippet:

steps:
  - name: Run tests
    run: |
      echo "Starting tests"
      pytest tests/
      echo "Tests done"

What will be the output if all tests pass?

medium

A. Starting tests\nTests failed

B. Starting tests\npytest: command not found

C. Starting tests\nTests done

D. Tests done\nStarting tests

Solution

1. Step 1: Analyze the commands in order

   The pipeline runs 'echo "Starting tests"', then 'pytest tests/', then 'echo "Tests done"'.

2. Step 2: Understand output if tests pass

   If pytest runs successfully, it outputs test results but here we focus on echo commands output. So output includes 'Starting tests' then 'Tests done'.

3. Final Answer:

   Starting tests\nTests done -> Option C

4. Quick Check:

   Echo commands print start and done messages [OK]

Hint: Echo commands print messages before and after tests [OK]

Common Mistakes:

• Assuming pytest output is shown instead of echo
• Mixing order of printed lines
• Thinking tests failed without error

4. In a CI pipeline, the test step fails with error: sh: pytest: command not found. What is the most likely cause?

medium

A. The test script has a syntax error

B. The pipeline skipped the test step

C. The tests directory is missing

D. pytest is not installed in the pipeline environment

Solution

1. Step 1: Interpret the error message

   The error 'sh: pytest: command not found' means the shell cannot find the pytest command.

2. Step 2: Identify cause in CI environment

   This usually means pytest is not installed or not in PATH in the pipeline environment.

3. Final Answer:

   pytest is not installed in the pipeline environment -> Option D

4. Quick Check:

   Command not found = missing installation [OK]

Hint: Command not found means tool missing or not installed [OK]

Common Mistakes:

• Assuming syntax error causes command not found
• Thinking missing tests directory causes this error
• Believing pipeline skipped the step without error

5. You want to add continuous testing to your CI/CD pipeline so tests run only if code changes affect the src/ directory. Which approach best achieves this?

hard

A. Run tests on every pipeline run regardless of changes

B. Configure the pipeline to run tests only when files in src/ change

C. Run tests only after deployment to production

D. Manually trigger tests after code review

Solution

1. Step 1: Understand conditional testing in CI/CD

   To save time, tests should run only when relevant code changes occur.

2. Step 2: Apply file path filters in pipeline configuration

   Configuring the pipeline to detect changes in src/ and run tests only then is the best approach.

3. Final Answer:

   Configure the pipeline to run tests only when files in src/ change -> Option B

4. Quick Check:

   Run tests conditionally based on changed files [OK]

Hint: Run tests only if relevant files change to save time [OK]

Common Mistakes:

• Running tests every time wastes resources
• Testing only after deployment delays bug detection
• Manual triggers reduce automation benefits