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
  • CoreKeyInitializers
  • ApiKeyInitializers
  • WebKeyInitializers
  • Integration with Automation Templates

Was this helpful?

  1. Automation features
  2. KeyInitializers

Types of KeyInitializers

In the Open Code version of our Scriptless Automation framework, the KeyInitializers are categorized into three distinct classes, each designed to cater to specific areas of automation:

  1. CoreKeyInitializers - Core framework utilities.

  2. ApiKeyInitializers - API automation utilities.

  3. WebKeyInitializers - Web automation utilities.

Each initializer provides thread-local variables to ensure data consistency across parallel test executions.

CoreKeyInitializers

  • Purpose: Used for core framework operations.

  • Variables Available:

    • customSoftAssert: To perform custom assertions.

    • testManagementRunUrl: To retrieve the test management run URL.

Usage:

  • Retrieve the current instance of custom soft assertions for validation.

  • Access the test management run URL during the execution of your tests.

ApiKeyInitializers

  • Purpose: Provides utilities for API automation.

  • Variables Available:

    • mailingServices: To access mailing services.

    • globalVariables: A map to store and retrieve global variables.

    • response: To get the latest API response.

Usage:

  • Use mailing services for sending emails during API tests.

  • Store and retrieve global variables required for API testing.

  • Access and validate the latest API response received.

WebKeyInitializers

  • Purpose: Used specifically for web automation.

  • Variables Available:

    • browserName: To retrieve the name of the browser being used.

    • getMainWindow: To get the main window handle of the browser.

    • devToolsListener: A map to manage DevTools listeners.

    • firstName, lastName, phoneNumber: To store and retrieve user details.

    • driver: To access the WebDriver instance.

Usage:

  • Access the browser name and main window handle for managing browser sessions.

  • Use the DevTools listener map to handle browser events.

  • Retrieve user details like first name, last name, and phone number for form submissions.

  • Interact with web elements using the WebDriver instance.

Integration with Automation Templates

  • Custom Actions: Integrate custom actions using these initializers in your automation templates. Define actions in your templates that invoke methods from your custom classes.

  • Custom Assertions: Use CoreKeyInitializers to integrate custom assertions into your tests. This allows you to perform complex validation checks.

  • API Execution: Utilize ApiKeyInitializers for handling API responses and mailing services within your API automation templates. This enables dynamic test flows based on API interactions.

PreviousKeyInitializersNextReporting

Last updated 10 months ago

Was this helpful?

🪶
🗝️