Test execution reporting in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What does a test execution report typically include?

Imagine you ran a set of tests on a new app feature. What key information would you expect to see in the test execution report?

A A summary of passed and failed tests, error messages, and test duration

B Only the list of test names without results or errors

C User feedback comments unrelated to tests

D The source code of the application tested

💡 Hint

Think about what helps developers quickly understand test outcomes.

A test execution report shows which tests passed or failed, any error details, and how long tests took. This helps teams fix issues efficiently.

❓ Predict Output

intermediate

What is the output of this simple test report summary code?

Given this Python code that simulates a test report summary, what will it print?

Testing Fundamentals

tests = {'login': True, 'signup': False, 'logout': True}
passed = sum(1 for result in tests.values() if result)
failed = len(tests) - passed
print(f"Passed: {passed}, Failed: {failed}")

A Passed: 0, Failed: 3

B Passed: 1, Failed: 2

C Passed: 3, Failed: 0

D Passed: 2, Failed: 1

💡 Hint

Count how many tests have True as result.

Two tests passed (login and logout), one failed (signup). So output is Passed: 2, Failed: 1.

❓ assertion

advanced

Which assertion correctly checks that all tests passed?

You have a list of test results as booleans. Which assertion will confirm all tests passed?

Testing Fundamentals

test_results = [True, True, True, False]

A assert any(test_results) == True

B assert all(test_results) == True

C assert sum(test_results) == len(test_results)

D assert test_results.count(True) > 0

💡 Hint

Think about how to confirm every item is True.

Sum of True values equals the list length only if all are True. Option B correctly asserts all tests passed.

🔧 Debug

advanced

Why does this test report code raise an error?

Look at this code snippet that tries to print test results. Why does it raise an error?

Testing Fundamentals

test_results = {'test1': 'pass', 'test2': 'fail'}
print(f"Failures: {test_results['fail']}")

A KeyError because 'fail' is not a key in the dictionary

B SyntaxError due to missing colon in dictionary

C TypeError because dictionary values are strings

D No error, prints 'Failures: fail'

💡 Hint

Check if the key used in print exists in the dictionary.

The dictionary keys are 'test1' and 'test2'. Accessing 'fail' key causes KeyError.

❓ framework

expert

In a test execution report, which framework feature helps group tests by status automatically?

Which feature of modern test frameworks automatically organizes test results into passed, failed, and skipped groups in reports?

A Using print statements to show test status

B Manual logging inside each test function

C Test result listeners or reporters that categorize tests by outcome

D Writing separate test files for passed and failed tests

💡 Hint

Think about automatic features that help organize test outcomes.

Test result listeners or reporters in frameworks automatically group tests by their status, making reports clear and easy to read.

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