|
| 1 | +--- |
| 2 | +id: hyperexecute-connected-workflows |
| 3 | +title: HyperExecute Connected Workflows |
| 4 | +sidebar_label: Connected Workflows |
| 5 | +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. |
| 6 | +keywords: |
| 7 | + - LambdaTest Hyperexecute |
| 8 | + - LambdaTest Hyperexecute help |
| 9 | + - LambdaTest Hyperexecute documentation |
| 10 | + - LambdaTest Projects |
| 11 | + - Workflows |
| 12 | + - Schedule Workflows |
| 13 | + - Connected Workflows |
| 14 | + - Chained tests |
| 15 | +url: https://www.lambdatest.com/support/docs/hyperexecute-connected-workflows/ |
| 16 | +site_name: LambdaTest |
| 17 | +slug: hyperexecute-connected-workflows/ |
| 18 | +--- |
| 19 | + |
| 20 | +<script type="application/ld+json" |
| 21 | + dangerouslySetInnerHTML={{ __html: JSON.stringify({ |
| 22 | + "@context": "https://schema.org", |
| 23 | + "@type": "BreadcrumbList", |
| 24 | + "itemListElement": [{ |
| 25 | + "@type": "ListItem", |
| 26 | + "position": 1, |
| 27 | + "name": "Home", |
| 28 | + "item": "https://www.lambdatest.com" |
| 29 | + },{ |
| 30 | + "@type": "ListItem", |
| 31 | + "position": 2, |
| 32 | + "name": "Support", |
| 33 | + "item": "https://www.lambdatest.com/support/docs/" |
| 34 | + },{ |
| 35 | + "@type": "ListItem", |
| 36 | + "position": 3, |
| 37 | + "name": "HyperExecute Concepts", |
| 38 | + "item": "https://www.lambdatest.com/support/docs/hyperexecute-connected-workflows/" |
| 39 | + }] |
| 40 | + }) |
| 41 | + }} |
| 42 | +></script> |
| 43 | +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. |
| 44 | + |
| 45 | +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. |
| 46 | + |
| 47 | +## Features of HyperExecute Connected Workflows |
| 48 | +- **Automated Workflow Chains:** Define test chains where the success of one workflow triggers subsequent workflows. |
| 49 | +- **Flexible Scheduling:** Schedule workflows to run based on your desired frequency and conditions. |
| 50 | +- **Conditional Triggering:** Trigger workflows based on specific outcomes, such as the passing or failing of previous tests. |
| 51 | +- **Centralized Configuration:** Set up and manage workflows easily within the HyperExecute platform. |
| 52 | + |
| 53 | +## Real-World Use Case Scenarios |
| 54 | +### Example 1: Conditional Regression Testing |
| 55 | +Let’s consider a development scenario where: |
| 56 | +- **Workflow A** (smoke tests) runs first. This workflow contains a set of critical tests that must pass to ensure the build is functional. |
| 57 | +- **Workflow B** (regression tests) runs next, but only if Workflow A passes. |
| 58 | + |
| 59 | +Our objective is to automatically trigger the regression tests after the smoke tests pass to ensure that the software does not break after critical functionalities are verified. |
| 60 | + |
| 61 | +**Workflow Flow:** |
| 62 | +- **Workflow A - Smoke tests (runs daily):** Executes a subset of tests (e.g., 30 high-severity or critical tests). |
| 63 | +- **Workflow B: Regression tests (triggered after successful execution of Workflow A):** Executes a larger set of tests, ensuring that the product remains functional after code changes. |
| 64 | + |
| 65 | +### Example 2: Severity-based Test Execution |
| 66 | +In this scenario, you can define tests to run based on their severity levels. |
| 67 | +- **Workflow A:** High-severity tests (e.g., critical functionality tests) are executed every day. |
| 68 | +- **Workflow B:** General regression tests (run only after Workflow A passes). |
| 69 | + |
| 70 | +Our objective is to run essential tests first and trigger a broader set of tests only if the critical tests pass. |
| 71 | + |
| 72 | +**Workflow Flow:** |
| 73 | +- **Workflow A:** High-severity tests run daily. |
| 74 | +- **Workflow B:** General regression tests run if Workflow A passes. |
| 75 | + |
| 76 | +This setup ensures that resources are focused on high-priority tests while the more extensive tests are executed only when necessary. |
| 77 | + |
| 78 | +## Steps to Set Up Connected Workflows in HyperExecute |
| 79 | +Follow these steps to configure connected workflows in HyperExecute: |
| 80 | + |
| 81 | +### Prerequisite |
| 82 | +- Setup your [Project](/support/docs/hyperexecute-projects/#setup-your-project) before setting up the Workflows. |
| 83 | +- You must have created your required [wokrflows](/support/docs/hyperexecute-projects/#schedule-your-workflows) that you want to trigger. |
| 84 | + |
| 85 | +### Step 1: Setup Workflow |
| 86 | +- Click on the "**Setup Workflow**" button: |
| 87 | +- Enter Workflow Details: |
| 88 | + - **Workflow Name:** Give your workflow a descriptive name (e.g., "Smoke Tests" or "Regression Tests"). |
| 89 | + - **Branch Name:** Specify the branch where your tests are stored. |
| 90 | + - **YAML File Path:** Provide the path to your YAML configuration file that contains the test definitions for this workflow. |
| 91 | +- Click "Next" to proceed to the scheduling configuration. |
| 92 | + |
| 93 | +<img loading="lazy" src={require('../assets/images/hyperexecute/knowledge-base/connected-workflows/1.png').default} alt="Image" className="doc_img"/> |
| 94 | + |
| 95 | +### Step 2: Configure the Schedule |
| 96 | +- Configure the schedule of your workflow. Select the **days** and **time** at which you want to trigger your tests. Click on **Next**. |
| 97 | + |
| 98 | +### Step 3: Workflow Linking |
| 99 | +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. |
| 100 | + |
| 101 | +<img loading="lazy" src={require('../assets/images/hyperexecute/knowledge-base/connected-workflows/2.png').default} alt="Image" className="doc_img"/> |
| 102 | + |
| 103 | +## Conclusion |
| 104 | +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. |
| 105 | + |
| 106 | +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. |
0 commit comments