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

Was this helpful?

  1. Get Started
  2. Scriptless Config
  3. ReportConfiguration

extentReportConfiguration.properties

A configuration file designed for the Extent Reports integration within the automation framework. Extent Reports is a versatile reporting tool 📊 that crafts interactive and comprehensive test reports, offering a visual representation of test execution. This file defines parameters shaping the appearance, structure, and behavior of the generated Extent Reports, ensuring alignment with preferred specifications and aesthetics.

Keys within extentReportConfiguration.properties:

  1. ReportName: 🏷

    • Purpose: Specifies the title or name for the generated Extent Report.

    • Description: The designated name for the report is "AutomationReport", and this will be displayed prominently as the report's title.

  2. Report_Theme: 🌓

    • Purpose: Determines the visual theme of the Extent Report.

    • Description: The selected theme is "dark", producing a dark mode visual for the report. Users can switch between "dark" and "standard" themes based on viewing preferences.

  3. Report_JS: 🖥

    • Purpose: Injects custom JavaScript to refine or modify the interactive dynamics of the Extent Report.

    • Description: The JavaScript code provided adjusts elements tagged as "details-col", changing their content to "Steps", enhancing clarity in the report's layout.

  4. Report_CSS: 🎨

    • Purpose: Adds custom CSS to modify the visual aspects and design of the Extent Report.

    • Description: The specified CSS tweaks the dimensions of the logo in the report's header, ensuring its proportional and consistent display.

  5. Report_logo: 🖼

    • Purpose: Defines the path to the logo image to be displayed in the Extent Report.

    • Description: The logo for the report is located at "/config/logo.jpg". This image will be embedded in the report, typically at the top, to provide a branded touch to the report's presentation.

  6. Report_captureScreenshotOnPass: 🖼️

    • Purpose: Switch to capture image on validation pass.

    • Description: Enabling this setting allows the framework to capture and embed screenshots when validations pass. This provides visual documentation of successful test executions, useful for creating comprehensive reports, visual regression testing, and ensuring the application's state is correctly validated at each step.


By using the extentReportConfiguration.properties file 📁, the automation framework offers a tailored approach to customise Extent Reports. This ensures reports are both informative 🧾 and align with organisational branding and style preferences. 🎨🔧

File

PreviousReportConfigurationNextTestManagementConfiguration

Last updated 8 months ago

Was this helpful?

🎛️
🛂
348B
extentReportConfiguration.properties