From ecaa79f0b6da89963db21eeed7388f0c3d97c1d7 Mon Sep 17 00:00:00 2001 From: amanchopra1905 Date: Fri, 28 Mar 2025 12:47:32 +0530 Subject: [PATCH] updated the hyperexecute test chains doc --- .../1.png | Bin .../2.png | Bin ...rkflows.md => hyperexecute-test-chains.md} | 24 +++++++++--------- sidebars.js | 2 +- 4 files changed, 13 insertions(+), 13 deletions(-) rename assets/images/hyperexecute/knowledge-base/{connected-workflows => test-chains}/1.png (100%) rename assets/images/hyperexecute/knowledge-base/{connected-workflows => test-chains}/2.png (100%) rename docs/{hyperexecute-connected-workflows.md => hyperexecute-test-chains.md} (79%) diff --git a/assets/images/hyperexecute/knowledge-base/connected-workflows/1.png b/assets/images/hyperexecute/knowledge-base/test-chains/1.png similarity index 100% rename from assets/images/hyperexecute/knowledge-base/connected-workflows/1.png rename to assets/images/hyperexecute/knowledge-base/test-chains/1.png diff --git a/assets/images/hyperexecute/knowledge-base/connected-workflows/2.png b/assets/images/hyperexecute/knowledge-base/test-chains/2.png similarity index 100% rename from assets/images/hyperexecute/knowledge-base/connected-workflows/2.png rename to assets/images/hyperexecute/knowledge-base/test-chains/2.png diff --git a/docs/hyperexecute-connected-workflows.md b/docs/hyperexecute-test-chains.md similarity index 79% rename from docs/hyperexecute-connected-workflows.md rename to docs/hyperexecute-test-chains.md index fc0bae66c..d3fab7308 100644 --- a/docs/hyperexecute-connected-workflows.md +++ b/docs/hyperexecute-test-chains.md @@ -1,7 +1,7 @@ --- -id: hyperexecute-connected-workflows -title: HyperExecute Connected Workflows -sidebar_label: Connected Workflows +id: hyperexecute-test-chains +title: HyperExecute Test Chains +sidebar_label: Test Chains description: Discover the power of HyperExecute connected workflows and how testers or developers can leverage it for their daily autoamtion testing of their organization features. keywords: - LambdaTest Hyperexecute @@ -12,9 +12,9 @@ keywords: - Schedule Workflows - Connected Workflows - Chained tests -url: https://www.lambdatest.com/support/docs/hyperexecute-connected-workflows/ +url: https://www.lambdatest.com/support/docs/hyperexecute-test-chains/ site_name: LambdaTest -slug: hyperexecute-connected-workflows/ +slug: hyperexecute-test-chains/ --- -Connected workflows allow you to link multiple test workflows so that one workflow triggers another based on specific conditions, such as the success or failure of a previous workflow. This feature eliminates the need for manual intervention between different stages of testing, allowing for a seamless automated testing pipeline. +Test Chains allow you to link multiple test workflows so that one workflow triggers another based on specific conditions, such as the success or failure of a previous workflow. This feature eliminates the need for manual intervention between different stages of testing, allowing for a seamless automated testing pipeline. -In this guide, we will walk through the setup and use of connected workflows in HyperExecute, providing real-world examples and step-by-step instructions on how to implement them. +In this guide, we will walk through the steps to create test chains using connected workflows in HyperExecute, providing real-world examples and step-by-step instructions on how to implement them. ## Features of HyperExecute Connected Workflows - **Automated Workflow Chains:** Define test chains where the success of one workflow triggers subsequent workflows. @@ -80,7 +80,7 @@ Follow these steps to configure connected workflows in HyperExecute: ### Prerequisite - Setup your [Project](/support/docs/hyperexecute-projects/#setup-your-project) before setting up the Workflows. -- You must have created your required [wokrflows](/support/docs/hyperexecute-projects/#schedule-your-workflows) that you want to trigger. +- You must have created your required [workflows](/support/docs/hyperexecute-projects/#schedule-your-workflows) that you want to trigger. ### Step 1: Setup Workflow - Click on the "**Setup Workflow**" button: @@ -90,7 +90,7 @@ Follow these steps to configure connected workflows in HyperExecute: - **YAML File Path:** Provide the path to your YAML configuration file that contains the test definitions for this workflow. - Click "Next" to proceed to the scheduling configuration. -Image +Image ### Step 2: Configure the Schedule - Configure the schedule of your workflow. Select the **days** and **time** at which you want to trigger your tests. Click on **Next**. @@ -98,9 +98,9 @@ Follow these steps to configure connected workflows in HyperExecute: ### Step 3: Workflow Linking You can link this workflow to other existing workflows within the same project or across other projects you own. Once this workflow completes successfully, it can automatically trigger the linked workflows, enabling seamless execution across stages. To set this up, simply select the projects and workflows you wish to trigger from the available list. This feature allows you to build automated, end-to-end workflow chains, ideal for orchestrating complex testing and deployment pipelines. -Image +Image ## Conclusion -HyperExecute’s Connected Workflows feature significantly enhances the automation of testing processes by creating logical dependencies between workflows. This feature allows for a more efficient, error-free testing pipeline that ensures quality software with minimal manual intervention. +HyperExecute’s Test Chain feature significantly enhances the automation of testing processes by creating logical dependencies between workflows. This feature allows for a more efficient, error-free testing pipeline that ensures quality software with minimal manual intervention. By setting up workflows that automatically trigger based on the outcomes of previous ones, teams can reduce the time spent managing tests, allowing them to focus on critical tasks. Whether you are running smoke tests first, followed by full regression tests, or organizing tests based on severity, HyperExecute provides the flexibility to streamline your testing processes. \ No newline at end of file diff --git a/sidebars.js b/sidebars.js index 2d3f79bab..e0848ac26 100644 --- a/sidebars.js +++ b/sidebars.js @@ -717,7 +717,7 @@ module.exports = { "hyperexecute-build-mobile-apps-using-tools", "hyperexecute-utilizing-custom-libraries", "hyperexecute-supported-languages-and-packages", - "hyperexecute-connected-workflows" + "hyperexecute-test-chains" ], }, {