Pipeline stages and test gates in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Pipeline Stages

Which of the following best describes the purpose of the build stage in a software pipeline?

A It monitors application performance after deployment.

B It deploys the application to the production environment.

C It runs automated tests to verify code correctness.

D It compiles the source code and creates executable artifacts.

💡 Hint

Think about what happens before testing and deployment.

The build stage compiles the source code and produces executable files or packages. This is necessary before running tests or deploying.

❓ assertion

intermediate

Test Gate Logic in Pipeline

In a pipeline, a test gate is configured to fail the pipeline if any unit test fails. Given the following test results, what will be the pipeline outcome?

Unit tests passed: 95/100
Integration tests passed: 50/50

A Pipeline passes because most unit tests passed.

B Pipeline passes because integration tests passed.

C Pipeline fails because some unit tests failed.

D Pipeline fails because integration tests are mandatory.

💡 Hint

Test gates often require 100% pass rate for critical tests.

The test gate is set to fail if any unit test fails. Since 5 unit tests failed, the pipeline fails regardless of integration test results.

❓ Predict Output

advanced

Pipeline Stage Execution Order

Consider this simplified pipeline stage execution code snippet:

stages = ['build', 'test', 'deploy']
results = []
for stage in stages:
    if stage == 'test':
        results.append('test skipped')
        break
    results.append(stage + ' completed')
print(results)

What is the output after running this code?

A ['build completed', 'test skipped']

B ['build completed']

C ['build completed', 'test completed', 'deploy completed']

D ['test skipped']

💡 Hint

Note the break statement inside the loop.

The loop appends 'build completed', then encounters 'test', appends 'test skipped', and breaks the loop, so 'deploy' is not processed.

🔧 Debug

advanced

Debugging a Test Gate Failure

A pipeline test gate is supposed to block deployment if code coverage is below 80%. The following code snippet is used to check coverage:

coverage = 78
if coverage < 80:
    print('Pass test gate')
else:
    print('Fail test gate')

Why does the pipeline allow deployment even when coverage is 78%?

A Because 78 is less than 80, so it should fail but the code logic is reversed.

B Because the condition uses '>' instead of '>=' causing 80% to fail but 78% to pass.

C Because the condition only passes if coverage is strictly greater than 80, so 78 fails and blocks deployment.

D Because the code prints 'Fail test gate' when coverage is below 80%, so deployment is blocked.

💡 Hint

Check the logic of the if-else condition carefully.

The if condition is reversed: coverage=78 <80 is true, so it prints 'Pass test gate', allowing deployment. It should print 'Fail test gate' when coverage is below 80%.

❓ framework

expert

Designing a Test Gate for Multiple Criteria

You want to design a test gate that blocks deployment if any of these conditions fail:

• All unit tests pass
• Code coverage is at least 85%
• No critical bugs are open

Which of the following pseudocode snippets correctly implements this test gate?

unit_tests_passed = True
coverage = 87
critical_bugs_open = 0
if ???:
    print('Pass test gate')
else:
    print('Fail test gate')

A if unit_tests_passed or coverage >= 85 or critical_bugs_open == 0:

B if unit_tests_passed and coverage >= 85 and critical_bugs_open == 0:

C if not unit_tests_passed and coverage < 85 and critical_bugs_open > 0:

D if unit_tests_passed and coverage > 85 and critical_bugs_open != 0:

💡 Hint

All conditions must be true to pass the gate.

Using 'and' ensures all conditions must be met. 'Or' would allow passing if any single condition is true, which is incorrect.