Continuous Integration testing in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Continuous Integration (CI) testing?

Continuous Integration testing is the practice of automatically running tests every time code changes are added to a shared project. It helps catch errors early and keeps the software working well.

beginner

Why is Continuous Integration testing important?

It finds problems quickly, so developers can fix them before they grow. This saves time and makes the software more reliable.

beginner

Name a common tool used for Continuous Integration testing.

Jenkins is a popular tool that helps run tests automatically when code changes happen.

intermediate

What types of tests are usually run in Continuous Integration?

Unit tests and integration tests are commonly run to check small parts and how they work together.

intermediate

How does Continuous Integration testing improve teamwork?

It helps everyone see if their code works well with others quickly, reducing conflicts and confusion.

What triggers tests in Continuous Integration testing?

A Every time code is changed and added to the shared project

B Only when a developer asks for it

C Once a month

D When the software is released

In CI testing, tests run automatically whenever code changes are added to the shared project.

Which of these is NOT a benefit of Continuous Integration testing?

A Making software slower

B Finding bugs early

C Improving code quality

D Helping teamwork

CI testing helps improve speed and quality, it does not make software slower.

Which test type is commonly run in Continuous Integration?

A No tests

B Manual exploratory tests

C Performance tests only

D Unit tests

Unit tests are small tests run automatically in CI to check individual parts of the code.

What is a popular tool used for Continuous Integration?

A Excel

B Jenkins

C Photoshop

D Slack

Jenkins is a widely used tool to automate CI testing.

How does Continuous Integration testing help developers work together?

A By making everyone work alone

B By stopping all code changes

C By showing if code works well with others quickly

D By hiding errors from the team

CI testing helps teams by quickly showing if new code fits well with existing code.

Explain what Continuous Integration testing is and why it is useful.

Think about how testing every change helps the team.

Describe common tests run during Continuous Integration and their purpose.

Focus on test types and why they run in CI.

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