Test prioritization in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to print the highest priority test case first.

Testing Fundamentals

test_cases = [('Login', 3), ('Signup', 1), ('Checkout', [1])]
sorted_tests = sorted(test_cases, key=lambda x: x[1])
print(sorted_tests[0][0])

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

A2

B5

C1

D4

Attempts:

3 left

💡 Hint

Common Mistakes

Using a priority number that is too high or too low, causing wrong order.

Not understanding that lower numbers mean higher priority.

The priority number 2 is used to correctly order the 'Checkout' test case so that sorting by priority works as expected.

2fill in blank

medium

Complete the code to filter only high priority tests (priority less than 3).

Testing Fundamentals

test_cases = [('Login', 3), ('Signup', 1), ('Checkout', 2)]
high_priority = [test for test in test_cases if test[1] [1] 3]
print(high_priority)

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

A>

B==

C<

D>=

Attempts:

3 left

💡 Hint

Common Mistakes

Using > instead of < causing wrong tests to be selected.

Using equality operator which only selects priority exactly 3.

We use < 3 to select tests with priority less than 3, meaning higher priority tests.

3fill in blank

hard

Fix the error in the code to correctly sort tests by priority ascending.

Testing Fundamentals

test_cases = [('Login', 3), ('Signup', 1), ('Checkout', 2)]
sorted_tests = sorted(test_cases, key=lambda x: x[[1]])
print([test[0] for test in sorted_tests])

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

A1

B2

C0

D-1

Attempts:

3 left

💡 Hint

Common Mistakes

Using index 0 which sorts by test name, not priority.

Using index 2 which is out of range and causes error.

The priority is the second element in each tuple, so index 1 is used as the key for sorting.

4fill in blank

hard

Fill both blanks to create a dictionary of test names and their priorities, filtering only tests with priority {{BLANK_1}} 2 and {{BLANK_2}} 4.

Testing Fundamentals

test_cases = [('Login', 3), ('Signup', 1), ('Checkout', 2), ('Profile', 4)]
filtered = {test[0]: test[1] for test in test_cases if test[1] [1] 2 and test[1] [2] 4}
print(filtered)

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

A>=

B<=

C==

D!=

Attempts:

3 left

💡 Hint

Common Mistakes

Using equality operators which select only exact values.

Using wrong comparison directions causing empty results.

We want tests with priority greater or equal to 2 and less or equal to 4, so >= and <= are used.

5fill in blank

hard

Fill all three blanks to create a list of test names with priority {{BLANK_1}} 3, sorted by priority {{BLANK_2}} and then by name {{BLANK_3}}.

Testing Fundamentals

test_cases = [('Login', 3), ('Signup', 1), ('Checkout', 3), ('Profile', 2)]
sorted_tests = sorted(test_cases, key=lambda x: (x[1], x[0]), reverse=[1])
result = [test[0] for test in sorted_tests if test[1] [2] 3]
print(result)

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

AFalse

BTrue

C==

D<

Attempts:

3 left

💡 Hint

Common Mistakes

Using reverse=True which sorts descending, not desired here.

Using wrong comparison operators causing wrong filtering.

We sort ascending (reverse=False), filter tests with priority equal to 3 (== 3), and sort names ascending (<).

Practice

1. What is the main goal of test prioritization in software testing?

easy

A. To run the most important tests first to find bugs faster

B. To run all tests in alphabetical order

C. To skip tests that are easy to pass

D. To run tests only after the software is released

Solution

1. Step 1: Understand the purpose of test prioritization

   Test prioritization means deciding which tests to run first based on their importance or likelihood to find bugs.

2. Step 2: Identify the correct goal

   The goal is to save time and find bugs faster by running important tests first.

3. Final Answer:

   To run the most important tests first to find bugs faster -> Option A

4. Quick Check:

   Test prioritization = run important tests first [OK]

Hint: Remember: prioritize tests that catch bugs quickly [OK]

