Why Continuous Integration testing in Testing Fundamentals? - Purpose & Use Cases

The Big Idea

What if your code could test itself every time you save it, catching bugs before they cause trouble?

The Scenario

Imagine a team of developers working on a big project. Every day, they write new code and change old code. Without automation, they have to test everything by hand each time someone adds something new. This means running tests one by one, checking if the app still works, and hoping they didn't break anything.

The Problem

Manual testing is slow and tiring. It takes a lot of time to run all tests after every change. People can miss bugs because they get tired or rush. Also, if many developers work together, it's hard to keep track of which changes caused problems. This leads to delays and unhappy users.

The Solution

Continuous Integration testing automatically runs all tests every time a developer adds new code. It quickly checks if the new code works well with the old code. This way, bugs are caught early, and the team knows right away if something breaks. It saves time and keeps the project healthy.

Before vs After

✗ Before

Developer runs tests manually after coding:
run test1
run test2
run test3

✓ After

CI system runs tests automatically on every code change:
trigger CI pipeline
run all tests
report results

What It Enables

Continuous Integration testing makes it possible to deliver software faster and with fewer bugs by catching problems immediately after code changes.

Real Life Example

A team building a shopping app uses Continuous Integration testing. Every time a developer adds a new feature, the system runs tests automatically. If a test fails, the team fixes it before the app reaches customers, ensuring a smooth shopping experience.

Key Takeaways

Manual testing after every change is slow and error-prone.

Continuous Integration testing automates running tests on every code update.

This helps teams find and fix bugs early, speeding up delivery.

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