Skip to content

Added new doc for End-to-End Testing #889

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bharathk08 merged 2 commits into from
Dec 26, 2025
Merged

Added new doc for End-to-End Testing #889

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4ab817b
Added new doc for End-to-End Testing
bharathk08 Dec 26, 2025
4e4afb3
Merge branch 'dev' into DOC-765
bharathk08 Dec 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion src/left-nav-title.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -759,5 +759,6 @@
"user-settings": {"/docs/configuration/user-settings/": "User Settings" },
"google-sso": {"/docs/configuration/security/google-sso/": "Setting Up Google SSO Login" },
"okta-sso": {"/docs/configuration/security/okta-sso/": "Setting Up Okta SSO Login (SAML)" },
"azure-sso": {"/docs/configuration/security/azure-sso/": "Setting Up Azure SSO Login (SAML)" }
"azure-sso": {"/docs/configuration/security/azure-sso/": "Setting Up Azure SSO Login (SAML)" },
"end-to-end-testing": {"/docs/test-plans/end-to-end-testing/": "End-to-End Testing"}
}
97 changes: 97 additions & 0 deletions src/pages/docs/test-plans/end-to-end-testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,97 @@
---
title: "End-to-End Testing in Testsigma"
page_title: "End-to-End Testing in Testsigma"
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"
noindex: false
order: 8.271
page_id: "end-to-end-testing"
warning: false
contextual_links:
- type: section
name: "Contents"
- type: link
name: "Prerequisites"
url: "#prerequisites"
- type: link
name: "Enable End-to-End Testing"
url: "#enable-end-to-end-testing"
- type: link
name: "Add Test Suites from Different Projects & Applications"
url: "#add-test-suites-from-different-projects--applications"
---

---

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.

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.

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.

---

