Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

How to View Test Results in Allure Report

his tutorial will guide you through the process of navigating an Allure report to analyze test results, including passed, failed, broken, and skip tests, and how to access error logs and screenshots.

📺 Step 1: Open the Allure Report

  1. In the Slack message, you’ll see a summary of the test results. Shows the distribution of results:
    1. Passed: Tests that executed successfully.
    2. Failed: Tests that encountered errors or assertion failures.
    3. Skipped: Tests that were skipped during execution.
    4. Broken: Tests that failed due to unexpected errors.
  2. Click the :bar_chart: View Report link. This will redirect you to the Allure report in your browser.

👥 Step 2: View Detailed Test Results

  1. Click on the "Behaviors" or "Suites" tab in the left-hand menu.
    • Behaviors: Groups tests by features or stories (if configured).
    • Suites: Groups tests by test suites or classes.
  2. Expand the test suite or behavior to see individual test cases.
  3. Click on a specific test case to view its details.

📝 Step 3: Analyze Failed or Broken Tests

For failed or broken tests, follow these steps to debug:

  1. In the test case details, scroll down to the "Test Body" section.
  2. Look for the "Steps" section. Each step will show:
    • The action performed.
    • The result (e.g., passed, failed).
  3. If a step failed, you’ll see the error message and stack trace under the step.

✅ Step 4: View Screenshots or Attachments

If the tests captured screenshots or other attachments (e.g., logs, JSON files), you can view them in the report:

  1. In the test case details, scroll down to the "Attachments" section.
  2. Click on the attachment (e.g., a screenshot) to view it.
    • Screenshots are especially useful for debugging UI test failures.

🔑 Need Help?

If you have any questions or need further assistance, feel free to reach out to the QA team. Happy debugging! 🚀