Skip to content

Commit 5e636db

Browse files
authored
Merge pull request #880 from testsigmahq/dev
Added two new FAQs
2 parents 52fc5ce + 347bb83 commit 5e636db

19 files changed

+492
-71
lines changed

src/left-nav-title.json

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -487,7 +487,7 @@
487487
"/docs/configuration/api-keys/": "API Keys"
488488
},
489489
"security": {
490-
"/docs/configuration/security/": "Security(SSO)"
490+
"/docs/configuration/security/": "Security"
491491
},
492492
"api": {
493493
"/docs/api/": "Testsigma REST APIs"
@@ -752,10 +752,12 @@
752752
"xray": {"/docs/integrations/test-management/xray/": "Xray"},
753753
"qtest": {"/docs/integrations/test-management/qtest/": "qTest"},
754754
"requirements": {"/docs/atto/generative-ai/generate-tests/requirements/": "Add Requirements"},
755-
"live-editor": {"/docs/atto/generative-ai/copilot/live-editor/": "In Testsigma"},
756-
"live-editor": {"/docs/live-editor/": "Copilot"},
757755
"jira": {"/docs/integrations/bug-reporting/jira/": "Jira" },
758756
"jira": {"/docs/atto/generative-ai/integrations/jira/": "Jira"},
759757
"xray": {"/docs/atto/generative-ai/integrations/xray/": "Xray"},
760-
"qtest": {"/docs/atto/generative-ai/integrations/qtest/": "qTest"}
758+
"qtest": {"/docs/atto/generative-ai/integrations/qtest/": "qTest"},
759+
"user-settings": {"/docs/configuration/user-settings/": "User Settings" },
760+
"google-sso": {"/docs/configuration/security/google-sso/": "Setting Up Google SSO Login" },
761+
"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)" }
761763
}
Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
1+
---
2+
title: "How to Update an Excel File in Testsigma Uploads?"
3+
metadesc: "When Excel files are modified during test execution, updates are stored locally. Learn how to upload the updated file back to Testsigma correctly."
4+
order: 24.41
5+
page_id: "how-to-update-an-excel-file-in-testsigma-uploads-?"
6+
warning: false
7+
contextual_links:
8+
- type: section
9+
name: "Contents"
10+
- type: link
11+
name: "Prerequisites"
12+
url: "#prerequisites"
13+
- type: link
14+
name: "Install the Addons"
15+
url: "#install-the-addons"
16+
- type: link
17+
name: "Steps to Resolve the Issue"
18+
url: "#steps-to-resolve-the-issue"
19+
---
20+
21+
---
22+
23+
When you modify an Excel file during a test run, the changes are stored locally on the test machine. To make sure these updates are reflected inside Testsigma, you must upload the modified file back using the appropriate addons. This article discusses the steps required to update and re-upload the Excel file correctly.
24+
25+
---
26+
27+
> ## **Prerequisites**
28+
>
29+
> Before you begin, ensure that you have an excel file that has been uploaded to Testsigma.
30+
31+
---
32+
33+
## **Install the Addons**
34+
35+
1. From the left navigation bar, click **Addons**.
36+
![Addons](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_1.png)
37+
38+
2. Under the **New & Updated Addons** section, search for the **Upload Latest file to Testsigma Uploads** addon and click **Install**.
39+
![Upload Latest File to Testsigma Uploads](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_2.1.png)
40+
41+
3. Under the **New & Updated Addons** section, search for the **ExcelActions_cloud** addon and click **Install**.
42+
![ExcelActions](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_3.png)
43+
44+
---
45+
46+
## **Steps to Resolve the Issue**
47+
48+
1. In your test case, first use the **Wait the data datavalue into the Excelfile excel-path with Cell value rowNo, columnNo, sheet-index and store the path in runtime variable variable-name (supports upload section)** NLP to enter the value that you want to add to the excel file.
49+
![NLP 1](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_4.1.png)
50+
51+
- Enter the value you want to write into the **datavalue** placeholder.![datavalue](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_5.png)
52+
- Click the **excel-path** placeholder and replace it by selecting **Upload** from the **Test Data Types** dropdown.![Upload](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_6.png)
53+
- In the **Uploads** overlay, choose the Excel file you want to update.![Excel file](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_7.png)
54+
- Specify the row number in the **rowNo** placeholder. ![rowNo](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_8.png)
55+
- Specify the column number in the **columnNo** placeholder. ![columnNo](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_9.png)
56+
- Specify the sheet number in the **sheet-index** placeholder. ![sheet-index](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_10.png)
57+
- Enter a variable name in the **variable-name** placeholder. ![Variable Name](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_11.png)
58+
- Click **Create Step**. ![Create Step](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_12.png)
59+
60+
2. Secondly, use the **Upload file with path on testigma uploads with projectid, applicationid, uploadname, url with API key api_key** NLP to push the updated file back to your project.
61+
![NLP 2](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_13.png)
62+
63+
- Click the **absolutepath** placeholder and replace it by selecting **Runtime** from the **Test Data Types** dropdown.![Runtime](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_14.png)
64+
- In the **Runtime Variable** overlay, select the runtime variable you created in the previous step. ![select the runtime variable](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_15.png)
65+
- Click the **projectid** placeholder and enter your project id. ![projectid](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_16.png)
66+
[[info | **NOTE**:]]
67+
| To get **project id** and **application id** use the following steps:
68+
| 1. Before you begin, open the inspect panel and refresh the page. Now, right-click on the application name and select **Inspect**.![Inspect](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_17.png)
69+
| 2. Go to the **Network** tab and refresh the page. ![Network](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_18.png)
70+
| 3. Click applications query. ![applications query](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_19.png)
71+
| 4. Here you can find your **projectId** and **applicationId** under the **Preview** tab. ![Preview](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_20.png)
72+
- Click the **applicationid** placeholder and enter your application id. ![applicationid](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_21.png)
73+
- Click the **uploadname** placeholder and enter your excel file’s name. ![uploadname](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_22.png)
74+
[[info | **NOTE**:]]
75+
| To get **uploadname** and **upload id**, go to **Uploads** and hover over the excel file you want to update. ![Uploads](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_26.png)
76+
- Enter the following URL **[https://app.testsigma.com/api/v1/uploads/{ID}](https://app.testsigma.com/api/v1/uploads/{ID})** and replace <ID> with the upload ID copied from the **Uploads** page. For example, **[https://app.testsigma.com/api/v1/uploads/8](https://app.testsigma.com/api/v1/uploads/8)** ![URL](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_23.png)
77+
- Enter the api key in the **testdata** placeholder. ![api](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_24.png)
78+
[[info | **NOTE**:]]
79+
| Please refer to the [documentation on generating api keys](https://testsigma.com/docs/configuration/api-keys/).
80+
- Click **Create Step**. ![Create Step](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_25.png)
81+
82+
After you execute it, here's how it looks:
83+
![Run Result](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/uploads_28.png)
84+
85+
---
Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
---
2+
title: "Why Can’t Selenium ChromeDriver Interact With 3DS Authentication Pages?"
3+
metadesc: "Learn why Selenium hangs on 3DS payment pages and how a simple desired capability prevents ChromeDriver from waiting indefinitely."
4+
order: 24.20
5+
page_id: "why-cant-selenium-chromedriver-interact-with-3ds-authentication-pages?"
6+
warning: false
7+
contextual_links:
8+
- type: section
9+
name: "Contents"
10+
- type: link
11+
name: "Steps to Add the Desired Capability to the Test Case"
12+
url: "#steps-to-add-the-desired-capability-to-the-test-case"
13+
---
14+
15+
---
16+
17+
When you navigate to 3D Secure (3DS) authentication pages such as Visa or Mastercard, Selenium on Chrome or Edge may freeze or time out during execution.
18+
19+
**Why This Happens**
20+
21+
3DS authentication screens load a third-party iframe that runs continuous background scripts from the payment gateway.
22+
23+
Inside these iframes:
24+
- Long-running JavaScript and postMessage listeners are always active.
25+
- Messages are continuously exchanged with the payment provider.
26+
- The browser keeps processing events and never reaches a fully loaded state.
27+
28+
As a result:
29+
- ChromeDriver waits indefinitely for the page to finish loading
30+
- The pageLoad event never completes
31+
- Selenium becomes unresponsive after navigation
32+
33+
To prevent Selenium from waiting indefinitely, you need to add a desired capability to your test case that stops ChromeDriver from waiting for the full page load.
34+
35+
This article discusses how to add the desired capability to the test case.
36+
37+
---
38+
39+
## **Steps to Add the Desired Capability to the Test Case**
40+
41+
1. From the left navigation bar, go to **Create Tests > Test Cases**.
42+
![Test Cases](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/selenium_faq_1.png)
43+
44+
2. In the Test Case Explorer section, expand a **Feature** and a **Scenario** and select the required test case.
45+
![Test Case](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/selenium_faq_2.png)
46+
47+
3. In the Test Case Details page, click **Run**.
48+
![Run](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/selenium_faq_3.png)
49+
50+
4. In the **Ad-Hoc Run** overlay, expand the **Desired Capabilities** section, enter the following:
51+
52+
| **Key** | **Data Type** | **Value** |
53+
| ------------- | ------------- | ------------- |
54+
| pageLoadStrategy | String | none |
55+
56+
![Desired Capability](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/selenium_faq_4.png)
57+
58+
5. Click **Run Now**.
59+
![Run Now](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/selenium_faq_5.png)
60+
61+
---

src/pages/docs/atto/generative-ai/copilot/live-editor.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: "Copilot in Testsigma"
3-
page_title: "Copilot in Testsigma"
4-
metadesc: "The Copilot in Testsigma helps you debug, execute, and modify test cases in real time. It also enables you to generate test cases using Testsigma Copilot"
2+
title: "Copilot in Live Editor"
3+
page_title: "Copilot in Live Editor"
4+
metadesc: "The Live Editor in Testsigma helps you debug, execute, and modify test cases in real time. It also enables you to generate test cases using Testsigma Live Editor"
55
noindex: false
66
order: 4.7433
77
page_id: "copilot-in-live-editor"
@@ -19,13 +19,13 @@ contextual_links:
1919

2020
---
2121

22-
The Copilot in Testsigma helps you debug, execute, and modify test cases in real time. It also enables you to generate test cases using Testsigma Copilot, allowing you to convert prompts into executable test steps. Whether you're reviewing a failed step, learning elements dynamically, or creating new tests from scratch, the Copilot gives you complete control over the test execution flow. This article discusses the capabilities of the Copilot in Testsigma.
22+
The Live Editor in Testsigma helps you debug, execute, and modify test cases in real time. It also enables you to generate test cases using Testsigma Live Editor, allowing you to convert prompts into executable test steps. Whether you're reviewing a failed step, learning elements dynamically, or creating new tests from scratch, the Live Editor gives you complete control over the test execution flow. This article discusses the capabilities of the Live Editor in Testsigma.
2323

2424
---
2525

2626
> <p id="prerequisites">Prerequisites</p>
2727
>
28-
> Before you begin, ensure **Testsigma Terminal** is installed and the **Copilot** is ready.
28+
> Before you begin, ensure **Testsigma Terminal** is installed and the **Live Editor** is ready.
2929
3030
---
3131

src/pages/docs/auto-healing/using-auto-healing-in-live-editor-test-execution.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: "Using Auto-Healing in Copilot Test Execution"
3-
page_title: "Using Auto-Healing in Copilot Test Execution"
4-
metadesc: "Enable Auto-Healing in the Copilot to validate and fix element locators in real time, ensuring tests stay stable despite UI changes during execution."
2+
title: "Using Auto-Healing in Live Editor Test Execution"
3+
page_title: "Using Auto-Healing in Live Editor Test Execution"
4+
metadesc: "Enable Auto-Healing in the Live Editor to validate and fix element locators in real time, ensuring tests stay stable despite UI changes during execution."
55
noindex: false
66
order: 4.916
7-
page_id: "using-auto-healing-in-copilot-test-execution"
7+
page_id: "using-auto-healing-in-live-editor-test-execution"
88
warning: false
99
contextual_links:
1010
- type: section
@@ -22,7 +22,7 @@ contextual_links:
2222

2323
---
2424

25-
With Auto-Healing enabled, you can execute test cases directly in the Copilot to validate element locators in real time. This helps ensure that any changes in the application’s UI are automatically detected and corrected during execution. This article discusses how auto-healing identifies and updates element locators while executing test cases in the Copilot.
25+
With Auto-Healing enabled, you can execute test cases directly in the Live Editor to validate element locators in real time. This helps ensure that any changes in the application’s UI are automatically detected and corrected during execution. This article discusses how auto-healing identifies and updates element locators while executing test cases in the Live Editor.
2626

2727
---
2828

src/pages/docs/configuration/security/azure-sso.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ title: "Setting up SAML-based SSO login for Testsigma in Azure"
33
page_title: "Setting up SAML-based Single Sign-On (SSO) for Testsigma with Azure AD"
44
metadesc: "Learn how to Set up SAML-based SSO login for Testsigma in Azure. With Azure Active Directory, users can automatically sign into their cloud-hosted/on-premise apps "
55
noindex: false
6-
order: 19.24
7-
page_id: "Set up SAML-based SSO login for Testsigma in Azure"
6+
order: 19.27
7+
page_id: "setting-up-azure-sso-with-saml-in-testsigma"
88
search_keyword: ""
99
warning: false
1010
contextual_links:

src/pages/docs/configuration/security/google-sso.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ title: "Setting Up Google Single Sign-On(SSO) Login in Testsigma"
33
page_title: "Setting up Google Single Sign-On (SSO) login"
44
metadesc: "Learn how to set up Single Sign-On (SSO) with Google in Testsigma. With Google SSO, you are not required to store and manage passwords for the websites."
55
noindex: false
6-
order: 19.22
7-
page_id: "Setting up Google Single Sign-On(SSO) login in Testsigma Application."
6+
order: 19.25
7+
page_id: "google-sso"
88
search_keyword: ""
99
warning: false
1010
contextual_links:

src/pages/docs/configuration/security/okta-sso.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ title: "Setting Up Okta Single Sign-On Integration with SAML Login in Testsigma"
33
page_title: "Configuring Okta SSO Integration with SAML in Testsigma"
44
metadesc: "Single Sign-On (SSO) provides faster, easier, and trusted access to applications. Learn how to set up Single Sign-On (SSO) with SAML login easily in Testsigma."
55
noindex: false
6-
order: 19.23
7-
page_id: "setting-up-okta-sso-with-saml--in-testsigma"
6+
order: 19.26
7+
page_id: "setting-up-okta-sso-with-saml-in-testsigma"
88
search_keyword: ""
99
warning: false
1010
contextual_links:
Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
---
2+
title: "Configure Organization Settings"
3+
metadesc: "Organization Settings allow administrators to manage authentication and security configurations for the organization | Learn how to configure organization settings in Testsigma"
4+
noindex: false
5+
order: 19.22
6+
page_id: "organization-settings"
7+
search_keyword: ""
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: "Password Policy"
17+
url: "#password-policy"
18+
- type: link
19+
name: "Single Sign-On (SSO)"
20+
url: "#single-sign-on-sso"
21+
- type: link
22+
name: "Supported SSO Providers"
23+
url: "#supported-sso-providers"
24+
---
25+
26+
---
27+
28+
Organization Settings allow administrators to manage authentication and security configurations for the organization. These settings define how users access Testsigma and help enforce consistent security standards across the organization.
29+
30+
This article discusses an overview of organization-level security settings, including Password Policy and Single Sign-On (SSO).
31+
32+
---
33+
34+
> <p id="prerequisites">Prerequisites</p>
35+
> Before you begin, ensure that:
36+
> - You have an active Testsigma account with administrator access.
37+
> - You have access to the Single Sign-On (SSO) identity provider you plan to use.
38+
39+
---
40+
41+
## **Password Policy**
42+
43+
Password Policy allows organization administrators to configure password-related security controls for user accounts.
44+
45+
To learn how to configure password policies, see [Configure Password Policy](https://testsigma.com/docs/configuration/security/password-policy/).
46+
47+
---
48+
49+
## **Single Sign-On (SSO)**
50+
51+
Single Sign-On (SSO) allows users to authenticate using an external identity provider and enforces SSO-based access to the organization.
52+
53+
---
54+
55+
## **Supported SSO Providers**
56+
Testsigma supports the following Single Sign-On (SSO) providers:
57+
- [Google Single Sign-On](https://testsigma.com/docs/configuration/security/google-sso/)
58+
- [SAML-based Single Sign-On (Okta)](https://testsigma.com/docs/configuration/security/okta-sso/)
59+
- [SAML-based Single Sign-On (Azure)](https://testsigma.com/docs/configuration/security/azure-sso/)
60+
- **SAML-based Single Sign-On (OneLogin)**
61+
- **SAML-based Single Sign-On (Google Workspace)**
62+
63+
---

0 commit comments

Comments
 (0)