> <p id="prerequisites">Prerequisites</p>
>
> Before you begin, ensure that you have referred to:
>
> 1. [Documentation on creating test plans](https://testsigma.com/docs/test-management/test-plans/overview/).
> 2. [Documentation on creating test suites](https://testsigma.com/docs/test-management/test-suites/overview/).
> 3. [Documentation on creating test machine](https://testsigma.com/docs/test-management/test-plans/manage-test-machines/).

Comment on lines +33 to +40
Copy link
Contributor

@coderabbitai coderabbitai bot Dec 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

# First, let's verify the file exists and check its content
cat -n src/pages/docs/test-plans/end-to-end-testing.md | sed -n '33,40p'

Repository: testsigmahq/testsigma-docs

Length of output: 573

🏁 Script executed:

# Check the repository structure for documentation paths
fd -t d "test-management" src/pages/docs/
fd -t d "test-plans" src/pages/docs/
fd -t d "test-suites" src/pages/docs/

Repository: testsigmahq/testsigma-docs

Length of output: 169

🏁 Script executed:

# Check for the specific documentation files referenced in the links
fd -t f "overview" src/pages/docs/
fd -t f "manage-test-machines" src/pages/docs/

Repository: testsigmahq/testsigma-docs

Length of output: 1009

🏁 Script executed:

# Check for Next.js or routing configuration that might handle the /test-management/ routing
find src -name "next.config.*" -o -name "*routing*" -o -name "*redirect*"

Repository: testsigmahq/testsigma-docs

Length of output: 88

🏁 Script executed:

# Check for middleware or route handlers
fd -t f "middleware\|route\|redirect" src/

Repository: testsigmahq/testsigma-docs

Length of output: 52

🏁 Script executed:

# Look for any configuration that maps /test-management/ paths
rg "test-management" src/pages/docs/ -l

Repository: testsigmahq/testsigma-docs

Length of output: 2973

🏁 Script executed:

# Check the redirects.json file to understand URL routing
cat src/redirects.json | head -100

Repository: testsigmahq/testsigma-docs

Length of output: 151

🏁 Script executed:

# Search specifically for /test-management redirects
rg "test-management" src/redirects.json -A 2 -B 2

Repository: testsigmahq/testsigma-docs

Length of output: 52

Fix broken documentation links and improve sentence variety.

Three issues:

  1. Incorrect documentation link paths: The links reference /test-management/ paths, but the actual documentation is at /test-plans/ and /test-suites/. Update the links to:

    • Line 37: https://testsigma.com/docs/test-plans/overview/
    • Line 38: https://testsigma.com/docs/test-suites/overview/
    • Line 39: https://testsigma.com/docs/test-plans/manage-test-machines/

  2. Repetitive sentence structure: All three list items begin with "Documentation on". Vary the phrasing for better readability.

  3. Grammar inconsistency: Line 39 says "test machine" (singular) but should be "test machines" (plural) to match the context.

🧰 Tools
🪛 LanguageTool

[style] ~39-~39: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...anagement/test-suites/overview/). > 3. [Documentation on creating test machine](https://tests...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

🤖 Prompt for AI Agents 
In src/pages/docs/test-plans/end-to-end-testing.md around lines 33 to 40, update
the three broken links to use the correct paths (line 37 ->
https://testsigma.com/docs/test-plans/overview/, line 38 ->
https://testsigma.com/docs/test-suites/overview/, line 39 ->
https://testsigma.com/docs/test-plans/manage-test-machines/), revise the three
list items to avoid repeating “Documentation on” by varying phrasing (e.g., “See
the overview of test plans”, “Learn about creating test suites”, “Manage test
machines”), and fix the grammar on line 39 by changing “test machine” to “test
machines.”

---

## **Enable End-to-End Testing**

1. From the left navigation bar, go to **Test Plans** and click **Create Test Plan**.
![Test Plan](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/E2E_Test_Plan_Navigation.png)

2. In the **Basic Details** tab, provide the following information and click **Continue**:
- **Name (Required)**: Enter a title for the test plan.
- **Description (Optional)**: Enable the Description toggle and briefly describe the purpose and scope of the test plan.
- **Labels (Optional)**: Add labels to help organize and manage test plans.
- **Test Plan Type (Required)**: Select **Custom Test Plan**.
![Basic Details](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Basic_Details_E2E_Test_Plan.png)

> End-to-end testing can be enabled only for **Custom Test Plans**.

3. In the **Add Test Suites & Link Machine Profiles** tab, click **Add Test Suites**.
![Test Suites & Machines](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/E2E_Testing_Add_Suites.png)

4. In the **Add Test Suites to Plan** dialog, enable the **End-to-End Testing** toggle.
![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)

---

## **Add Test Suites from Different Projects & Applications**

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.

1. In the **Add Test Suites to Plan** dialog, select the **Project**, **Application**, and **Version**.
![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)

2. From the **Available Test Suites** list, select the required test suites and add them to the plan.
![Select Suites](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Select_Suites_for_E2E_Test.png)

3. The selected test suites appear in the **Selected for Test Plan** section.
![Suites Selected Section](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Suites_Selected_for_E2E_Test.png)

4. Change the **Project**, **Application**, or **Version** to add test suites from a different source.

5. Repeat steps 1–3 until all required test suites from different projects and applications are added.

6. Click **Add to Plan**.
![Add all Suites to Plan](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Add_Suites_to_Plan.png)

7. In the **Add Test Suites & Link Machine Profiles** tab, click **Test Machine** for a test suite.
![Link Machine Profiles](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Link_Machines_to_Suites_E2E.png)

8. In the **Select Test Machine Profiles** overlay, select the required test machines and click **Save Selections**.
![Save Selections](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Save_Machine_Selections_For_E2E_Test.png)

9. Repeat the same for each test suite, selecting machine profiles based on the application type.

10. Click **Continue** to proceed with the remaining test plan configuration.
![Continue to Settings](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Continue_to_Settings_for_E2E_Test.png)


---