Test execution reporting in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is test execution reporting?

Test execution reporting is the process of collecting and presenting the results of running tests. It shows which tests passed, failed, or were skipped, helping teams understand software quality.

beginner

Name three common elements included in a test execution report.

1. Test case names or IDs
2. Test results (pass/fail/skip)
3. Execution time or duration
These help track what was tested and how it performed.

beginner

Why is test execution reporting important in software development?

It provides clear feedback on software quality, helps find bugs early, supports decision-making, and improves communication among team members.

intermediate

What is the difference between a summary report and a detailed test execution report?

A summary report shows overall results like total tests passed or failed. A detailed report includes individual test case results, error messages, and logs.

intermediate

How can automation tools help with test execution reporting?

Automation tools run tests and generate reports automatically. This saves time, reduces errors, and provides consistent, easy-to-read results.

What does a test execution report primarily show?

A User manuals

B How to write test cases

C The software's source code

D Which tests passed or failed

Test execution reports focus on showing the results of tests, mainly which passed or failed.

Which of these is NOT usually part of a test execution report?

A Test case names

B Developer's salary

C Execution time

D Test results

Developer's salary is unrelated to test execution reporting.

Why is it helpful to have detailed error messages in a test report?

A To confuse testers

B To decorate the report

C To understand why a test failed

D To increase report size

Error messages help testers quickly find and fix problems.

Automation tools in test reporting help by:

A Running tests and creating reports automatically

B Writing code for developers

C Designing user interfaces

D Managing project budgets

Automation tools speed up testing and reporting by doing these tasks automatically.

A summary test report usually includes:

A Overall pass/fail counts

B Detailed logs of every test step

C Source code changes

D User feedback

Summary reports give a quick overview of test results, like how many tests passed or failed.

Explain what information you would expect to find in a test execution report and why it is useful.

Think about what helps a team understand how well the software works after testing.

Describe how automated test execution reporting improves the testing process.

Consider how machines can help testers by doing repetitive tasks.

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