ScriptlessAutomation
  • 👋Welcome to Scriptless Automation
  • Discover More About Automation
    • ⚙️Automation platform intro
    • 💡Advantages of Scriptless Automation
    • 🚀Release Notes
      • 📖Open Code
      • 📕License Code
  • Product tools
    • 📪Pre-request Tools
    • 🔧Project Dependencies
  • Automation Architecture
    • 🎨Flow diagram
  • Get Started
    • 🛠️Start with Automation
    • 📖Open Code Automation
      • 🌏Web Automation
      • ↔️API Automation
    • 🏢Maven Configuration
    • 🗜️Setting Up Maven Project in IntelliJ IDEA
    • 🎛️Scriptless Config
      • 🕸️BrowserConfiguration
        • chrome.properties
      • 👥CommunicationConfiguration
        • SlackConfiguration.properties
      • 📧MailConfiguration
        • gmailCredentials.properties
      • 🛂ReportConfiguration
        • extentReportConfiguration.properties
      • 🕵️TestManagementConfiguration
        • testRail.properties
        • zephyrscale.properties
        • testiny.properties
      • ⚙️testNgConfiguration.properties
    • 🍱TestData Configuration
    • 👨‍💼Gherkin Language and Scriptless Automation Framework
  • Automation Import Notes
    • 🎨Points to Remember
  • Automation Platforms
    • 👾ScriptlessApi Automation
      • 🖊️Introduction
      • 🗜️Api Automation Setup
      • 🔃Supported API Request Types
      • 🪧API Automation Template
      • 📚Example of API Requests
        • ⬇️GET
        • ↕️POST
        • ⤵️PUT
        • ❌DELETE
      • 🎯API Response Validation
      • 👨‍👦API Dependent TestCase
      • 📝Store API Variables
      • 📔API with JSON body
      • 🙋‍♂️Api Wait
      • 🗜️API Schema Validation
      • 🏗️API Tailor-Made coding
      • 👨‍🦯API Support Generator
      • ↘️Api Response Store Objects
      • ✍️API Test Report
      • 🚃Api Response Type Validation
    • 🌐ScriptlessWeb Automation
      • 🖊️Introduction
      • 🗜️Web Automation Setup
      • 🪧Web Automation Template
      • 🧮page_object_locators
      • 📜Web Automation Key Phrases
        • 📃PAGE_NAME
        • ⌛WAIT_TYPE
        • 📜SCROLL_TYPE
        • 👨‍💼ELEMENT_NAME
        • 🏎️ACTIONS
        • ⌨️SEND_KEYS
        • ✔️VALIDATION
        • ✅VALIDATION_TYPE
      • 👨‍👦Web Dependent Test Case
      • 🐒MOCK
      • 🛂AutomationAsserts
      • 🏗️Web Tailor-Made coding
      • 📝Store Web Variables
      • 🤼‍♀️Web & API integration
      • 🖇️Dynamic Strings
      • 🗣️ReadFile Annotation for Custom Code
      • 🖼️Page_Comparison
      • 👨‍💼Gherkin Template for Web Automation
    • 📱Mobile Automation
  • 🪶Automation features
    • 🌲Environment and System Variables
    • 🗝️KeyInitializers
      • Types of KeyInitializers
    • ✍️Reporting
      • Dashboard
      • Category
      • Tests
        • Screenshot Section
    • 👯Parallel Testing
    • 🏗️Tailor-Made Coding
  • ⏩Automation Demo
Powered by GitBook
On this page
  • Introduction
  • Understanding the Tests Section
  • Navigation and Analysis
  • Conclusion

Was this helpful?

  1. Automation features
  2. Reporting

Tests

PreviousCategoryNextScreenshot Section

Last updated 1 year ago

Was this helpful?

Introduction

The 'Tests' section of the AutomationReport.html delivers an in-depth look at each individual test case executed during the testing process. This area of the report allows stakeholders to drill down into the specifics of each test, including the steps taken, their status, and the time at which they were executed.

Understanding the Tests Section

Test Case Breakdown

Each test case is listed with a timestamp and duration, giving a clear picture of when it was run and how long it took. The status indicator (such as "Fail" in red) provides an immediate visual cue to the test outcome.

Detailed Step Analysis

For each test case, you can view a list of steps that were performed, along with their individual outcomes:

  • Info: These entries provide context or descriptive information about the test steps, such as actions that have no direct pass/fail outcome.

  • Pass: Steps that were successfully completed are marked with this status, indicating that the expected outcome was achieved.

  • Fail: Steps that did not meet the expected criteria are marked as failures. These are critical and typically require further analysis to identify the root cause.

Filtering Test Results

The report offers functionality to filter test cases by their status and category:

  • By Status: You can filter the test cases to display only those that have passed, failed, or have informational entries, as demonstrated in the second screenshot you provided. This makes it easier to focus on areas that require attention or review.

  • By Category: As shown in the third screenshot, selecting a category (or test directory) filters the test cases to show only those within that specific group. This is particularly useful when you need to review tests related to a certain module or feature.

Navigation and Analysis

Using the provided filters, stakeholders can efficiently navigate through a large number of test cases to find exactly what they need. For example, quickly identifying all failed tests in a specific category can significantly speed up the debugging process.

Conclusion

The AutomationReport.html offers a comprehensive and detailed view of each test case's execution path, making it an invaluable resource for thorough test analysis. By understanding and utilizing the report's detailed views and filtering capabilities, teams can enhance their ability to deliver high-quality software by promptly addressing any issues that arise during testing.

🪶
✍️