Test execution reporting in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to print the test execution result as 'PASS' or 'FAIL'.

Testing Fundamentals

result = 'PASS' if tests_passed else [1]
print(result)

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

A'SKIP'

B'DONE'

C'FAIL'

D'ERROR'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'ERROR' or 'DONE' instead of 'FAIL' for failed tests.

Leaving the else part empty or incorrect.

The code sets result to 'PASS' if tests_passed is True; otherwise, it should be 'FAIL' to indicate test failure.

2fill in blank

medium

Complete the code to count how many tests passed from the list of test results.

Testing Fundamentals

passed_count = sum(1 for result in test_results if result == [1])

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

A'ERROR'

B'PASS'

C'SKIP'

D'FAIL'

Attempts:

3 left

💡 Hint

Common Mistakes

Counting 'FAIL' or other statuses instead of 'PASS'.

Using incorrect string quotes or case.

The code counts how many test results are equal to 'PASS', indicating successful tests.

3fill in blank

hard

Fix the error in the code that generates a summary report of test results.

Testing Fundamentals

summary = f"Total: {total_tests}, Passed: {passed}, Failed: {failed}, [1]: {skipped}"

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

ASkipped

BSkip

Cskip

DSKIP

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase or inconsistent capitalization for the label.

Using 'Skip' which is not the correct label.

The label in the summary string should be capitalized as 'Skipped' to match the report style.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that maps test names to their pass/fail status.

Testing Fundamentals

test_status = {test[1]: result == 'PASS' for test, result in test_results.items() if result [2] 'SKIP'}

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 '!=' to filter skipped tests.

Not converting test names to uppercase.

The first blank uses .upper() to standardize test names in uppercase. The second blank uses != to exclude skipped tests.

5fill in blank

hard

Fill all three blanks to create a filtered report dictionary with test names in lowercase, results, and only passed tests.

Testing Fundamentals

filtered_report = {test[1]: result for test, result in report.items() if result [2] 'PASS' and test [3] 'test_1'}

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

A.lower()

B==

C!=

D.capitalize()

Attempts:

3 left

💡 Hint

Common Mistakes

Using '!=' instead of '==' to check for passed tests.

Including 'test_1' instead of excluding it.

The test names are converted to lowercase with .lower(). The filter includes only tests where the result is 'PASS' (==) and excludes the test named 'test_1' (!=).

Practice

1. What is the main purpose of a test execution report in software testing?

easy

A. To write new test cases

B. To design the software architecture

C. To show which tests passed or failed

D. To deploy the software to users

Solution

1. Step 1: Understand the role of test execution reports

   Test execution reports summarize the results of running tests, showing which tests passed or failed.

2. Step 2: Eliminate unrelated options

   Writing test cases, designing software, and deploying are different activities not related to reporting test results.

3. Final Answer:

   To show which tests passed or failed -> Option C

4. Quick Check:

   Test execution report = pass/fail summary [OK]

Hint: Reports show pass/fail status clearly [OK]

Common Mistakes:

• Confusing report with test design
• Thinking reports deploy software
• Assuming reports write tests

2. Which of the following is a common element included in a test execution report?

easy

A. Test case names and their status

B. Source code of the application

C. User interface design sketches

D. Database schema diagrams

Solution

1. Step 1: Identify typical report contents

   Test execution reports usually list test case names and whether they passed or failed.

2. Step 2: Remove unrelated technical documents

   Source code, UI sketches, and database diagrams are not part of test execution reports.

3. Final Answer:

   Test case names and their status -> Option A

4. Quick Check:

   Report = test names + status [OK]

Hint: Reports list tests and results, not design files [OK]

Common Mistakes:

• Including source code in reports
• Confusing reports with design documents
• Expecting diagrams in test reports

3. Consider this test execution report snippet:
TestLogin: Passed
TestPayment: Failed
TestLogout: Passed
How many tests passed according to this report?

medium

A. 1

B. 2

C. 3

D. 0

Solution

1. Step 1: Count tests marked as Passed

   TestLogin and TestLogout are marked Passed, so 2 tests passed.

2. Step 2: Confirm no other Passed tests

   TestPayment is Failed, so it does not count.

3. Final Answer:

   2 -> Option B

4. Quick Check:

   Passed tests count = 2 [OK]

Hint: Count only 'Passed' labels in report [OK]

Common Mistakes:

• Counting failed tests as passed
• Misreading the report lines
• Counting total tests instead of passed

4. A test execution report shows:
TestA: Passed
TestB: Passed
TestC: Passed
TestD: Passed
But the tester says TestC actually failed. What is the most likely problem?

medium

A. TestD result was copied to TestC by mistake

B. TestC was never executed

C. All tests actually passed

D. The report was not updated after the test run

Solution

1. Step 1: Understand report and tester mismatch

   If the report shows TestC passed but tester says it failed, the report is outdated or incorrect.

2. Step 2: Evaluate other options

   TestC was likely executed but result not updated; copying results is less common; all passing contradicts tester.

3. Final Answer:

   The report was not updated after the test run -> Option D

4. Quick Check:

   Report outdated = wrong pass shown [OK]

Hint: Mismatch means report not refreshed [OK]

Common Mistakes:

• Assuming test was not run
• Believing all tests passed
• Ignoring report update timing

5. You have a test execution report with 10 tests: 7 passed, 2 failed, and 1 skipped. How should this report be presented to best help the development team?

hard

A. List all tests with status, highlight failed tests, and include error details

B. Show only passed tests to keep the report short

C. Exclude skipped tests and failed tests from the report

D. Report only the total number of tests run without details

Solution

1. Step 1: Identify useful report content

   Listing all tests with their status helps the team see the full picture.

2. Step 2: Emphasize failed tests and errors

   Highlighting failures and showing error details helps developers fix issues quickly.

3. Final Answer:

   List all tests with status, highlight failed tests, and include error details -> Option A

4. Quick Check:

   Complete, clear report = best for fixing bugs [OK]

Hint: Show all results, focus on failures with details [OK]

Common Mistakes:

• Hiding failed or skipped tests
• Giving only totals without details
• Ignoring error messages