|
| 1 | +--- |
| 2 | +title: "End-to-End Testing in Testsigma" |
| 3 | +page_title: "End-to-End Testing in Testsigma" |
| 4 | +metadesc: "This document discusses enabling & configuring end-to-end testing in Testsigma by creating a single test plan that includes test suites from multiple projects & applications" |
| 5 | +noindex: false |
| 6 | +order: 8.271 |
| 7 | +page_id: "end-to-end-testing" |
| 8 | +warning: false |
| 9 | +contextual_links: |
| 10 | +- type: section |
| 11 | + name: "Contents" |
| 12 | +- type: link |
| 13 | + name: "Prerequisites" |
| 14 | + url: "#prerequisites" |
| 15 | +- type: link |
| 16 | + name: "Enable End-to-End Testing" |
| 17 | + url: "#enable-end-to-end-testing" |
| 18 | +- type: link |
| 19 | + name: "Add Test Suites from Different Projects & Applications" |
| 20 | + url: "#add-test-suites-from-different-projects--applications" |
| 21 | +--- |
| 22 | + |
| 23 | +--- |
| 24 | + |
| 25 | +End-to-end (E2E) testing validates a complete business workflow from start to finish, as experienced by an end user. In modern applications, a single workflow often spans multiple applications, runs across different platforms, and relies on several interconnected systems. |
| 26 | + |
| 27 | +For example, a user may book a flight on a web application, cancel the booking using a mobile application, and then verify the refund status on the web. This workflow involves systems such as authentication services, booking engines, payment gateways, and notification services. End-to-end testing ensures that these systems work together correctly and that data remains consistent across the entire workflow. |
| 28 | + |
| 29 | +This document discusses enabling and configuring end-to-end testing in Testsigma by creating a single test plan that includes test suites from multiple projects and applications. |
| 30 | + |
| 31 | +--- |
| 32 | + |
| 33 | +> <p id="prerequisites">Prerequisites</p> |
| 34 | +> |
| 35 | +> Before you begin, ensure that you have referred to: |
| 36 | +> |
| 37 | +> 1. [Documentation on creating test plans](https://testsigma.com/docs/test-management/test-plans/overview/). |
| 38 | +> 2. [Documentation on creating test suites](https://testsigma.com/docs/test-management/test-suites/overview/). |
| 39 | +> 3. [Documentation on creating test machine](https://testsigma.com/docs/test-management/test-plans/manage-test-machines/). |
| 40 | +
|
| 41 | +--- |
| 42 | + |
| 43 | +## **Enable End-to-End Testing** |
| 44 | + |
| 45 | +1. From the left navigation bar, go to **Test Plans** and click **Create Test Plan**. |
| 46 | +  |
| 47 | + |
| 48 | +2. In the **Basic Details** tab, provide the following information and click **Continue**: |
| 49 | + - **Name (Required)**: Enter a title for the test plan. |
| 50 | + - **Description (Optional)**: Enable the Description toggle and briefly describe the purpose and scope of the test plan. |
| 51 | + - **Labels (Optional)**: Add labels to help organize and manage test plans. |
| 52 | + - **Test Plan Type (Required)**: Select **Custom Test Plan**. |
| 53 | +  |
| 54 | + |
| 55 | +> End-to-end testing can be enabled only for **Custom Test Plans**. |
| 56 | +
|
| 57 | +3. In the **Add Test Suites & Link Machine Profiles** tab, click **Add Test Suites**. |
| 58 | +  |
| 59 | + |
| 60 | +4. In the **Add Test Suites to Plan** dialog, enable the **End-to-End Testing** toggle. |
| 61 | +  |
| 62 | + |
| 63 | +--- |
| 64 | + |
| 65 | +## **Add Test Suites from Different Projects & Applications** |
| 66 | + |
| 67 | +When end-to-end testing is enabled, you can add test suites from multiple projects and applications to a single test plan. You add test suites incrementally by selecting a project and application, adding the required suites, and then switching to another project or application to continue adding more suites. |
| 68 | + |
| 69 | +1. In the **Add Test Suites to Plan** dialog, select the **Project**, **Application**, and **Version**. |
| 70 | +  |
| 71 | + |
| 72 | +2. From the **Available Test Suites** list, select the required test suites and add them to the plan. |
| 73 | +  |
| 74 | + |
| 75 | +3. The selected test suites appear in the **Selected for Test Plan** section. |
| 76 | +  |
| 77 | + |
| 78 | +4. Change the **Project**, **Application**, or **Version** to add test suites from a different source. |
| 79 | + |
| 80 | +5. Repeat steps 1–3 until all required test suites from different projects and applications are added. |
| 81 | + |
| 82 | +6. Click **Add to Plan**. |
| 83 | +  |
| 84 | + |
| 85 | +7. In the **Add Test Suites & Link Machine Profiles** tab, click **Test Machine** for a test suite. |
| 86 | +  |
| 87 | + |
| 88 | +8. In the **Select Test Machine Profiles** overlay, select the required test machines and click **Save Selections**. |
| 89 | +  |
| 90 | + |
| 91 | +9. Repeat the same for each test suite, selecting machine profiles based on the application type. |
| 92 | + |
| 93 | +10. Click **Continue** to proceed with the remaining test plan configuration. |
| 94 | +  |
| 95 | + |
| 96 | + |
| 97 | +--- |
0 commit comments