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. TestManagementConfiguration

testiny.properties

Introduction

Integrating your automated testing framework with Testiny streamlines the process of managing test cases, executing tests, and reporting outcomes. This detailed guide explains the configuration settings within the testiny.properties file to ensure successful integration.

Location of testiny.properties

Ensure the file is placed in your project structure as follows:

project
└── config
    └── testManagementConfiguration
        └── testiny.properties

Configuration Settings in testiny.properties 🛠️

Located under your project's configuration directory, the testiny.properties file contains the necessary settings for Testiny integration. Here's what you need to know about each key:

testiny.enable: Controls whether the Testiny integration is active. Set to "enable" to activate the integration.

  • Example: testiny.enable=enable

testiny.base.url: The base URL for the Testiny API. This URL is where your automated tests will send API requests.

  • Example: testiny.base.url=https://app.testiny.io/api/v1/

testiny.X-Api-Key: Your Testiny API key used for authentication. This token grants your automated tests access to Testiny's API for managing test cases and results.

  • Example: testiny.X-Api-Key=API-KEY

testiny.project.name: The name of the project in Testiny where your tests are organized. This should match the project name in Testiny.

  • Example: testiny.project.name=My Demo Project

testiny.tester.email: The email of the tester. This is used to send notifications or results to the tester.

  • Example: testiny.tester.email=EMAIL

testiny.test.name: The name of the test or group of tests. This can be used to identify specific tests or test suites within a test plan.

  • Example: testiny.test.name=Regression

testiny.testplan.title: Controls the management of test plans. If set to "NEW", automation will create a new test plan. If a title is given and not present on the board, automation will create a new one with that title. If the given title is already present, automation will use the existing test plan.

  • Example: testiny.testplan.title=Regression-2024-04-08_06:32:56

testiny.testplan.description: A description of the test plan. This provides context for the test cases and cycles grouped under this plan.

  • Example: testiny.testplan.description=Test plan Automation description

testiny.testrun.title: Controls the management of test runs. If set to "NEW", automation will create a new test run. If a title is given and not present on the board, automation will create a new one with that title. If the given title is already present, automation will use the existing test run.

  • Example: testiny.testrun.title=Regression-TestRun-2024-04-08_06:34:48

testiny.testrun.description: A description of the test run. This provides additional details about the scope or purpose of the test run.

  • Example: testiny.testrun.description=Test run Automation description

Conclusion

After configuring the testiny.properties file with the appropriate settings, your automated testing framework is equipped to leverage Testiny for enhanced test management capabilities. This integration facilitates the automated creation and updating of test plans, cycles, and cases, ensuring a seamless workflow between test execution and result reporting.

This feature is available in License Code

Previouszephyrscale.propertiesNexttestNgConfiguration.properties

Last updated 11 months ago

Was this helpful?

🎛️
🕵️