Build Run Report – Test Details

The Build Run - Test page gives you a comprehensive look at individual test cases. Let's break down the key sections.

At the top, you’ll find key details about this particular Build Run:

• Build Name: High-Level Automation Suite Regression 4.


• Tester: Rahul Sharma (the person who executed this build).
• Execution Date: Nov 19, 2024, at 10:21 AM.
• Build Duration: This test run took 59 minutes and 56 seconds to complete.

Below this, you can see a summary of the overall results for this suite, including:

• Total Passed: Green represents tests that passed successfully.
• Total Failed: Red shows tests that failed.
• Skipped Tests: Yellow indicates tests that were skipped.
• Ignored Tests: Grey represents tests that were ignored.

Under the summary section, you will find the list of test cases included in this build run. Each test case is listed with the following details:

• Test Name: The name and purpose of the test (for example, "Verify Duplicate Rule for Warning [QAA-TC-479]").
• Execution Time: The duration it took for each test to run. For instance, one test may have taken 3 minutes and 33 seconds, while another may have completed in just 1 minute and 44 seconds.

Each test case result is displayed with a color-coded status indicator in-front of it:

• Green: Indicates that the test passed successfully.
• Red: Shows that the test failed.

For example, the test case "Verify Dependency Rule Change Scenario [QAA-TC-431]" is marked with a red icon, indicating a failure, while "Verify Delta Sync Schedule Functionality [QAA-TC-568]" is marked in green, meaning it passed.

Each failed test has a status label marked next to it. This label is used to identify tests that need further investigation. You’ll often find this next to failed or problematic tests that require additional attention from the QA team.

Here are some key examples from the test case list:

• Failed Test Case:
  • Name: Verify Duplicate Rule for Warning [QAA-TC-479].
  • Tag: Product Bug.
  • Execution Time: 1 minute and 44 seconds.
• Test Case with Environment Issue:
  • Name: Verify Data Restrictions Only Allow Extensions to New Org Levels Exactly One [QAA-TC-558].
  • Tag: Environment Issue.
  • Execution Time: 4 minutes and 5 seconds.
• Automation Bug Example:
  • Name: To Verify Restrictions for Header, Hierarchy and Grid [QAA-TC-521].
  • Tag: Automation Bug.
  • Execution Time: 1 minute and 44 seconds.
• To Investigate Case:
  • Name: Verifying Functional Location Creation and Editing [QAA-TC-401].
  • Tag: To Investigate.
  • Execution Time: 3 minutes and 01 second
• No Defect Case:
• Name: Validation using Daxe [QAA-TC-540].
• Tag: No Defect.
• Execution Time: 3 minutes and 33 second

By expanding any test case in the list, you can view more detailed information about that specific test, like this:

When a test case fails during a build run, TestReport.io provides a detailed breakdown of the failure, allowing you to investigate and resolve issues efficiently. Let’s go through the key sections of the..

At the top, you’ll see the basic information about the test case:

• Test Case Name: "VerifyWebsite1"
• Execution Time: The test ran for 4 seconds before it failed.
• Test Status: The test is marked as Failed with the status label as TO INVESTIGATE.

This section shows the detailed Result Output of the test case:

• Screen shot with Failed page URL: You can see the failed page screenshot and URL of the failed page. By clicking on the screenshot you can download it.

This section provides a brief description of what the test case was attempting to do when it failed. In this case, it shows:

4. Exception Name

This section highlights the specific exception that caused the test to fail. In this case, the failure was due to:

• Exception Name: org.openqa.selenium.TimeoutException

This indicates that a timeout occurred during the test run, preventing it from completing successfully.

This section provides more detailed information about the exception:

This helps you understand exactly why the test failed, providing clues for resolving the issue. 

In this section, you’ll find the Exception Backtrace, which gives you the complete error trace:

• This trace shows the sequence of steps the test took before encountering the exception.
• It lists the exact method calls and scripts that led to the failure, making it easier for you to pinpoint where things went wrong.

On the right-hand side of the page, you have options for Defect Management:

• Select Defect Category: You can classify the defect into one of several categories such as Product Bug, Automation Bug, Environment Issue, or mark it as No Defect.

If integrated with Jira, you can immediately create a ticket for this defect by selecting the issue type and adding a description.

This allows the issue to be tracked and resolved in a structured way. This integration makes it easy to report and manage defects directly from TestReport.io

At the bottom right, you have the ability to Post Comments:

• You can add comments about the failure, provide feedback, or communicate with team members about the next steps.
• The comment section is rich-text enabled, allowing you to format your notes for clarity.

This collaborative feature ensures that the whole team is on the same page when investigating and fixing test case failures.