Skip to content

Commit 4ab817b

Browse files
committed
Added new doc for End-to-End Testing
Added new doc for End-to-End Testing in Testsigma
1 parent 2117f67 commit 4ab817b

File tree

2 files changed

+99
-1
lines changed

2 files changed

+99
-1
lines changed

src/left-nav-title.json

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -759,5 +759,6 @@
759759
"user-settings": {"/docs/configuration/user-settings/": "User Settings" },
760760
"google-sso": {"/docs/configuration/security/google-sso/": "Setting Up Google SSO Login" },
761761
"okta-sso": {"/docs/configuration/security/okta-sso/": "Setting Up Okta SSO Login (SAML)" },
762-
"azure-sso": {"/docs/configuration/security/azure-sso/": "Setting Up Azure SSO Login (SAML)" }
762+
"azure-sso": {"/docs/configuration/security/azure-sso/": "Setting Up Azure SSO Login (SAML)" },
763+
"end-to-end-testing": {"/docs/test-plans/end-to-end-testing/": "End-to-End Testing"}
763764
}
Lines changed: 97 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,97 @@
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+
![Test Plan](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/E2E_Test_Plan_Navigation.png)
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+
![Basic Details](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Basic_Details_E2E_Test_Plan.png)
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+
![Test Suites & Machines](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/E2E_Testing_Add_Suites.png)
59+
60+
4. In the **Add Test Suites to Plan** dialog, enable the **End-to-End Testing** toggle.
61+
![End-to-End Testing Toggle](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/End_to_End_Testing_Toggle.png)
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+
![Select Project, Application & Version](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Select_Project_App_Version_For_Suite.png)
71+
72+
2. From the **Available Test Suites** list, select the required test suites and add them to the plan.
73+
![Select Suites](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Select_Suites_for_E2E_Test.png)
74+
75+
3. The selected test suites appear in the **Selected for Test Plan** section.
76+
![Suites Selected Section](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Suites_Selected_for_E2E_Test.png)
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+
![Add all Suites to Plan](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Add_Suites_to_Plan.png)
84+
85+
7. In the **Add Test Suites & Link Machine Profiles** tab, click **Test Machine** for a test suite.
86+
![Link Machine Profiles](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Link_Machines_to_Suites_E2E.png)
87+
88+
8. In the **Select Test Machine Profiles** overlay, select the required test machines and click **Save Selections**.
89+
![Save Selections](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Save_Machine_Selections_For_E2E_Test.png)
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+
![Continue to Settings](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Continue_to_Settings_for_E2E_Test.png)
95+
96+
97+
---

0 commit comments

Comments
 (0)