Test execution reporting in Testing Fundamentals - Test Execution Trace

Test Overview

This test checks if a simple login form accepts correct credentials and shows a welcome message. It verifies the login process and the final message display.

Test Code

Testing Fundamentals

def test_login_success():
    # Simulate opening the login page
    page = open_login_page()
    
    # Enter username and password
    page.find_element('username').send_keys('user1')
    page.find_element('password').send_keys('pass123')
    
    # Click the login button
    page.find_element('login_button').click()
    
    # Check if welcome message is displayed
    welcome_text = page.find_element('welcome_message').text
    assert welcome_text == 'Welcome, user1!', f"Expected welcome message not found, got: {welcome_text}"

Execution Trace - 8 Steps

Step	Action	System State	Assertion	Result
1	Test starts	Test environment initialized, ready to open login page	—	PASS
2	Open login page	Login page loaded with username, password fields and login button	Check page loaded successfully	PASS
3	Find username field and enter 'user1'	Username field filled with 'user1'	Verify username field contains 'user1'	PASS
4	Find password field and enter 'pass123'	Password field filled with 'pass123'	Verify password field contains 'pass123'	PASS
5	Find and click login button	Login button clicked, processing login	—	PASS
6	Find welcome message element	Welcome message element found on page	Verify welcome message text equals 'Welcome, user1!'	PASS
7	Assertion checks welcome message text	Welcome message text is 'Welcome, user1!'	Assert welcome message text is correct	PASS
8	Test ends	Test completed successfully	—	PASS

Failure Scenario

Failing Condition: Welcome message text does not match expected 'Welcome, user1!'

Execution Trace Quiz - 3 Questions

What is the first action performed in the test execution?

A Open login page

B Enter username

C Click login button

D Check welcome message

Key Result

Always verify the final expected output or message after performing actions to confirm the test scenario passed.

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