Shift-left testing in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the main goal of shift-left testing.

Testing Fundamentals

shift_left_testing_goal = "Detect defects [1] in the development process"

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

Aduring maintenance

Blate

Cafter deployment

Dearly

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'late' because testing is often done after coding.

Confusing shift-left with testing after deployment.

Shift-left testing means finding defects early in the development process to save time and cost.

2fill in blank

medium

Complete the code to show which phase shift-left testing emphasizes.

Testing Fundamentals

shift_left_focus = "[1] testing"

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

Aacceptance

Bsystem

Cunit

Dperformance

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing system testing which happens later.

Confusing acceptance testing with early testing.

Shift-left testing focuses on unit testing early in development to catch bugs quickly.

3fill in blank

hard

Fix the error in the code that describes shift-left testing benefits.

Testing Fundamentals

def benefits_of_shift_left():
    return "Reduces cost and time by finding bugs [1]"

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

Aearly

Blate

Cnever

Drandomly

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'late' which increases cost.

Selecting 'never' which is incorrect.

Finding bugs early reduces cost and time in software development.

4fill in blank

hard

Fill both blanks to complete the dictionary that maps testing phases to shift-left focus.

Testing Fundamentals

shift_left_map = {"[1]": "early testing", "[2]": "later testing"}

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

Aunit

Bintegration

Csystem

Dacceptance

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up system and acceptance testing.

Choosing integration for early testing instead of unit.

Unit testing is done early, system testing is done later in the process.

5fill in blank

hard

Fill all three blanks to complete the code that filters tests suitable for shift-left testing.

Testing Fundamentals

suitable_tests = [test for test in all_tests if test.type == '[1]' and test.phase [2] 'development' and test.automated == [3]]

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

Aunit

B==

CTrue

D!=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '!=' instead of '==' for phase comparison.

Setting automated to False which is not typical for shift-left.

Shift-left testing uses unit tests that run during development and are automated (True).