Continuous Integration testing in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a basic CI pipeline step that runs tests.

Testing Fundamentals

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

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

Apytest

Bclean

Cbuild

Ddeploy

Attempts:

3 left

💡 Hint

Common Mistakes

Using build or deploy commands instead of test commands.

The pytest command runs tests in the CI pipeline. Other options do not run tests.

2fill in blank

medium

Complete the code to trigger the CI pipeline on every push to the main branch.

Testing Fundamentals

on:
  push:
    branches:
      - '[1]'

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

Afeature

Bdevelop

Cmain

Drelease

Attempts:

3 left

💡 Hint

Common Mistakes

Using feature or develop branches which are not main branches.

The CI pipeline triggers on pushes to the main branch, which is the primary branch.

3fill in blank

hard

Fix the error in the test script command to correctly run tests in CI.

Testing Fundamentals

steps:
  - name: Run tests
    run: [1]

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

Anpm deploy

Bnpm run test

Cnpm build

Dnpm testt

Attempts:

3 left

💡 Hint

Common Mistakes

Typo in the test command causing failure.

npm run test is the correct command to run tests. npm testt is a typo.

4fill in blank

hard

Fill both blanks to define a test stage that runs tests only if the code is pushed to the main branch.

Testing Fundamentals

stages:
  - name: Test
    if: contains([1], '[2]')
    steps:
      - run: pytest

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

Agithub.ref

Bmain

Cdevelop

Dgithub.event_name

Attempts:

3 left

💡 Hint

Common Mistakes

Using event name instead of branch ref, or wrong branch name.

The condition checks if the branch reference github.ref contains main to run tests only on main branch pushes.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps test names to their pass status if the test duration is less than 5 seconds.

Testing Fundamentals

test_results = { [1]: results[[2]]['passed'] for [1] in results if results[[2]]['duration'] [3] 5 }

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

Atest_name

B'test_name'

C<

D>

Attempts:

3 left

💡 Hint

Common Mistakes

Using string keys instead of variable, or wrong comparison operator.

The comprehension uses test_name as the key and index, and filters tests with duration less than 5 seconds using <.

Practice

1. What is the main purpose of Continuous Integration (CI) testing in software development?

easy

A. To automatically run tests on every code change to find bugs early

B. To manually test software after all development is complete

C. To deploy software directly to users without testing

D. To write code without any testing involved

Solution

1. Step 1: Understand CI testing purpose

   Continuous Integration testing runs tests automatically whenever code changes happen.

2. Step 2: Compare options with CI goals

   Only To automatically run tests on every code change to find bugs early describes automatic testing on code changes to catch bugs early.

3. Final Answer:

   To automatically run tests on every code change to find bugs early -> Option A

4. Quick Check:

   CI testing = automatic tests on code changes [OK]

Hint: CI testing runs tests automatically on code updates [OK]

Common Mistakes:

• Thinking CI testing is manual
• Confusing CI with deployment
• Believing testing happens after development only

2. Which of the following is the correct syntax to trigger a test run in a CI pipeline configuration file?

easy

A. run_tests: true

B. test: run

C. execute tests

D. script: pytest

Solution

1. Step 1: Identify common CI syntax

   CI pipelines often use a script key to run commands like pytest for tests.

2. Step 2: Check options for valid syntax

   Only script: pytest uses correct syntax: script: pytest runs tests properly.

3. Final Answer:

   script: pytest -> Option D

4. Quick Check:

   CI test command syntax = script: pytest [OK]

Hint: Look for 'script:' followed by test command [OK]

Common Mistakes:

• Using invalid keys like 'run_tests' or 'test: run'
• Writing commands without proper keys
• Confusing natural language with config syntax

3. Consider this simplified CI test script snippet:

steps:
  - script: echo "Run tests"
  - script: pytest tests/
  - script: echo "Tests complete"

What will be the output when this CI pipeline runs?

medium

A. Run tests\nTests complete

B. Only pytest tests output

C. Run tests\n(pytest runs tests output)\nTests complete

D. No output because script commands are ignored

Solution

1. Step 1: Analyze each script step output

   The first script prints "Run tests", the second runs pytest showing test results, the third prints "Tests complete".

2. Step 2: Combine outputs in order

   All outputs appear in sequence: first message, pytest output, then final message.

3. Final Answer:

   Run tests\n(pytest runs tests output)\nTests complete -> Option C

4. Quick Check:

   CI scripts run sequentially showing all outputs [OK]

Hint: CI scripts run in order showing all outputs [OK]

Common Mistakes:

• Ignoring pytest output
• Assuming only first or last script runs
• Thinking scripts are skipped

4. A CI pipeline fails to run tests because the test command is written as script: pytes instead of pytest. What is the best way to fix this error?

medium

A. Change pytes to pytest in the script command

B. Remove the script command entirely

C. Add a new script command with pytest but keep the old one

D. Ignore the error and rerun the pipeline

Solution

1. Step 1: Identify the typo in the test command

   The command pytes is a misspelling of pytest, causing the failure.

2. Step 2: Correct the command to fix the pipeline

   Fixing the typo to pytest ensures the tests run properly.

3. Final Answer:

   Change pytes to pytest in the script command -> Option A

4. Quick Check:

   Fix typos in commands to fix CI errors [OK]

Hint: Check spelling of commands in CI scripts [OK]

Common Mistakes:

• Removing test commands instead of fixing
• Adding duplicate commands without removing errors
• Ignoring errors and rerunning

5. You want to ensure your CI pipeline only runs tests on files that changed in the last commit to save time. Which approach best applies this in a CI configuration?

hard

A. Run all tests every time regardless of changes

B. Use a script step that detects changed files and runs tests only on those

C. Disable tests in the CI pipeline

D. Manually run tests after deployment

Solution

1. Step 1: Understand selective testing in CI

   To save time, CI can detect changed files and run only related tests.

2. Step 2: Identify the correct approach

   Use a script step that detects changed files and runs tests only on those describes using a script to detect changes and run targeted tests, which is efficient.

3. Final Answer:

   Use a script step that detects changed files and runs tests only on those -> Option B

4. Quick Check:

   Selective tests on changed files save CI time [OK]

Hint: Run tests only on changed files to save CI time [OK]

Common Mistakes:

• Running all tests every time wasting resources
• Disabling tests in CI
• Relying on manual testing after deployment