Why performance testing prevents bottlenecks in Testing Fundamentals - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the main goal of performance testing.

Testing Fundamentals

def performance_testing_goal():
    return "[1] bottlenecks before release"

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

ADelay

BIgnore

CIdentify

DCreate

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'Ignore' because it sounds like avoiding problems.

Choosing 'Create' thinking performance testing causes bottlenecks.

Performance testing helps identify bottlenecks early so they can be fixed before the software is released.

2fill in blank

medium

Complete the code to show what performance testing measures.

Testing Fundamentals

def measure_performance():
    return "[1] and response time"

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

ALoad

BColor

CSize

DSpeed

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'Color' or 'Size' which are unrelated to performance.

Choosing 'Speed' which is close but not the main measurement term.

Performance testing measures load (how much work the system can handle) and response time (how fast it reacts).

3fill in blank

hard

Fix the error in the function that simulates a bottleneck detection.

Testing Fundamentals

def detect_bottleneck(load):
    if load [1] 1000:
        return "Bottleneck detected"
    else:
        return "System OK"

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

A<=

B==

C<

D>

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<=' which detects low load instead of high.

Using '==' which only detects exactly 1000.

The function should detect a bottleneck when the load is greater than 1000, so the correct operator is >.

4fill in blank

hard

Fill both blanks to create a dictionary that maps test types to their focus areas.

Testing Fundamentals

test_focus = {
    "Load Testing": "[1]",
    "Stress Testing": "[2]"
}

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

Asystem capacity

Bbreaking point

Cuser interface

Dcode style

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing user interface or code style as focus areas for performance tests.

Load Testing focuses on system capacity, while Stress Testing focuses on the breaking point of the system.

5fill in blank

hard

Fill all three blanks to create a function that returns a report summary after performance testing.

Testing Fundamentals

def report_summary(errors, time, bottlenecks):
    return {
        "errors": [1],
        "total_time": [2],
        "bottlenecks_found": [3]
    }

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

Aerrors

Btime

Cbottlenecks

Dsummary

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'summary' which is not a parameter.

Mixing keys and variables incorrectly.

The function returns a dictionary with keys matching the parameters: errors, time, and bottlenecks.