Common Mistakes:

• Thinking test order is random
• Believing all tests have equal priority
• Skipping tests without reason

2. Which of the following is a good factor to consider when prioritizing tests?

easy

A. The number of testers available

B. The color of the test case document

C. The font size used in test descriptions

D. Recent changes in the code

Solution

1. Step 1: Identify relevant factors for test prioritization

   Good factors include recent code changes, past failures, and test importance.

2. Step 2: Choose the factor related to code changes

   Recent changes in code can introduce new bugs, so tests covering those areas should run first.

3. Final Answer:

   Recent changes in the code -> Option D

4. Quick Check:

   Prioritize tests by recent code changes [OK]

Hint: Focus on code changes, not irrelevant details [OK]

Common Mistakes:

• Choosing unrelated factors like document color
• Ignoring recent code updates
• Confusing tester count with test priority

3. Given the following test cases and their last failure dates, which test should be run first based on test prioritization?

Test A: failed 2 days ago
Test B: passed last run
Test C: failed 10 days ago
Test D: never failed

medium

A. Test B

B. Test D

C. Test A

D. Test C

Solution

1. Step 1: Analyze failure recency

   Tests that failed recently are more likely to find bugs again, so they get higher priority.

2. Step 2: Compare failure dates

   Test A failed 2 days ago, which is more recent than Test C (10 days ago). Tests B and D did not fail recently.

3. Final Answer:

   Test A -> Option C

4. Quick Check:

   Run tests with recent failures first [OK]

Hint: Pick tests with the most recent failures first [OK]

Common Mistakes:

• Choosing tests that never failed
• Ignoring failure dates
• Picking tests that passed last run

4. You have a test suite with 4 tests. The priority order should be based on recent code changes and past failures. The current order is:

1. Test X (no recent changes, no failures)
2. Test Y (recent changes, no failures)
3. Test Z (no recent changes, failed last run)
4. Test W (recent changes, failed last run)

Which test should be run first to follow best test prioritization?

medium

A. Test W

B. Test X

C. Test Z

D. Test Y

Solution

1. Step 1: Combine recent changes and past failures

   Tests with both recent changes and past failures have highest priority.

2. Step 2: Identify test with both factors

   Test W has recent changes and failed last run, so it should run first.

3. Final Answer:

   Test W -> Option A

4. Quick Check:

   Prioritize tests with recent changes and failures [OK]

Hint: Pick tests with both recent changes and failures first [OK]

Common Mistakes:

• Ignoring one of the prioritization factors
• Running tests without recent changes first
• Choosing tests that never failed

5. A team has 5 tests with these details:

Test 1: covers critical feature, no recent changes, failed last run
Test 2: covers minor feature, recent changes, passed last run
Test 3: covers critical feature, recent changes, passed last run
Test 4: covers minor feature, no recent changes, never failed
Test 5: covers critical feature, recent changes, failed last run

Which order best follows test prioritization principles?

hard

A. Test 1, Test 5, Test 3, Test 2, Test 4

B. Test 5, Test 1, Test 3, Test 2, Test 4

C. Test 5, Test 3, Test 1, Test 2, Test 4

D. Test 4, Test 2, Test 3, Test 1, Test 5

Solution

1. Step 1: Identify highest priority tests

   Tests covering critical features with recent changes and failures have highest priority. Test 5 fits all three.

2. Step 2: Order remaining tests by priority

   Next is Test 1 (critical, failed but no recent changes), then Test 3 (critical, recent changes, passed), followed by Test 2 and Test 4 (minor features, lower priority).

3. Final Answer:

   Test 5, Test 1, Test 3, Test 2, Test 4 -> Option B

4. Quick Check:

   Prioritize critical, recent changes, failures first [OK]

Hint: Order by criticality, recent changes, then failures [OK]

Common Mistakes:

• Ignoring feature criticality
• Not combining multiple factors
• Running low priority tests first