Continuous Delivery testing in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the main goal of Continuous Delivery testing.

Testing Fundamentals

def continuous_delivery_goal():
    return "[1]"

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

ADeliver software changes quickly and safely

BWrite only manual tests

CAvoid automation

DDelay releases for months

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing options that suggest avoiding automation or delaying releases.

The main goal of Continuous Delivery testing is to deliver software changes quickly and safely by automating tests and deployment.

2fill in blank

medium

Complete the code to identify the type of tests most important in Continuous Delivery pipelines.

Testing Fundamentals

important_tests = "[1]"

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

AAutomated unit and integration tests

BOnly performance tests

CManual exploratory tests

DAd-hoc tests

Attempts:

3 left

💡 Hint

Common Mistakes

Selecting manual or ad-hoc tests which slow down the pipeline.

Automated unit and integration tests are crucial in Continuous Delivery to ensure fast and reliable feedback.

3fill in blank

hard

Fix the error in the test automation step to correctly trigger tests in the pipeline.

Testing Fundamentals

def run_tests():
    if not [1]:
        print("Tests failed")
    else:
        print("Tests passed")

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

Atests_failed()

Btests_running()

Ctests_skipped()

Dtests_passed()

Attempts:

3 left

💡 Hint

Common Mistakes

Using tests_failed() which might not exist or invert logic incorrectly.

The condition should check if tests_passed() returns False to print 'Tests failed'. Using tests_passed() correctly reflects test results.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that maps test names to their pass status, filtering only passed tests.

Testing Fundamentals

passed_tests = {test[1]: status for test, status in test_results.items() if status [2] True}

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

A.upper()

B==

C!=

D.lower()

Attempts:

3 left

💡 Hint

Common Mistakes

Using '!=' instead of '==' in the filter condition.

Not applying a string method to test names.

The comprehension converts test names to uppercase and filters tests where status is True (passed).

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps test names in lowercase to their duration, filtering tests longer than 5 seconds.

Testing Fundamentals

long_tests = {test[1]: duration for test, duration in test_durations.items() if duration [2] 5 and test[3]

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

A.lower()

B>

Cisalpha()

D.upper()

Attempts:

3 left

💡 Hint

Common Mistakes

Using '.upper()' instead of '.lower()' for test names.

Using '<' instead of '>' for duration comparison.

The comprehension converts test names to lowercase, filters durations greater than 5, and includes only tests with alphabetic names.

Practice

1. What is the main goal of Continuous Delivery testing in software development?

easy

A. To delay testing until after deployment

B. To write manual test cases for every feature

C. To ensure the software is always in a releasable state

D. To test only the user interface manually

Solution

1. Step 1: Understand Continuous Delivery testing purpose

   Continuous Delivery testing aims to keep software ready to release at any time by running automated tests frequently.

2. Step 2: Compare options with the goal

   Only To ensure the software is always in a releasable state matches this goal. Other options describe manual or delayed testing, which contradict Continuous Delivery principles.

3. Final Answer:

   To ensure the software is always in a releasable state -> Option C

4. Quick Check:

   Continuous Delivery = Always releasable software [OK]

Hint: Continuous Delivery means software is always ready to release [OK]

Common Mistakes:

• Thinking manual testing is the main focus
• Believing testing happens only after deployment
• Confusing Continuous Delivery with manual UI testing

2. Which of the following is the correct syntax to define a simple automated test step in a Continuous Delivery pipeline script?

easy

A. run_tests script pytest tests/

B. run_tests: script: pytest tests/

C. run_tests: pytest tests/

D. run_tests = pytest tests/

Solution

1. Step 1: Identify correct YAML syntax for pipeline steps

   Pipeline scripts often use YAML format where keys have colons and nested keys are indented, e.g., 'run_tests: script: pytest tests/'.

2. Step 2: Check each option's syntax

   run_tests: script: pytest tests/ uses correct YAML with colon and nested script key. Options A, C, and D miss colons or use invalid assignment.

3. Final Answer:

   run_tests: script: pytest tests/ -> Option B

4. Quick Check:

   YAML step syntax = run_tests: script: command [OK]

Hint: YAML keys need colons and proper indentation [OK]

Common Mistakes:

• Omitting colons in YAML keys
• Using equal signs instead of colons
• Not indenting nested keys properly

3. Consider this simplified test pipeline code snippet:

tests = ['unit', 'integration', 'e2e']
results = []
for test in tests:
    if test == 'integration':
        results.append('fail')
    else:
        results.append('pass')
print(results)

What will be the output after running this code?

medium

A. ['pass', 'fail', 'pass']

B. ['fail', 'fail', 'fail']

C. ['pass', 'pass', 'fail']

D. ['fail', 'pass', 'fail']

Solution

1. Step 1: Analyze the loop and conditions

   The list 'tests' has three items: 'unit', 'integration', 'e2e'. The loop checks if the test is 'integration' to append 'fail', else 'pass'.

2. Step 2: Determine results for each test

   'unit' -> not 'integration' -> 'pass'
   'integration' -> equals 'integration' -> 'fail'
   'e2e' -> not 'integration' -> 'pass'

3. Final Answer:

   ['pass', 'fail', 'pass'] -> Option A

4. Quick Check:

   Only 'integration' test fails [OK]

Hint: Only 'integration' test appends 'fail' [OK]

Common Mistakes:

• Assuming all tests pass
• Confusing the condition logic
• Mixing order of results

4. A Continuous Delivery pipeline script has this step:

test_step:
  script:
    - pytest --maxfail=1 --disable-warnings
    - echo "Tests completed"

However, the pipeline does not stop on the first test failure as expected. What is the likely cause?

medium

A. pytest does not support the --maxfail option

B. The --maxfail=1 option is invalid and ignored

C. The echo command causes the pipeline to stop early

D. The pipeline runs all script commands regardless of failure by default

Solution

1. Step 1: Understand pipeline script behavior

   In many CI/CD tools, all commands under 'script' run sequentially even if one fails, unless configured to stop on failure.

2. Step 2: Analyze the options and commands

   --maxfail=1 is a valid pytest option to stop pytest early, but the pipeline still runs the next command 'echo'. So the pipeline itself does not stop on failure automatically.

3. Final Answer:

   The pipeline runs all script commands regardless of failure by default -> Option D

4. Quick Check:

   Pipeline runs all script lines unless configured to stop [OK]

Hint: Pipeline runs all script commands unless told to stop [OK]

Common Mistakes:

• Thinking pytest controls pipeline flow
• Believing echo causes failure
• Assuming invalid option causes issue

5. In a Continuous Delivery pipeline, you want to run tests only on changed files to speed up feedback. Which approach best achieves this?

hard

A. Use a script to detect changed files and run tests related to those files

B. Run all tests every time regardless of changes

C. Manually select tests to run after each commit

D. Disable automated tests and rely on manual testing

Solution

1. Step 1: Understand test optimization in Continuous Delivery

   Running all tests every time can be slow. Detecting changed files and running only related tests speeds feedback.

2. Step 2: Evaluate options for automation and speed

   Use a script to detect changed files and run tests related to those files automates detection and selective testing, fitting Continuous Delivery goals. Options B, C, and D are inefficient or manual.

3. Final Answer:

   Use a script to detect changed files and run tests related to those files -> Option A

4. Quick Check:

   Selective testing on changes = faster feedback [OK]

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

Common Mistakes:

• Running all tests every time without optimization
• Relying on manual test selection
• Skipping automated tests entirely