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 to Test Management in Automation 📘
  • Test Management Configuration Description 🛠️
  • Purpose of the Test Management Integration 🎯

Was this helpful?

  1. Get Started
  2. Scriptless Config

TestManagementConfiguration

Introduction to Test Management in Automation 📘

Test management tools are indispensable for structuring and optimizing automated testing processes. Their integration ensures that automation remains organized and traceable. We will delve deeper into the intricacies and benefits of this integration in upcoming documentation 🔍.

Test Management Configuration Description 🛠️

This configuration serves as a blueprint to integrate automated testing with a test management tool. By setting the appropriate properties, you can streamline the process of executing specific tests and updating their results directly to your test management platform.

Purpose of the Test Management Integration 🎯

  • Fetch Descriptions 📁: The system retrieves the description from the test management tool using test case IDs. These test case IDs are then used as CSV file names, and the fetched descriptions are integrated into the report. This ensures a consistent link between test data and its representation in reports.

  • Update Test Management Tool 🔄: This configuration allows for dynamic updates to the test management tool based on requirements, ensuring that the tool always reflects the most recent and relevant test data.

  • Simplified Tool Integration 🛠️: Enabling integration with a test management tool requires adding only a single configuration file specific to the tool you wish to integrate. This design principle emphasizes simplicity and modularity, allowing for easy switching or updating of test management tools without extensive configuration changes.

Configuring Test Management Integration

To enable integration with a test management tool, place its configuration file within the following directory structure in your project:

project
└── config
    └── testManagementConfiguration

Inside the testManagementConfiguration folder, add the specific configuration file (e.g., testRail.properties for TestRail integration). This file contains all necessary configurations, such as API keys, project IDs, and other tool-specific settings, enabling seamless communication between your automated tests and the test management platform.

By adhering to this configuration pattern, you can maintain a clean and organized setup that supports the efficient management of test cases and results, contributing significantly to the overall quality assurance process.

Tools Integrated

This feature is available in License Code

PreviousextentReportConfiguration.propertiesNexttestRail.properties

Last updated 11 months ago

Was this helpful?

🎛️
🕵️
testRail.properties
zephyrscale.properties
testiny.properties