Continuous Integration testing in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Continuous Integration (CI)

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

A To automatically merge all code changes without testing

B To manually test software after all features are complete

C To frequently integrate code changes and run automated tests to detect errors early

D To deploy software directly to production without review

💡 Hint

Think about how CI helps catch problems quickly by running tests often.

Continuous Integration means developers frequently merge code changes into a shared repository. Automated tests run on these changes to find errors early, improving software quality and reducing integration problems.

❓ Predict Output

intermediate

CI Pipeline Test Result Interpretation

Given this simplified CI pipeline test output, what is the final test result?

Test Suite: User Login Tests
- Test 1: Passed
- Test 2: Passed
- Test 3: Failed
- Test 4: Skipped

A All tests passed successfully

B Tests failed because at least one test failed

C Tests passed because skipped tests do not count

D Tests are inconclusive due to skipped tests

💡 Hint

Consider how a single failed test affects the overall result.

In CI, if any test fails, the overall test result is considered failed. Skipped tests do not cause failure but do not count as passed either.

❓ assertion

advanced

Correct Assertion for CI Test Automation

Which assertion correctly verifies that a function getBuildStatus() returns the string "SUCCESS" in a CI test script?

Testing Fundamentals

status = getBuildStatus()

A assert status == "SUCCESS"

B assert status = "SUCCESS"

C assertEqual(status, "SUCCESS")

D assert status.equals("SUCCESS")

💡 Hint

Remember the correct syntax for assertions in Python.

In Python, assert followed by a condition checks if it is true. Option A uses correct syntax. Option A uses assignment instead of comparison. Option A is a unittest method but not valid standalone. Option A is Java syntax.

🔧 Debug

advanced

Debugging a Failing CI Test

A CI test script fails with this error: TimeoutError: Test exceeded time limit. What is the most likely cause?

A The test is stuck or running longer than allowed

B The test passed but the report is incorrect

C The CI server is offline

D The test code has a syntax error

💡 Hint

Think about what a timeout error means in testing.

A TimeoutError means the test took too long to finish, possibly due to an infinite loop or waiting for a resource. It is not a syntax error or server offline issue.

❓ framework

expert

Choosing the Best CI Tool Feature

Which feature is most important for a CI tool to support efficient parallel test execution?

A No integration with version control systems

B Ability to run tests sequentially on a single machine

C Manual triggering of tests only

D Support for distributed test runners across multiple machines

💡 Hint

Think about how to speed up testing by running many tests at once.

Parallel test execution requires running tests on multiple machines or environments simultaneously. Support for distributed test runners enables this. Sequential runs or manual triggers slow down testing. Integration with version control is essential but not directly related to parallelism.

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