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
  • Configuration
  • Usage
  • Conclusion

Was this helpful?

  1. Get Started
  2. Scriptless Config
  3. TestManagementConfiguration

testRail.properties

Introduction

This document provides step-by-step instructions on how to configure and use TestRail for managing automated test cases and results within your project. TestRail integration allows you to streamline your testing process, manage test cases, and automatically update test results, ensuring a robust quality assurance process.

Configuration

TestRail.properties

Before utilizing the TestRail integration with your automated tests, you must configure the TestRail.properties file. This file contains all necessary details for connecting to your TestRail account and managing your testing process.

Steps:

  1. Locate the TestRail.properties File:

    Find the TestRail.properties file within your project's directory structure. It is located at:

    project
    └── config
        └── testManagementConfiguration
            └── testRail.properties
  2. Edit the File: Open the TestRail.properties file in a text editor or IDE of your choice.

  3. Configure the Properties: You will find several key-value pairs in the file. Here's a breakdown of what each key represents and the values you should provide:

    • TEST_RAIL_BASE_URL: The base URL of your TestRail instance. This URL is used to access the TestRail API.

    • TESTRAIL_USER: Your TestRail username. This is often your email address used to log into TestRail.

    • TESTRAIL_PASSWORD: Your TestRail API key. It is recommended to use an API key instead of your password for security reasons. You can generate or find this in your TestRail user settings.

    • PROJECT_NAME: The name of the project in TestRail that you're working on. This should exactly match the project name in TestRail.

    • MILE_STONE_NAME: The milestone associated with your tests. This helps in grouping test runs within a specific development phase or release.

    • SUITE_NAME: The name of the test suite in TestRail that you want to update with your test results. This should match the suite name in TestRail.

    • TestRail_Enable: This flag determines whether the TestRail integration is enabled. Set this to enable to turn on the integration.

    After editing, save your changes to the TestRail.properties file.

Usage

After configuring the TestRail.properties file, your automated testing framework is now set to interact with TestRail. Here's what happens behind the scenes:

  • Test Initialization: At the start of your test run, the framework will connect to TestRail using the details provided in the TestRail.properties file. It then retrieves or creates a test run based on your project, milestone, and suite configurations.

  • Test Execution: As your automated tests execute, the framework will update TestRail with the status of each test case. This includes passing, failing, and skipping tests.

  • Results Reporting: Upon completion of the test run, the framework will finalize the test run in TestRail, updating it with the overall outcome and attaching any relevant reports or logs.

Conclusion

By following the steps outlined in this document and correctly configuring the TestRail.properties file, you can seamlessly integrate TestRail with your automated testing process. This integration will enhance your ability to manage test cases, track test execution, and report on test outcomes, contributing to a more efficient and effective quality assurance cycle.

This feature is available in License Code

PreviousTestManagementConfigurationNextzephyrscale.properties

Last updated 11 months ago

Was this helpful?

🎛️
🕵️