diff --git a/.github/workflows/cd.yml b/.github/workflows/cd.yml
index ca2d2b8d..57878422 100644
--- a/.github/workflows/cd.yml
+++ b/.github/workflows/cd.yml
@@ -7,6 +7,8 @@ jobs:
Deploy:
runs-on: ubuntu-latest
steps:
+ - name: Update package information with default mirror
+ run: sudo sed -i 's|mirror+file:/etc/apt/apt-mirrors.txt|http://archive.ubuntu.com/ubuntu|' /etc/apt/sources.list && sudo apt-get update
- name: Install libvips
run: sudo apt-get install libvips
- uses: actions/checkout@v2
@@ -51,7 +53,7 @@ jobs:
TYPESENSE_COLLECTION: ${{ secrets.TYPESENSE_COLLECTION }}
TYPESENSE_API_KEY: ${{ secrets.TYPESENSE_API_KEY }}
TYPESENSE_SEARCH_API_KEY: ${{ secrets.TYPESENSE_SEARCH_API_KEY }}
-
+
- name: Start Gatsby server
run: npm run develop &
env:
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 409b5603..e5052716 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -1,11 +1,13 @@
name: 'CI'
on:
pull_request:
- types: [ opened, synchronize, reopened ]
+ types: [opened, synchronize, reopened]
jobs:
CI:
runs-on: ubuntu-latest
steps:
+ - name: Update package information with default mirror
+ run: sudo sed -i 's|mirror+file:/etc/apt/apt-mirrors.txt|http://archive.ubuntu.com/ubuntu|' /etc/apt/sources.list && sudo apt-get update
- name: Install libvips
run: sudo apt-get install libvips
- uses: actions/checkout@v2
diff --git a/.github/workflows/staging-cd.yml b/.github/workflows/staging-cd.yml
index 78e4c346..e359d5ba 100644
--- a/.github/workflows/staging-cd.yml
+++ b/.github/workflows/staging-cd.yml
@@ -7,6 +7,8 @@ jobs:
StagingDeploy:
runs-on: ubuntu-latest
steps:
+ - name: Update package information with default mirror
+ run: sudo sed -i 's|mirror+file:/etc/apt/apt-mirrors.txt|http://archive.ubuntu.com/ubuntu|' /etc/apt/sources.list && sudo apt-get update
- name: Install libvips
run: sudo apt-get install libvips
- uses: actions/checkout@v2
@@ -38,7 +40,7 @@ jobs:
echo TYPESENSE_SEARCH_API_KEY=${{ secrets.WEBSITE_STAGING_TYPESENSE_SEARCH_API_KEY }} >> .env
cat .env
- name: Set environment
- run : sed -i 's/localhost/website.testsigma.com/g' src/environment.ts
+ run: sed -i 's/localhost/website.testsigma.com/g' src/environment.ts
- name: Build
run: |
PREFIX_PATHS=true npm run build && npm run deploy
diff --git a/src/left-nav-title.json b/src/left-nav-title.json
index 2ff290c7..895b33ea 100644
--- a/src/left-nav-title.json
+++ b/src/left-nav-title.json
@@ -574,5 +574,14 @@
},
"desktop-windows":{
"/docs/projects/setup/desktop-windows/": "Desktop Windows"
+ },
+ "actions-and-options-recorder":{
+ "/docs/test-cases/create-test-steps/actions-and-options-recorder/": "Actions & Options (Recorder)"
+ },
+ "actions-and-options-manual":{
+ "/docs/test-cases/create-test-steps/actions-and-options-manual/": "Actions & Options (Manual)"
+ },
+ "multiple-webviews":{
+ "/docs/test-cases/create-test-steps/actions-and-options-recorder/multiple-webviews/": "Tests for Multiple WebViews"
}
}
\ No newline at end of file
diff --git a/src/pages/docs/continuous-integration/aws-devops.md b/src/pages/docs/continuous-integration/aws-devops.md
index 28f2f35d..b0d81713 100644
--- a/src/pages/docs/continuous-integration/aws-devops.md
+++ b/src/pages/docs/continuous-integration/aws-devops.md
@@ -1,6 +1,6 @@
---
title: " Integrate Testsigma with AWS DevOps"
-metadecs: "How to integrate Testsigma with AWS DevOps"
+metadecs: "This article discusses step-by-step instructions for integrating Testsigma application with AWS DevOps | Learn how to integrate AWS DevOps with Testsigma Application"
order: 12.15
page_id: "Integrate Testsigma with AWS DevOps"
warning: false
@@ -16,13 +16,16 @@ contextual_links:
AWS services that are used as a part of CI/CD pipeline are:
-**CodeCommit:** AWS CodeCommit is a version control service that enables you to privately store and manage Git repositories in the AWS cloud.
-**CodeBuild:** CodeBuild compiles your source code, runs unit tests, and produces artifacts that are ready to deploy.
+**CodeCommit:** AWS CodeCommit is a version control service that enables you to privately store and manage Git repositories in the AWS cloud.
+
+**CodeBuild:** CodeBuild compiles your source code, runs unit tests, and produces artifacts that are ready to deploy.
+
**CodeDeploy:** AWS CodeDeploy is a deployment service that enables developers to automate the deployment of applications to instances and to update the applications as required.
---
-##**AWS DevOps integration methods:**
+
+## **AWS DevOps integration methods:**
Below are the 2 methods to integrate and trigger Testsigma tests via AWS DevOps:
@@ -114,3 +117,4 @@ That's all we need to automate Test Execution when a successful build is trigger
+---
\ No newline at end of file
diff --git a/src/pages/docs/continuous-integration/github-cicd.md b/src/pages/docs/continuous-integration/github-cicd.md
index c6283f11..0474238a 100644
--- a/src/pages/docs/continuous-integration/github-cicd.md
+++ b/src/pages/docs/continuous-integration/github-cicd.md
@@ -1,6 +1,6 @@
---
title: "Integrate Testsigma with Github"
-metadecs: "This document describes detailed step-by-step instructions for integrating Testsigma with Github | Learn how to integrate Github with Testsigma"
+metadecs: "This article discusses step-by-step instructions for integrating Testsigma application with Github | Learn how to integrate Github with Testsigma Application"
order: 12.21
page_id: "github-cicd"
warning: false
@@ -19,6 +19,7 @@ contextual_links:
When you want to automate, customize, and, execute your software development workflows right in your github repository, you need to use github actions. In this document, we will discuss how to integrate Github with Testsigma for CI/CD purposes.
---
+
## **Pre-requisites:**
You should already know:
1. The basics of github actions. If not, please refer here: [Quickstart with github actions](https://docs.github.com/en/actions/quickstart)
@@ -26,6 +27,7 @@ You should already know:
2. [How to get Test Plan ID from an existing Test Plan.](https://testsigma.com/docs/continuous-integration/get-test-plan-details/)
---
+
## **For Github CICD Integration:**
To start with Github Actions, create a .github/workflows directory in your repository on GitHub if this directory does not already exist.
diff --git a/src/pages/docs/elements/android-apps/capture-single-element.md b/src/pages/docs/elements/android-apps/capture-single-element.md
index 5f75d51a..6b04cc81 100644
--- a/src/pages/docs/elements/android-apps/capture-single-element.md
+++ b/src/pages/docs/elements/android-apps/capture-single-element.md
@@ -17,7 +17,12 @@ contextual_links:
- type: link
name: "How to create one element at a time using the Testsigma mobile inspector for an android project in Testsigma"
url: "#how-to-create-one-element-at-a-time-using-the-testsigma-mobile-inspector-for-an-android-project-in-testsigma"
-
+- type: link
+ name: "Updating an Element"
+ url: "#updating-an-element"
+- type: link
+ name: "Reusing Elements Recorded"
+ url: "#reusing-elements-recorded"
---
@@ -61,3 +66,75 @@ In an Android project in Testsigma, you can selectively capture elements one at
You can also [capture multiple elements at once via mobile test recorder](https://testsigma.com/docs/elements/android-apps/record-multiple-elements/).
+
+## **Updating an Element**
+
+ 1. Create a Test Case using Testsigma’s test Recorder in your Android Project.
+ 2. On the Recorder UI, hover over the step that has the element you want to edit. The elements appear in green on the Testsigma test Recorder UI
+
+
+
+
+ 3. Click on the ‘More Details’ button corresponding to the step that you want to edit. The button corresponding to the step is highlighted in the screenshot below:
+
+
+
+ 4. Click on ‘More details’ button:
+
+
+
+ 5. Click on the edit button corresponding to the element on the Test Step Details:
+
+
+
+
+
+
+
+
+
+Here are the fields that appear on the ‘Edit Element’ window:
+
+ * **Name**: Text input field, you can edit the name of the Element here
+ * **Screen Name**: This is an editable field, you can edit the screen name for the Element here.
+ * **Element Type**: This is a drop-down field that has values:
+ 1. Xpath
+ 2. ID
+ 3. Name
+ 4. Class Name
+ 5. Accessibility ID
+
+You can select any of these options for element type.
+ * **Enter Value**: Here, the value should correspond to the element type selected. This is also an editable field.
+
+
+6. Click on the ‘Update’ button to finalize the changes.
+
+---
+
+
+## **Reusing Elements Recorded**
+
+ 1. Create a test case in which you will be reusing your pre-recorded elements.
+ 2. Start recording test steps for the test case.
+ 3. Manually add a test step where you want to reuse elements:
+
+
+
+
+
+
+Alternatively, you can record a test step that uses an element. Given below is an example of test steps as they appear on Recorder UI. The text in green is an element.
+
+
+
+ 4. Hover on the test step that you want to edit and click on the corresponding edit button.
+ 5. Click on the green text that represents ‘element’. The ‘Elements’ section appears on the test Recorder UI, listing all pre-recorded elements in the project:
+
+
+
+ 6. Start typing the name of the element that you want to reuse, the elements will be filtered by name. You can search the elements by name or by Screen name.
+ 7. From the filtered results, you can click on the element that you want to use, and the element text in your test step will be replaced by the chosen element.
+ 8. Click on ‘Update’ button corresponding to the test step on the Testsigma test Recorder UI to finalize the change.
+
+---
\ No newline at end of file
diff --git a/src/pages/docs/elements/android-apps/create-manually.md b/src/pages/docs/elements/android-apps/create-manually.md
index 7f17301b..c5ad3396 100644
--- a/src/pages/docs/elements/android-apps/create-manually.md
+++ b/src/pages/docs/elements/android-apps/create-manually.md
@@ -1,6 +1,6 @@
---
title: "Create Elements [Manually]"
-metadesc: "Element path plays an important role in dynamic websites. Learn how to create elements manually for a android apps in Testsigma."
+metadesc: "Element path plays an important role in dynamic websites. Learn how to create elements manually for a android apps in Testsigma application"
noindex: false
order: 6.34
page_id: "Create Elements [Manually]"
@@ -12,34 +12,35 @@ contextual_links:
name: "Introduction"
url: "#introduction"
- type: link
- name: "Pre-requisites"
- url: "#pre-requisites"
+ name: "Prerequisites"
+ url: "#prerequisites"
- type: link
- name: "How to create elements manually for an android project in Testsigma"
- url: "#how-to-create-elements-manually-for-an-android-project-in-testsigma"
-
----
-
+ name: "Creating Elements"
+ url: "#creating-elements"
+- type: link
+ name: "Creating Element While Adding Test Steps"
+ url: "#creating-element-while-adding-test-steps"
+- type: link
+ name: "Updating an Element"
+ url: "#updating-an-element"
+- type: link
+ name: "Updating Multiple Elements"
+ url: "#updating-multiple-elements"
---
-##**Introduction**
-In this document, we will discuss how to create elements manually for your android project in Testsigma i.e. without the use of a mobile test recorder.
-
---
-##**Pre-requisites**
-1. You should have an android project in Testsigma. See [creating a project](https://testsigma.com/docs/projects/overview/).
-
-
-**Navigation**
+In this document, we will discuss how to create elements manually for your android project in Testsigma i.e. without the use of a mobile test recorder.
-**Test Development > Elements**
+---
-
+## **Prerequisites**
+- You should have an android project in Testsigma. See [creating a project](https://testsigma.com/docs/projects/overview/).
---
-##**How to create elements manually for an android project in Testsigma**
+
+## **Creating Elements**
1. Go to your android project, then go to Test Development > Elements.
2. On the ‘All Elements’ page that appears, click on the create button on the top right:
@@ -66,3 +67,87 @@ Here are the fields that you will see:
6. Once you have added all the details, click on the ‘Create’ button and the element you created will be added to the project.
+
+
+---
+
+## **Creating Element While Adding Test Steps**
+ 1. Create a test case or go to a pre-existing test case.
+ 2. Add a test step to the test case that contains an element. The language for the test step should contain an element. Some examples of such steps for an android application are shown in the screenshot below:
+
+
+
+ 3. Let’s say we add a step ‘Tap on element’ to our test case:
+
+
+
+ 4. On the step, click on the green text ‘element’, a layover will appear containing the elements in the project like this:
+
+
+
+ 5. Here, to create an element that is not in the list, start typing a new name for the element, the option “NEW” will appear like this:
+
+
+
+ 6. Click on the ‘NEW’ button highlighted in the last step. ‘Create Element’ form will open up as shown in the screenshot below:
+
+
+
+ 7. Create the element either manually or via element Test recorder. In this document, we will cover how to create elements ‘manually’. You can also [capture elements via Test recorder](https://testsigma.com/docs/elements/android-apps/capture-single-element/). For now, select the radio button ‘Manually’.
+
+ 8. You will see the form options as shown in the screenshot below:
+
+
+
+
+
+Here are the fields that you will see:
+ 1. **Name**: Enter the name you want to give your element.
+ 2. **Screen Name**: Mention the screen that your element resides on.
+ 3. **Element Type**: There are 5 types of identifier types supported in Testsigma. This field is a drop-down list and you can select any one of them: XPATH, ID, Name, Class Name, or Accessibility ID
+ 4. **Enter Value**: Enter the value here that is in correspondence with the Identifier Type you selected
+
+
+
+ 9. Once you have added all the details, click on the ‘Create’ button. The green text ‘element’ will be replaced in the test step you were creating.
+
+ You can now continue adding the test step for your android project.
+
+---
+
+## **Updating an Element**
+
+ 1. Select your project and then navigate to **Test Development > Elements**
+ 2. **All Elements** page will appear. This contains all the elements that you have created for the selected android project, like this:
+
+
+
+ 3. Scroll or filter to find the element you want to update.
+ 4. Hover over the element and click on the **Edit** that appears. The button is also highlighted in the screenshot below:
+
+
+
+ 5. The Edit Element layover will appear:
+
+
+
+There is a radio button that lets you choose between **Manually** or **Element Inspector**. When **Manually** is selected, you can make the changes you need to make in this element on the form and click on **Update** to finalize the changes. For the Test recorder approach, see how to [update elements using Test recorder](https://testsigma.com/docs/test-cases/create-steps-recorder/android-apps/update-elements/).
+
+---
+
+## **Updating Multiple Elements**
+
+ 1. Select your android project and then navigate to **Test Development > Elements**
+ 2. On the top right, there is an option to export the elements in excel format:
+
+
+
+ 3. In the excel sheet, update the required fields for the required elements.
+ 4. Click on **Import**. Select the excel sheet you updated in step 3 for import.
+
+
+
+With import, the edits done in step 3 will be visible in the corresponding elements in your android project in Testsigma.
+
+
+---
\ No newline at end of file
diff --git a/src/pages/docs/elements/ios-apps/capture-single-element.md b/src/pages/docs/elements/ios-apps/capture-single-element.md
index b4992937..8008d6b3 100644
--- a/src/pages/docs/elements/ios-apps/capture-single-element.md
+++ b/src/pages/docs/elements/ios-apps/capture-single-element.md
@@ -17,7 +17,12 @@ contextual_links:
- type: link
name: "How to create one element at a time by using the Testsigma mobile inspector for an iOS project in Testsigma"
url: "#how-to-create-one-element-at-a-time-by-using-the-testsigma-mobile-inspector-for-an-ios-project-in-testsigma"
-
+- type: link
+ name: "Update an Element"
+ url: "#update-an-element"
+- type: link
+ name: "Reusing Elements"
+ url: "#reusing-elements"
---
@@ -54,4 +59,85 @@ In an iOS project in Testsigma, you can selectively capture elements one at a ti
6. Once you enter the required details in the element form, click on the button ‘Save & Close’. The element will be saved in the project’s element list and the Test recorder will be closed.
-You can also [capture multiple elements at once via Test recorder](https://testsigma.com/docs/elements/ios-apps/record-multiple-elements/).
\ No newline at end of file
+You can also [capture multiple elements at once via Test recorder](https://testsigma.com/docs/elements/ios-apps/record-multiple-elements/).
+
+
+---
+
+## **Update an Element**
+1. Create a Test Case using Test Recorder in your iOS Project.
+
+2. On the Test Recorder UI, hover over the step that has the element you want to edit. The elements appear in green on the Testsigma Mobile Test Recorder UI:
+
+
+
+
+3. Click on the ‘More Details’ button corresponding to the step that you want to edit. The button corresponding to the step is highlighted in the screenshot below:
+
+
+
+4. Click on ‘More details’ button:
+
+
+
+5. Click on the edit button corresponding to the element on the Test Step Details:
+
+
+
+
+
+
+
+Here are the fields that appear on the ‘Edit Element’ window:
+
+ **1. Name:** Text input field, you can edit the name of the Element here.
+
+ **2. Screen Name:** This is an editable field, you can edit the screen name for the UI identifier here.
+
+ **3. Element Type:** This is a drop-down field that has values:
+
+ a. Xpath
+
+ b. ID
+
+ c. Name
+
+ Class Name
+
+ sAccessibility ID
+
+ You can select any of these options for an identifier type.
+
+ **4. Enter Value:** Here, the value should correspond to the identifier type selected. This is also an editable field.
+
+6. Click on the ‘Update’ button to finalize the changes.
+
+---
+
+## **Reusing Elements**
+
+1. Create a test case in which you will be reusing your pre-recorded elements.
+
+2. Start recording test steps for the test case.
+
+3. Manually add a test step where you want to reuse elements:
+
+
+
+Alternatively, you can record a test step that uses an element. Given below is an example of test steps as they appear on the Recorder UI. The text in green is an element.
+
+
+
+4. Hover on the test step that you want to edit and click on the corresponding edit button.
+
+5. Click on the green text that represents ‘element’. The ‘Elements’ section appears on the Test Recorder UI, listing all pre-recorded elements in the project:
+
+
+
+6. Start typing the name of the element that you want to reuse, the elements will be filtered by name. You can search the elements by name or by Screen name.
+
+7. From the filtered results, you can click on the element that you want to use, and the element text in your test step will be replaced by the chosen element.
+
+8. Click on the ‘Update’ button corresponding to the test step on the Test Recorder UI to finalize the change.
+
+---
\ No newline at end of file
diff --git a/src/pages/docs/elements/ios-apps/create-manually.md b/src/pages/docs/elements/ios-apps/create-manually.md
index 63506b81..d7ba1a6c 100644
--- a/src/pages/docs/elements/ios-apps/create-manually.md
+++ b/src/pages/docs/elements/ios-apps/create-manually.md
@@ -1,6 +1,6 @@
---
title: "Create Elements [Manually]"
-metadesc: "Element path plays an important role in dynamic websites. Learn how to create elements manually for a iOS Applications in Testsigma."
+metadesc: "Element path plays an important role in dynamic websites. Learn how to create elements manually for a iOS Applications in Testsigma application"
noindex: false
order: 6.44
page_id: "Create Elements [Manually]"
@@ -15,31 +15,35 @@ contextual_links:
name: "Pre-requisites"
url: "#pre-requisites"
- type: link
- name: "How to create elements manually for an iOS project in Testsigma"
- url: "#how-to-create-elements-manually-for-an-ios-project-in-testsigma"
+ name: "Creating Elements"
+ url: "#creating-elements"
+- type: link
+ name: "Creating Element While Adding Test Steps"
+ url: "#creating-element-while-adding-test-steps"
+- type: link
+ name: "Updating an Element"
+ url: "#updating-an-element"
+- type: link
+ name: "Updating Multiple Elements"
+ url: "#updating-multiple-elements"
---
---
-In this document, we will discuss how to create elements manually for your iOS project in Testsigma i.e. without the use of a Test recorder.
-
-
----
-##**Pre-requisites**
-You should have an iOS project in Testsigma. See [creating a project](https://testsigma.com/docs/projects/overview/).
+In this document, we will discuss how to create elements manually for your iOS project in Testsigma i.e. without the use of a Test recorder.
-
-**Navigation**
-**Test Development > Elements**
+---
-
+## **Prerequisites**
+You should have an iOS project in Testsigma. See [creating a project](https://testsigma.com/docs/projects/overview/).
---
-##**How to create elements manually for an iOS project in Testsigma**
+
+## **Creating Elements**
1. Go to your iOS project, then go to Test Development > Elements.
2. On the ‘All Elements’ page that appears, click on the create button on the top right:
@@ -65,4 +69,90 @@ Here are the fields that you will see:
6. Once you have added all the details, click on the ‘Create’ button and the element you created will be added to the project.
+---
+
+## **Creating Element While Adding Test Steps**
+
+ 1. Create a test case or go to a pre-existing test case.
+
+ 2. Add a test step to the test case that contains an element. The language for the test step should contain an element. Some examples of such steps for an iOS application are shown in the screenshot below:
+
+
+
+ 3. Let’s say we added the step ‘Tap on element’ to our test case:
+
+
+
+ 4. On the step, click on the green text ‘element’, a layover will appear containing the elements in the project like this:
+
+
+
+ 5. Here, to create an element that is not in the list, start typing a new name for the element, the option “NEW” will appear like this:
+
+
+
+ 6. Click on the ‘NEW’ button highlighted in the last step. ‘Create Element’ form will open up as shown in the screenshot below:
+
+
+
+ 7. Create the element either manually or via element inspector. In this document, we will cover how to create elements ‘manually’. You can also [capture elements via Test recorder](https://testsigma.com/docs/elements/ios-apps/capture-single-element/). For now, select the radio button ‘Manually’.
+
+ 8. You will see the form options as shown in the screenshot below:
+
+
+
+Here are the fields that you will see:
+
+**Name**: Enter the name you want to give your element.
+
+**Screen Name**: Mention the screen that your element resides on.
+
+**Element Type**: There are 5 types of identifier types supported in Testsigma. This field is a drop-down list and you can select any one of them: XPATH, ID, Name, Class Name, or Accessibility ID
+
+**Enter Value**: Enter the value here that is in correspondence with the Identifier Type you selected.
+
+
+
+ 8. Once you have added all the details, click on the ‘Create’ button. The green text ‘element’ will be replaced in the test step you were creating.
+
+You can now continue adding the test step for your iOS project.
+
+---
+
+## **Updating an Element**
+
+ 1. Select your project and then navigate to **Test Development > Elements**.
+ 2. **All Elements** page will appear. This contains all the elements that you have created for the selected iOS project, like this:
+
+
+
+ 3. Scroll or filter to find the element you want to update.
+ 4. Hover over the element and click on the **Edit**.
+
+
+
+The Edit Element layover will appear:
+
+
+
+There is a radio button that lets you choose between **Manually** or **Element Inspector**. When **Manually** is selected, you can make the changes you need to make in this element on the form and click on **Update** to finalize the changes. For Test recorder approach, see how to [update elements using Test recorder.](https://testsigma.com/docs/test-cases/create-steps-recorder/ios-apps/update-elements/)
+
+
+
+---
+
+## **Updating Multiple Elements**
+
+ 1. Select your iOS project and then navigate to ‘Test Development > Elements’
+ 2. On the top right, there is an option to export the elements in excel format:
+
+
+
+ 3. In the excel sheet, update the required fields for the required elements.
+ 4. Click on the import button highlighted in the screenshot below. Select the excel sheet you updated in step 3 for import.
+
+
+
+With import, the edits done in step 3 will be visible in the corresponding elements in your iOS project in Testsigma.
+---
\ No newline at end of file
diff --git a/src/pages/docs/elements/overview.md b/src/pages/docs/elements/overview.md
index 7e956244..6c0d3c48 100644
--- a/src/pages/docs/elements/overview.md
+++ b/src/pages/docs/elements/overview.md
@@ -28,8 +28,8 @@ contextual_links:
name: "View Saved Element Filters"
url: "#view-saved-element-filters"
- type: link
- name: "Update Saved Element Filter"
- url: "#update-saved-element-filter"
+ name: "Reusing Saved Elements"
+ url: "#reusing-saved-elements"
---
---
@@ -95,3 +95,8 @@ You can use user-defined custom fields and the default fields to filter elements
---
+## **Reusing Saved Elements**
+
+Once you create and add elements to a test case, they are saved in the corresponding project in Testsigma. You can reuse these elements in new test steps in the same project.
+
+---
\ No newline at end of file
diff --git a/src/pages/docs/elements/web-apps/capture-single-element.md b/src/pages/docs/elements/web-apps/capture-single-element.md
index 69ec9111..51925c38 100644
--- a/src/pages/docs/elements/web-apps/capture-single-element.md
+++ b/src/pages/docs/elements/web-apps/capture-single-element.md
@@ -20,6 +20,12 @@ contextual_links:
- type: link
name: "Steps to Create an Element From the Test Case Result Page"
url: "#steps-to-create-an-element-from-the-test-case-result-page"
+- type: link
+ name: "Updating elements via Test recorder"
+ url: "#updating-elements-via-test-recorder"
+- type: link
+ name: "Reusing elements recorded"
+ url: "#reusing-elements-recorded"
---
---
@@ -102,5 +108,60 @@ Here’s a quick GIF demonstrating how to create an element from the Elements pa
---
+## **Updating elements via Test recorder**
+
+ 1. Create a Test Case using the Test recorder.
+ 2. Click on the element/Elements that you want to edit. The Elements appear in green on the Test recorder UI.
+
+
+
+ 3. Click ‘edit Elements’ from the three dots on the far right
+
+
+
+These are the fields that will appear:
+
+ * **Name**
+ * **Screen Name**
+ * **Identifier Type**: This is a drop-down field that has values:
+ 1. Xpath
+ 2. CSS Selector
+ 3. ID
+ 4. Name
+ 5. Link Text
+ 6. Partial Link Text
+ 7. Class Name
+ 8. Tag Name
+
+You can select any of these options for identifier type.
+ * **Enter Value**: Here, the value should correspond to the identifier type selected.
+ * **View details**: Once you click on this, you will be able to see more details about the Elements.
+
+Click ‘Update’ button to finalize the changes.
+
+
+---
+
+## **Reusing Elements Recorded**
+
+ 1. Create a new test case in the same Project.
+ 2. Start recording the test steps.
+ 3. Add a test step as follows:
+
+
+
+
+You can also record a test step that uses an Element.
+
+
+
+ 4. Hover on the test step that you want to edit and click on the corresponding edit button.
+ 5. Click on the green text that says ‘Element’. The ‘Elements’ page appears on the Test recorder UI. This will have all the Elements in the project:
+
+
+ 6. Start typing the name of the Element that you want to use. The Elements can be filtered by name. You can also search the identifiers by name or by Screen name.
+ 7. From the filtered results, you can click on the Element that you want to use, and the Element text in your test step will be replaced by the chosen Element.
+ 8. Click on ‘Update’ button corresponding to the test step on the Test recorder UI to finalize the change.
+---
\ No newline at end of file
diff --git a/src/pages/docs/elements/web-apps/create-manually.md b/src/pages/docs/elements/web-apps/create-manually.md
index 6446d6dd..0ca91ebd 100644
--- a/src/pages/docs/elements/web-apps/create-manually.md
+++ b/src/pages/docs/elements/web-apps/create-manually.md
@@ -1,6 +1,6 @@
---
title: "Create Element Manually"
-metadesc: "Element path plays an important role in dynamic websites. Learn how to create elements manually for a Web Application project in Testsigma."
+metadesc: "Element path plays an important role in dynamic websites. Learn how to create elements manually for a Web Application project in Testsigma application"
noindex: false
order: 6.24
page_id: "Create Element Manually"
@@ -14,6 +14,15 @@ contextual_links:
- type: link
name: "Creating Element Manually"
url: "#creating-element-manually"
+- type: link
+ name: "Creating Element While Adding Test Steps"
+ url: "#creating-element-while-adding-test-steps"
+- type: link
+ name: "Updating an Element"
+ url: "#updating-an-element"
+- type: link
+ name: "Updating Multiple Elements"
+ url: "#updating-multiple-elements"
---
---
@@ -26,17 +35,16 @@ If you are not familiar with XPaths or CSS Selectors, please use the Testsigma t
[[info | NOTE:]]
| This guide is intended for Advanced Users. Familiarity with Elements, XPath and CSS Selectors is recommended for this guide.
-
---
-##**Why Create Elements Manually**
+## **Why Create Elements Manually**
For dynamic websites such as E-commerce websites, the elements might be dynamic in nature i.e none of their attributes/properties remain constant across sessions. In such cases, there are chances for the Elements created using Testsigma test Recorder to fail. In those specific cases, we might need to create some of the Elements manually.
-
---
-##**Creating Element Manually**
+
+## **Creating Element Manually**
Navigate to **Test Development > Elements** to get to the Elements page:
@@ -57,3 +65,92 @@ If you would like to know more about creating dynamic locators, refer: [Dynamic
After entering the values, click on the Create button to create the Element.
+
+---
+
+## **Creating Element While Adding Test Steps**
+ 1. Create a new test case or go to an existing test case.
+ 2. Add a test step to the test case. The language for the test step should contain an Element. For inspiration, check the screenshot below:
+
+
+
+ 3. Let’s say we added the step ‘Click on element’ to our test case. After addition, the step looks like this:
+
+
+
+ 4. On the step, click on the green text ‘Element’, a layover will appear containing the Elements in the project, as shown in the screenshot below:
+
+
+
+ 5. Here,if you want to create an element that is not added already, then you can start typing a new name for it: the option “NEW” will appear as also shown in the screenshot below:
+
+
+
+ 6. Now click on the ‘NEW’ button highlighted in the last step. ‘Create Element’ form will open up as shown in the screenshot below:
+
+
+
+ 7. Here, you can create the Element either manually or via test recorder. To proceed with creating the Element manually, select ‘Manually’.
+
+ If you want to create elements in less than half the time, capture them using Testsigma’s test recorder. Read more about it [here](https://testsigma.com/docs/elements/web-apps/capture-single-element/).
+
+ Here’s how to create the Element manually:
+
+ 8. Once you select ‘Manually’, you will see the form options as shown in the screenshot below:
+
+
+
+
+
+
+Fill the fields you see:
+
+ 1. **Name**: Element name
+ 2. **Screen Name**: Screen that your element resides on.
+ 3. **Identifier Type**: There are 5 types of identifier types supported in Testsigma, this field is a drop-down list, you can select any one of them: XPATH, CSS Selector, ID, Name or Link Text
+
+
+
+ 4. **Enter Value**: Enter the value here that is in correspondence with the Identifier Type you selected.
+
+
+
+ Once you have added all the details, click on the ‘CREATE’ button and your created element will be replaced in the test step you were creating.
+
+---
+
+## **Updating an Element**
+
+ 1. To update an element, go to **Test Development > Elements**
+ 2. **All UI identifiers** page will appear that contains all the elements in the selected project:
+
+
+
+ 3. Go to the element that you want to update. If there are too many to find the right one, try filtering the elements.
+ 4. Hover over the element and click on the **Edit** button.
+
+
+
+ 5. An Edit Elements layover opens as shown in the screenshot below:
+
+
+Edit the element and click on **Update** to save the changes.
+
+
+
+---
+## **Updating Multiple Elements**
+
+ 1. Go to **Test Development > Elements**
+ 2. On the top right, there is an option to export the elements in excel format. Click it:
+
+
+
+ 3. On your workstation, update the excel sheet. Save the changes and close the file.
+ 4. In Testsigma, click on the import button and upload the saved file from the previous step.
+
+
+
+This way, you can bulk edit element information. The changes will be visible in the corresponding elements in Testsigma.
+
+---
\ No newline at end of file
diff --git a/src/pages/docs/integrations/collaboration/microsoft-teams.md b/src/pages/docs/integrations/collaboration/microsoft-teams.md
index e32123de..8d43d08f 100644
--- a/src/pages/docs/integrations/collaboration/microsoft-teams.md
+++ b/src/pages/docs/integrations/collaboration/microsoft-teams.md
@@ -1,6 +1,6 @@
---
title: "Integrating MS Team with Testsigma for test run notifications"
-metsdesc: "Learn how to configure a Microsoft Teams channel to receive notifications about Test Results in real-time from Testsigma Application."
+metsdesc: "Configure Microsoft Teams channel to receive notifications about Test Results in real-time from Testsigma Application | Testsigms Integration with MS Team"
order: 16.22
page_id: "Integrating MS Team with Testsigma for test run notifications"
warning: false
@@ -23,12 +23,14 @@ contextual_links:
Integrating Testsigma with Microsoft Teams is similar to integrating with other collaboration tools like Google Chat and Slack.
---
+
## **Prerequisites**
We need a Microsoft Teams Connector to integrate with Testsigma. To know how to generate an Incoming Webhook in MS Teams, refer [Create an incoming Webhooks | MS Teams](https://docs.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook)
Microsoft Teams Connector is an Incoming Webhook mapped to a specific Channel in your organization and we will be using the connector to post the Test Results on that Teams channel.
---
+
## **Integrating Microsoft Teams with Testsigma**
Once the Connector URL is obtained, navigate to the Plugins page through **Dashboard > Settings > Plugins** and select **MS Teams** under the **Collaborations** Tab.
@@ -38,6 +40,7 @@ Once the Connector URL is obtained, navigate to the Plugins page through **Dashb
After entering the details, click on the Create button to add the Integration.
---
+
## **Enabling MS Teams notifications in Test Plan**
Once the MS Teams integration is added, you can enable the MS Teams notifications for your Test Plans while editing any of your existing Test Plans or while creating a new Test Plan.
@@ -52,6 +55,10 @@ From the **Send Notification When** section on the Test Plan Settings page,
The first and second line shows the integration added to the channel.
The third line shows the **Test Plan Completed** notification when the Test Plan completes.
+
Click on the **View in Testsigma** link to check the details inside the Testsigma App.
-
\ No newline at end of file
+
+
+
+---
\ No newline at end of file
diff --git a/src/pages/docs/integrations/product-management/clickup.md b/src/pages/docs/integrations/product-management/clickup.md
index 5d4894ce..6ca4ac1a 100644
--- a/src/pages/docs/integrations/product-management/clickup.md
+++ b/src/pages/docs/integrations/product-management/clickup.md
@@ -1,6 +1,6 @@
---
title: "Integrate Testsigma with Clickup"
-metadecs: "How to integrate Testsigma with Clickup for real-time bug reporting during Test Runs | Push bugs directly from Testsigma to your Clickup project"
+metadecs: "Learn how to integrate Testsigma with Clickup for real-time bug reporting during Test Runs | Push bugs directly from Testsigma to your Clickup project"
order: 16.55
page_id: "Clickup"
warning: false
@@ -28,7 +28,7 @@ To integrate Clickup with Testsigma, you need the following:
- **API Key:** API Token from Clickup.
[[info | **NOTE**:]]
-|*For more information on how to create API token in Clickup, refer to Clickup [personal API key](https://help.clickup.com/hc/en-us/articles/6303426241687-Getting-Started-with-the-ClickUp-API).*
+| *For more information on how to create API token in Clickup, refer to Clickup [personal API key](https://help.clickup.com/hc/en-us/articles/6303426241687-Getting-Started-with-the-ClickUp-API).*
---
diff --git a/src/pages/docs/integrations/product-management/linear.md b/src/pages/docs/integrations/product-management/linear.md
index 8b598cf4..f45ebc9a 100644
--- a/src/pages/docs/integrations/product-management/linear.md
+++ b/src/pages/docs/integrations/product-management/linear.md
@@ -1,10 +1,9 @@
---
title: "Integrate Testsigma with Linear"
-metadecs: "How to integrate Testsigma application with Linear for real-time bug reporting during Test Runs | Push bugs directly from Testsigma to your Linear project"
+metadecs: "Learn how to integrate Testsigma application with Linear for real-time bug reporting during Test Runs | Push bugs directly from Testsigma to your Linear project"
order: 16.52
page_id: "Linear"
warning: false
-
contextual_links:
- type: section
name: "Contents"
diff --git a/src/pages/docs/reports/runs/drill-down-reports.md b/src/pages/docs/reports/runs/drill-down-reports.md
index 7c3d419a..13757192 100644
--- a/src/pages/docs/reports/runs/drill-down-reports.md
+++ b/src/pages/docs/reports/runs/drill-down-reports.md
@@ -9,55 +9,120 @@ contextual_links:
- type: section
name: "Contents"
- type: link
- name: "Navigation"
- url: "#navigation"
+ name: "Prerequisites"
+ url: "#prerequisites"
- type: link
- name: "How to use drill-down reports in Testsigma"
+ name: "How to Use Drill-down Reports in Testsigma"
url: "#how-to-use-drill-down-reports-in-testsigma"
+- type: link
+ name: "Steps to Generate Test Case Reports"
+ url: "#steps-to-generate-test-case-reports"
+- type: link
+ name: "Steps to Generate Test Suite Reports"
+ url: "#steps-to-generate-test-suite-reports"
+- type: link
+ name: "Steps to Generate Test Machine Reports"
+ url: "#steps-to-generate-test-machine-reports"
+- type: link
+ name: "Additional Actions on Results"
+ url: "#additional-actions-on-results"
---
---
-If the quality of an application is inversely proportional to the number of bugs / technical glitches / performance issues / usability issues, etc, then
+The users will have better satisfaction when the application does not have bugs, technical glitches, performance issues, or usability issues. When these issues increase, the quality decreases, which results in bad UX. That's when drill-down reports come in handy.
+
+In Testsigma, you can view/download reports at multiple levels and find specific details, like the number of tests failed and the reason for failures or machines causing more problems. You can assess the application's quality and address issues from this data.
+
+---
+
+## **Prerequisites**
+
+- You should know how to [create a test case](https://testsigma.com/docs/test-cases/manage/add-edit-delete/#creating-a-test-case).
+
+- You should know how to [create a test suite](https://testsigma.com/docs/test-management/test-plans/overview/#steps-to-create-a-test-plan).
+
+- You should know how to [create a test plan](https://testsigma.com/docs/test-management/test-suites/overview/#creating-a-test-suit).
+
+---
+
+## **How to Use Drill-down Reports in Testsigma:**
+
+1. Navigate to **Run Results** page and click on a **Test Plan Result**.
+
+
+
+2. From **Test Plan Result** page, you can view **Test Case** reports.
+
-
- Quality = Customer Satisfaction * ( 1/ bugs ) * (1 / usability issues )
-
- Quality of an application reduces with more bugs.
+[[info | **NOTE**:]]
+| You can also view reports at test suite and test machine level by clicking on **Test Suite** and **Test Machine**.
+| 
-This is where drill-down reports really come in handy. Drill-down reports let you access data at all layers. They help you understand the quality of the application and how your test automation is helping contribute to it. **Drilling down can help you uncover granular details about your testing, such as**
+3. You can choose the different runs from the dropdown to see how the results have changed for different builds.
+
-1. Number of test cases failed
-2. Why did a specific test fail
-3. Number of distinct test suites with bad quality
-4. Which test machine is showing more bugs
-Testsigma provides you an easy way to find and understand all this data.
+---
+
+
+## **Steps to Generate Test Case Reports**
+
+
+1. Navigate to **Run Results** page and click on a **Test Plan Result**.
+
+
+2. Results are available in **Test Case**, **Test Suite**, and **Test Machine** level. Click on **Test Case** to view the results grouped by **Test Cases**.
+
---
-## **Navigation:**
-Select Project > Test Development > Run Results
+
+## **Steps to Generate Test Suite Reports**
+
+1. Navigate to **Run Results** page and click on a **Test Plan Result**.
+
+
+2. Results are available in **Test Case**, **Test Suite**, and **Test Machine** level. Click on **Test Suite** to view the results grouped by **Test Suites**.
+
+
+3. You can also check test case results inside test suite by clicking on the **Test suite** of your choice.
+
---
-## **How to use drill-down reports in Testsigma:**
-1. Navigate to **Run Results** page.
- 
+## **Steps to Generate Test Machine Reports**
+
+1. Navigate to **Run Results** page and click on a **Test Plan Result**.
+
+
+2. Results are available in **Test Case**, **Test Suite**, and **Test Machine** level. Click on **Test Machine** to view the results grouped by **Test Machines**.
+
+
+3. You can also check test suite results inside test machine by clicking on the **Test Machine** of your choice.
+
-2. Click on a Test Plan Result. The test plan result page will look like this:
- 
-3. Click on a test case. OR if you choose Test suites from the drop-down, click on a test suite. This is how results will appear if you choose ‘Test Suite Results.
- 
-4. The right side of the screen shows the test results for a specific test suite or a test machine.
+Here is a quick GIF demonstrating how to view test reports in Testsigma.
+
+
+---
+
+## **Additional Actions on Results**
+
+There are multiple actions that you can take on these results. These actions are:
+
+1. **Rerun**: You can initiate reruns of the test cases by clicking on Rerrun.
+
-5. Choose the different build numbers on the left side, under Run History, to view how the results have changed over time
+2. **Export Reports**: You can download the report in Junit and MS Excel Sheet at test case/test suite/test machine levels by clicking on the **Export** icon.
+
-See the steps above in action in the gif below:
+3. **Test Run Details**: You can see the test run details below the result overview.
+
-
\ No newline at end of file
+---
\ No newline at end of file
diff --git a/src/pages/docs/reports/runs/overview.md b/src/pages/docs/reports/runs/overview.md
index b680366d..0e37e8cb 100644
--- a/src/pages/docs/reports/runs/overview.md
+++ b/src/pages/docs/reports/runs/overview.md
@@ -1,6 +1,6 @@
---
title: "Test Runs - An Overview"
-metadesc: " To understand the quality you need to understand the results of your test execution. Here is a overview of test run results in Testsigma."
+metadesc: "To understand the quality you need to understand the results of your test execution. Here is a overview of test run results in Testsigma."
noindex: false
order: 13.21
page_id: "Test Runs - An Overview"
@@ -9,86 +9,62 @@ contextual_links:
- type: section
name: "Contents"
- type: link
- name: "What can you do on the Run Results page"
- url: "#what-can-you-do-on-the-run-results-page"
+ name: "Possible Actions on Run Results Page"
+ url: "#possible-actions-on-run-results-page"
+- type: link
+ name: "Steps to Rerun From Run Results"
+ url: "#steps-to-rerun-from-run-results"
---
---
-The purpose of test automation is to be able to quickly understand the state of quality in your application. To understand the quality you need to understand the results of your test execution and where test reports come in.
-
-In Testsigma, these reports can be viewed directly in the Testsigma application or can be downloaded. Reports are automatically created and are useful for debugging failing tests and helping managers understand the state of quality of the application under test (AUT).
-
-Testsigma provides a central repository for all the test results.
-Simply navigate to the **Test Development > Run Results** page.
+The purpose of test automation is to be able to understand the state of quality in your application quickly. To understand the quality, you need to understand the results of your test execution, and that's where test reports come in.
+In Testsigma, you can view reports directly in the application. Reports are automatically created and help debug failing tests and help managers understand the state of quality of the application under test (AUT). This article discusses the overview of run results page in Testsigma.
---
-## **What can you do on the Run Results page**
-
-1. Observe results for all Test Plan executions: Search, Sort & Filter
-
- a. **Search option on the top right:** To search for a run result by name, use this. The search will filter all the run results names that contain your search query.
-
- b. **Sort:** Click on the sort button — the button next to the search button on the top right to sort the list of Run Results according to your preference.
-
-
-
- You can sort the list Ascending or Descending based on the below fields
-
- * Name
-
- * Test Lab/Type
-
- * Created Date
-
- * Updated Date
- * Last Run
+## **Possible Actions on Run Results Page**
+The following are the actions possible on **Run Results** page:
- c. **Filter:** Click on the filter button - the button next to sort button on the top right. A 'Filters' layover, as shown in the screenshot below, appears.
-
+ - **Search**: To search for a run result by name, use this. The search will filter all the run results names that contain your search query.
+ 
+ - **Sort by:** Click on the **Sort by** button to sort the list of Run Results according to your preference. You can sort the list based on the **Title**, **Created Date**, **Updated Date**, **Last Run**, **Ascending** or **Descending**.
+ 
- You can filter the Test Plans based on the below options:
+ - **Filter:** Click on **Show Filters** to add filter and sort results according to your preference. You can add filters based on the options **Created By**, **Last Run Date**, **Created Date**, **Updated Date**, **Last Run Date**, and **Labels**.
+ 
- * Name
- * Created By
-
- * Status
-
- * Created Date
-
- * Updated Date
-
- * Last Run Date
-
- * Labels
-
-
-
-2. Drill down to test case / test suite / test machine level reports
-3. Understand reasons for failure
-4. Note downtime for each execution
+Here is a quick GIF demonstrating actions possible on run results page.
+
+Testers may need to rerun failed test cases, or all test cases from a particular test run result, after a hotfix or a change in environment. Follow the steps below to rerun test cases from test run results in Testsigma.
---
-## To know more about the different components of the run results page, refer to the documents below:
-1. [Drill-down Reports](https://testsigma.com/docs/reports/runs/drill-down-reports/)
+## **Steps to Rerun from Run Results**
+
+1. Navigate to **Run Results** page and click on a **Test Plan Result**.
+
-2. [Test Machine Level Reports](https://testsigma.com/docs/reports/runs/test-machine-reports/)
-3. [Test Suite Level Reports](https://testsigma.com/docs/reports/runs/test-suite-reports/)
+2. From results page, click on **Rerun**.
+
-4. [Test Case Reports](https://testsigma.com/docs/reports/runs/test-case-reports/)
-5. [Filter and Custom Reports](https://testsigma.com/docs/reports/runs/filter-custom-reports/)
+3. On the **Re-run options** prompt, you will see the following options:
+
+ - **All Test Cases:** This will rerun all the test cases in the selected run.
+ - **All Failed Test Cases:** This will rerun all the failed test cases in the selected run.
+ - **Select Cases for Re-Run:** This will allow you to select the test cases you want to rerun.
-6. [Export Reports - JUnit](https://testsigma.com/docs/reports/export-reports/export-reports-junit/)
+4. Choose the option and click on **Start execution** to rerun.
+
-7. [Export Reports - XLS](https://testsigma.com/docs/reports/export-reports/export-report-xls/)
+Here is a quick GIF demonstrating how to rerun tests from run results in Testsigma.
+
-8. [Export Reports - PDF](https://testsigma.com/docs/reports/export-reports/export-report-pdf/)
\ No newline at end of file
+---
\ No newline at end of file
diff --git a/src/pages/docs/test-cases/create-steps-recorder/android-apps/reuse-elements.md b/src/pages/docs/test-cases/create-steps-recorder/android-apps/reuse-elements.md
index fb4c6c28..7e74ad9b 100644
--- a/src/pages/docs/test-cases/create-steps-recorder/android-apps/reuse-elements.md
+++ b/src/pages/docs/test-cases/create-steps-recorder/android-apps/reuse-elements.md
@@ -29,6 +29,7 @@ You should know how to [record a test case via Testsigma’s test Recorder.](htt
---
+
##**How to reuse pre-recorded elements via Testsigma’s test Recorder for an android project:**
1. Create a test case in which you will be reusing your pre-recorded elements.
diff --git a/src/pages/docs/test-cases/create-steps-recorder/ios-apps/update-elements.md b/src/pages/docs/test-cases/create-steps-recorder/ios-apps/update-elements.md
index bd5b7803..9764c24b 100644
--- a/src/pages/docs/test-cases/create-steps-recorder/ios-apps/update-elements.md
+++ b/src/pages/docs/test-cases/create-steps-recorder/ios-apps/update-elements.md
@@ -22,12 +22,14 @@ When you update the structure of your iOS application, you will need to update t
---
-##**Pre-requisites:**
+
+## **Pre-requisites:**
You should already know [how to capture elements using Test Recorder](https://testsigma.com/docs/test-cases/create-steps-recorder/ios-apps/overview/).
---
+
##**How to update an element via Test Recorder:**
1. Create a Test Case using Test Recorder in your iOS Project.
diff --git a/src/pages/docs/test-cases/create-steps-recorder/web-apps/add-steps-manually.md b/src/pages/docs/test-cases/create-steps-recorder/web-apps/add-steps-manually.md
index e3c2ce9b..232b18f9 100644
--- a/src/pages/docs/test-cases/create-steps-recorder/web-apps/add-steps-manually.md
+++ b/src/pages/docs/test-cases/create-steps-recorder/web-apps/add-steps-manually.md
@@ -33,7 +33,7 @@ You should already know how-to, or have:
---
-##**Steps to follow:**
+## **Steps to follow:**
1. Create a test case via the Testsigma test recorder.
2. Hover on the test step after (or before) which you want to add more test steps.
diff --git a/src/pages/docs/test-cases/create-steps-recorder/web-apps/reorder.md b/src/pages/docs/test-cases/create-steps-recorder/web-apps/reorder.md
index d10c2e8f..db308cb8 100644
--- a/src/pages/docs/test-cases/create-steps-recorder/web-apps/reorder.md
+++ b/src/pages/docs/test-cases/create-steps-recorder/web-apps/reorder.md
@@ -33,6 +33,7 @@ You can reorder the test steps you record in a test case. Here’s how.
---
+
##**Reordering recorded test steps in a Web Project:**
1. Create a Test Case using Test recorder with multiple test steps.
diff --git a/src/pages/docs/test-cases/create-steps-recorder/web-apps/reuse-elements.md b/src/pages/docs/test-cases/create-steps-recorder/web-apps/reuse-elements.md
index ede65f28..701e56ec 100644
--- a/src/pages/docs/test-cases/create-steps-recorder/web-apps/reuse-elements.md
+++ b/src/pages/docs/test-cases/create-steps-recorder/web-apps/reuse-elements.md
@@ -35,7 +35,7 @@ When you record elements via Test recorder chrome extension, they are saved as e
---
-##**Reusing elements recorded via the Testsigma test recorder chrome extension:**
+## **Reusing elements recorded via the Testsigma test recorder chrome extension:**
1. Create a new test case in the same Project.
2. Start recording the test steps.
diff --git a/src/pages/docs/test-cases/create-steps-recorder/web-apps/update-elements.md b/src/pages/docs/test-cases/create-steps-recorder/web-apps/update-elements.md
index 26a8a463..bcbdba32 100644
--- a/src/pages/docs/test-cases/create-steps-recorder/web-apps/update-elements.md
+++ b/src/pages/docs/test-cases/create-steps-recorder/web-apps/update-elements.md
@@ -61,5 +61,4 @@ You can select any of these options for identifier type.
Click ‘Update’ button to finalize the changes.
-
-
+---
\ No newline at end of file
diff --git a/src/pages/docs/test-cases/create-steps-restapi/add-body-data.md b/src/pages/docs/test-cases/create-steps-restapi/add-body-data.md
index 688f8026..ddb847e3 100644
--- a/src/pages/docs/test-cases/create-steps-restapi/add-body-data.md
+++ b/src/pages/docs/test-cases/create-steps-restapi/add-body-data.md
@@ -3,7 +3,7 @@ title: "Body Data"
page_title: "Adding Body Data in API Request"
metadesc: "Adding body data in RESTful API testing is sending additional data to the server in the body of the request. Learn how to add Body Data in API Request in Testsigma"
noindex: false
-order: 4.64
+order: 4.94
page_id: "Adding Body Data in API Request"
search_keyword: ""
warning: false
diff --git a/src/pages/docs/test-cases/create-steps-restapi/adding-headers.md b/src/pages/docs/test-cases/create-steps-restapi/adding-headers.md
index 95757ef5..8282d7d9 100644
--- a/src/pages/docs/test-cases/create-steps-restapi/adding-headers.md
+++ b/src/pages/docs/test-cases/create-steps-restapi/adding-headers.md
@@ -3,7 +3,7 @@ title: "Headers"
page_title: "Headers in API Request"
metadesc: "APIs require particular headers and requests, to provide more metadata about your operation. Learn about headers in API Request in Testsigma"
noindex: false
-order: 4.65
+order: 4.95
page_id: "Headers in API Request"
search_keyword: ""
warning: false
diff --git a/src/pages/docs/test-cases/create-steps-restapi/adding-parameters.md b/src/pages/docs/test-cases/create-steps-restapi/adding-parameters.md
index 3d67d19f..addf77ef 100644
--- a/src/pages/docs/test-cases/create-steps-restapi/adding-parameters.md
+++ b/src/pages/docs/test-cases/create-steps-restapi/adding-parameters.md
@@ -3,7 +3,7 @@ title: "Parameters"
page_title: "Adding Parameters in API Request"
metadesc: "Adding parameters in RESTful API Testing is sending data to a server in order to get a response. Learn how to add Parameters in API Request in Testsigma"
noindex: false
-order: 4.63
+order: 4.93
page_id: "Adding Parameters in API Request"
search_keyword: ""
warning: false
diff --git a/src/pages/docs/test-cases/create-steps-restapi/api-resquest.md b/src/pages/docs/test-cases/create-steps-restapi/api-resquest.md
index d6fb4eb7..d461c331 100644
--- a/src/pages/docs/test-cases/create-steps-restapi/api-resquest.md
+++ b/src/pages/docs/test-cases/create-steps-restapi/api-resquest.md
@@ -3,7 +3,7 @@ title: "API Request"
page_title: "Add API Request in RESTful API in Testsigma"
metadesc: "Add API Request in RESTful API | Run your request with the help of the URL, method, and other optional values such as parameters, body, headers, and authorization"
noindex: false
-order: 4.62
+order: 4.92
page_id: "Add API Request in RESTful API"
search_keyword: ""
warning: false
diff --git a/src/pages/docs/test-cases/create-steps-restapi/attachments-rest-api.md b/src/pages/docs/test-cases/create-steps-restapi/attachments-rest-api.md
index a4943142..3b93ad7e 100644
--- a/src/pages/docs/test-cases/create-steps-restapi/attachments-rest-api.md
+++ b/src/pages/docs/test-cases/create-steps-restapi/attachments-rest-api.md
@@ -1,9 +1,9 @@
---
title: "Attachments"
page_title: "Attachments"
-metadesc: "Attachments in RESTful API testing is the ability to send/receive files such as images, docs, and videos as part of an API request or response | Learn about Attachments in RESTful API"
+metadesc: "Attachments in RESTful API testing is the ability to send/receive files such as images, docs, and videos as part of an API request or response"
noindex: false
-order: 4.691
+order: 4.991
page_id: "Attachments"
search_keyword: ""
warning: false
diff --git a/src/pages/docs/test-cases/create-steps-restapi/authorization-request.md b/src/pages/docs/test-cases/create-steps-restapi/authorization-request.md
index efd8c105..1fead273 100644
--- a/src/pages/docs/test-cases/create-steps-restapi/authorization-request.md
+++ b/src/pages/docs/test-cases/create-steps-restapi/authorization-request.md
@@ -1,9 +1,9 @@
---
title: "Authorization "
page_title: "Authorization in API Request"
-metadesc: "Authorization in RESTful API testing verifies that a user has the all permissions to access a specific resource. Learn about Authorization in API Request in Testsigma"
+metadesc: "Authorization in RESTful API testing verifies that a user has the all necessary permissions to access a specific resource"
noindex: false
-order: 4.66
+order: 4.96
page_id: "Authorization in API Request"
search_keyword: ""
warning: false
diff --git a/src/pages/docs/test-cases/create-steps-restapi/restful-api-overview.md b/src/pages/docs/test-cases/create-steps-restapi/restful-api-overview.md
index b262c658..8fde317d 100644
--- a/src/pages/docs/test-cases/create-steps-restapi/restful-api-overview.md
+++ b/src/pages/docs/test-cases/create-steps-restapi/restful-api-overview.md
@@ -1,9 +1,9 @@
---
title: "RESTful API Testing - Overview"
page_title: "RESTful API Testing in Testsigma"
-metadesc: "Add RESTful API Testing in Test Step"
+metadesc: "RESTful APIs allow you to access resources using uniform methods & protocols | This article discusses RESTful API Testing in Testsigma"
noindex: false
-order: 4.61
+order: 4.91
page_id: "Add RESTful API Testing in Test Step"
search_keyword: ""
warning: false
diff --git a/src/pages/docs/test-cases/create-steps-restapi/store-variables.md b/src/pages/docs/test-cases/create-steps-restapi/store-variables.md
index e2b611c5..ca661fce 100644
--- a/src/pages/docs/test-cases/create-steps-restapi/store-variables.md
+++ b/src/pages/docs/test-cases/create-steps-restapi/store-variables.md
@@ -3,7 +3,7 @@ title: "Store Variables"
page_title: "Store Variables"
metadesc: "tored variables are variables that are used to store data from a response body or response headers | Learn about Store Variables in Testsigma"
noindex: false
-order: 4.68
+order: 4.98
page_id: "Store Variables"
search_keyword: ""
warning: false
diff --git a/src/pages/docs/test-cases/create-steps-restapi/stored-objects.md b/src/pages/docs/test-cases/create-steps-restapi/stored-objects.md
index 7bb23b25..1cfcc7a4 100644
--- a/src/pages/docs/test-cases/create-steps-restapi/stored-objects.md
+++ b/src/pages/docs/test-cases/create-steps-restapi/stored-objects.md
@@ -3,7 +3,7 @@ title: "Stored Objects"
page_title: "Stored Objects"
metadesc: "Stored objects refer to the data that is stored in the database and is used to test the API. Learn about Stored Objects in RESTful API in Testsigma"
noindex: false
-order: 4.692
+order: 4.992
page_id: "Stored Objects"
search_keyword: ""
warning: false
diff --git a/src/pages/docs/test-cases/create-steps-restapi/verifications-request.md b/src/pages/docs/test-cases/create-steps-restapi/verifications-request.md
index db6336ba..1260a119 100644
--- a/src/pages/docs/test-cases/create-steps-restapi/verifications-request.md
+++ b/src/pages/docs/test-cases/create-steps-restapi/verifications-request.md
@@ -1,9 +1,9 @@
---
-title: "Verifications "
+title: "Verifications"
page_title: "Verifications Request"
metadesc: "Check whether the Rest API is functioning correctly by adding verification and assertions. Learn about Verifications Request in Testsigma"
noindex: false
-order: 4.67
+order: 4.97
page_id: "Verifications Request"
search_keyword: ""
warning: false
diff --git a/src/pages/docs/test-cases/create-steps.md b/src/pages/docs/test-cases/create-steps.md
index a3676518..cf3a55e3 100644
--- a/src/pages/docs/test-cases/create-steps.md
+++ b/src/pages/docs/test-cases/create-steps.md
@@ -1,6 +1,6 @@
---
-title: "Create test steps in Testsigma"
-metadesc: "How to create Test Steps in Testsigma "
+title: "Create Test Steps in Testsigma"
+metadesc: "This article discusses creating test steps manually using simple English (NLPs) as well as with a recorder for web, mobile web, Android, & iOS app in Testsigma"
noindex: false
order: 4.30
page_id: "Create Test Steps in Testsigma"
@@ -12,71 +12,156 @@ contextual_links:
name: "Prerequisites"
url: "#prerequisites"
- type: link
- name: "Ways to create Test Steps"
- url: "#ways-to-create-test-steps"
+ name: "Creating Test Steps Manually"
+ url: "#creating-test-steps-manually"
- type: link
- name: "Web & Mobile Web"
- url: "#web--mobile-web"
-- type: link
- name: "iOS"
- url: "#ios"
-- type: link
- name: "Android"
- url: "#android"
+ name: "Creating Test Steps Using Test Recorder"
+ url: "#creating-test-steps-using-test-recorder"
---
---
-In Testsigma terminology, each automated action executed by the test script is a Test Step. For example, in a login form “Enter username in the username field ” is a Test Step.
+In Testsigma terminology, each automated action executed by the test script is a test step. For example, in a login form, **Enter <username> in the <username> field** is a test step. This article discusses creating test steps for web, mobile web, Android, and iOS applications using Testsigma recorder & simple English (NLPs).
-[[info | NOTE:]]
-|In Testsigma we will be writing test steps in simple English, which automatically gets converted into automated actions.
+---
-
+## **Prerequisites**
----
-##**Pre-requisites:**
+- You should have Testsigma recorder installed.
-This document assumes that you know how to [Create a test case](https://testsigma.com/docs/test-cases/manage/add-edit-delete/).
+- You should know about [test step types](https://testsigma.com/docs/test-cases/step-types/overview/).
+
+- Web/Android/iOS application you want to test.
-
---
-##**Ways to create Test Steps:**
-There are two different ways to add test steps in a Test case.
- 1. Writing steps manually using simple English.
- 2. Generating test scripts through a Test Recorder.
+## **Creating Test Steps Manually**
-
+### **Web & Mobile Web**
-Follow the links to know how to use these approaches for:
+1. Navigate to **Create Tests > Test Cases**, and click on **Create Test Cases**.
----
-##**Web & Mobile Web**
+
- * [Write Tests using simple English](https://testsigma.com/docs/test-cases/create-steps-nl/web-apps/overview/)
- * [Record Steps using Test step Recorder](https://testsigma.com/docs/test-cases/create-steps-recorder/web-apps/overview/)
+2. Enter **Name** and click on **Add new step**.
-
+
----
-##**iOS**
+3. Use NLPs to create test steps as per the test case scenario. For example, if you’re creating test steps for the login page, your test steps will be:
+
+ 1. Navigate to https://simply-travel.testsigma.com/
+ 2. Click on **Login/Sign Up**
+ 3. Click on **Login**
+ 4. Enter <**email**> in the <**email address**> field
+ 5. Click on **Continue**
+ 6. Enter <**password**> in the <**password**> field
+ 7. Click on **Submit**
+
+Here's a screenshot of reproduced test steps in Testsigma application.
+
+
+
+### **iOS Apps**
+
+1. Navigate to **Create Tests > Test Cases**, and click on **Create Test Cases**.
+
+
+
+2. Enter **Name** and click on **Add new step**.
+
+
+
+3. Use NLPs to create test steps as per the test case scenario.
+
+### **Android Apps**
+
+1. Navigate to **Create Tests > Test Cases**, and click on **Create Test Cases**.
+
+
+
+2. Enter **Name** and click on **Add new step**.
+
+
+
+3. Use NLPs to create test steps as per the test case scenario.
+
+[[info | **NOTE**:]]
+| - By default the first step for Android and iOS applications is **Launch App**.
+| - You can also add steps above and below a test step by clicking on **Step Above** & **Step Below**.
+| 
+
+
+
+Here's a sample GIF demonstrating creating test steps manually for a Web Application.
- * [Write Tests using simple English](https://testsigma.com/docs/test-cases/step-types/overview/)
- * [Record Steps using Test Recorder](https://testsigma.com/docs/test-cases/create-steps-recorder/ios-apps/overview/)
+
-
---
-##**Android**
- * [Write Tests using simple English](https://testsigma.com/docs/test-cases/step-types/overview/)
- * [Record Steps using Test Recorder](https://testsigma.com/docs/test-cases/create-steps-recorder/android-apps/overview/)
+## **Creating Test Steps Using Test Recorder**
+
+### **Web & Mobile Web**
+
+1. Navigate to **Create Tests > Test Cases**, and click on **Create Test Case**.
+
+
+
+
+2. Create a test step using the URL that you want to automate and click on **Create Step**.
+
+
+
+
+3. Click on **Record**.
+
+
+
+
+4. A new window will open the given URL and you can record the test steps.
+
+
+
+
+[[info | **NOTE**:]]
+| Please wait a few seconds until the web page is fully loaded so the extension can collect information from the page in the background.
+
+5. Once the first web page is fully loaded, start interacting and performing actions on the page.
+
+
+6. The actions will be recorded and added to the test case in the background.
+
+
+7. Once the required actions are complete, click on **Done** to switch back to the test case details page.
+
+
+8. You can see the steps recorded in the test case details page.
+
+
+
+### **Android & iOS Apps**
+
+1. Navigate to **Create Tests > Test Cases**, click on **Create Test Case**.
+
+
+2. On **Test Case Details** page, click on **Record**.
+
+
+3. On **Record test steps** overlay, select **Test Lab**, **Test Machine** and **App Source** you want to test.
+
+4. Click on **Record**.
+
+5. Perform the actions on the application and once the required actions are complete, stop the recording to switch back to the test case details page.
+6. The test case details page will display the steps performed on the application.
+
+Here's a sample GIF demonstrating creating test steps using the recorder for a Web Application.
+
+---
\ No newline at end of file
diff --git a/src/pages/docs/test-cases/create-test-steps/actions-and-options-manual/bulk-actions.md b/src/pages/docs/test-cases/create-test-steps/actions-and-options-manual/bulk-actions.md
new file mode 100644
index 00000000..33df457f
--- /dev/null
+++ b/src/pages/docs/test-cases/create-test-steps/actions-and-options-manual/bulk-actions.md
@@ -0,0 +1,51 @@
+---
+title: "Bulk Actions"
+pagetitle: "Manage test steps efficiently with bulk actions in Testsigma."
+metadesc: "Streamline your testing process by using Testsigma's Bulk Actions feature to perform actions like selecting all, updating settings, creating blocks, and more in bulk."
+noindex: false
+order: 4.613
+page_id: "Bulk Actions"
+warning: false
+contextual_links:
+- type: section
+ name: "Contents"
+- type: link
+ name: "Prerequisites"
+ url: "#prerequisites"
+- type: link
+ name: "Using Bulk Actions on Test Steps"
+ url: "#using-bulk-actions-on-test-steps"
+---
+
+---
+
+Using Bulk Actions in Testsigma simplifies managing multiple test steps. You can perform actions such as selecting all, updating settings, creating blocks, creating step groups, and deleting multiple test steps. This guide will help you understand how to use Bulk Actions effectively.
+
+---
+
+## **Prerequisites**
+
+- You should know about [projects](https://testsigma.com/docs/projects/overview/) in Testsigma.
+
+- You should know how to [manage a test case](https://testsigma.com/docs/test-cases/manage/add-edit-delete/).
+
+- You should know how to [manage test steps](https://testsigma.com/docs/test-cases/step-types/natural-language/).
+
+---
+
+## **Using Bulk Actions on Test Steps**
+
+Follow these steps to use Bulk Actions for your test steps:
+
+1. Select a **Step** on the **Test Case Details** page by hovering your mouse over the test step number. The test step number will change into a **checkbox** as you hover.
+2. Click the **checkboxes** next to each test step to select the **test steps** you want to include in the **bulk action**.
+3. The bulk actions option appears when you've selected any test step in the **Test Case Details** page. To select all the steps at once, click the **Select All** button in the menu bar. 
+4. You can perform bulk actions on multiple test steps by selecting them on the menu bar. The actions available are:
+ - **Select All**: This option allows you to select all the test steps on the current page.
+ - **Update Settings**: You can use this option to update settings for the selected test steps all at once. For more information, refer to [Update Settings](https://testsigma.com/docs/test-cases/create-steps-nl/step-settings/#update-settings).
+ - **Create Block**: Use this option to create a block from the selected test steps. This will help you manage and structure your test cases. For more information, refer to [Step Block](https://testsigma.com/docs/test-cases/step-types/block/#create-a-block-using-bulk-action).
+ - **Create Step Group**: This action lets you create a step group containing the selected test steps. Step groups help you organise and reuse test steps. For more information, refer to [Step Group](https://testsigma.com/docs/test-cases/step-types/step-group/#create-step-group-from-a-test-case).
+ - **Delete**: You can delete the selected test steps in bulk if they are no longer needed.
+5. Click on **Exit Bulk Action** in the top right corner of the screen within the menu bar to exit the Bulk Action mode. 
+
+---
diff --git a/src/pages/docs/test-cases/create-test-steps/actions-and-options-manual/step-options.md b/src/pages/docs/test-cases/create-test-steps/actions-and-options-manual/step-options.md
new file mode 100644
index 00000000..b0492c57
--- /dev/null
+++ b/src/pages/docs/test-cases/create-test-steps/actions-and-options-manual/step-options.md
@@ -0,0 +1,124 @@
+---
+title: "Test Step Options"
+page_title: "Test Step Options | Testsigma Documentation"
+metadesc: "Explore Testsigma's Test Step Options - Configure, manage, and optimise your test steps efficiently. Enhance testing workflow with customisation and control."
+noindex: false
+order: 4.611
+page_id: "Test Step Actions"
+warning: false
+contextual_links:
+- type: section
+ name: "Contents"
+- type: link
+ name: "Prerequesties"
+ url: "#prerequesties"
+- type: link
+ name: "Clear Step"
+ url: "#clear-step"
+- type: link
+ name: "Step Settings"
+ url: "#step-settings"
+- type: link
+ name: "Disable Step"
+ url: "#disable-step"
+- type: link
+ name: "Ignore Step Result"
+ url: "#ignore-step-result"
+- type: link
+ name: "Enable Visual Testing"
+ url: "#enable-visual-testing"
+- type: link
+ name: "Clone Step"
+ url: "#clone-step"
+- type: link
+ name: "Delete Step"
+ url: "#delete-step"
+- type: link
+ name: "Steps Above and Below"
+ url: "#steps-above-and-below"
+- type: link
+ name: "Reorder Test Step"
+ url: "#reorder-test-step"
+---
+
+---
+
+In Testsigma, you can customize test steps within a test case using test step options. These options allow you to control and customize various aspects of test execution, such as data inputs, assertions, and behavior, enhancing the test scenario's flexibility and accuracy. This article discusses all test step options available in Testsigma.
+
+---
+
+## **Prerequesties**
+
+- You should know how to create **test steps** and [manage a test case](https://testsigma.com/docs/test-cases/manage/add-edit-delete/).
+
+
+---
+
+## **Clear Step**
+
+Click on the **test step**, then click the **Eraser** icon to clear the step in a single click. Clearing the test step will remove any existing actions or data within the step. 
+
+---
+
+## **Step Settings**
+
+Click on the **test step**, then click the **Settings** icon or the **ellipsis** icon to open a dropdown list of **Test Step Settings**. Select the **Step Settings** option from this list to configure particular settings for the test step, such as timeouts, retries, prerequisites, or other settings. Refer to [Test Step Settings](https://testsigma.com/docs/test-cases/create-steps-nl/step-settings/) for more information. 
+
+---
+
+## **Disable Step**
+
+Click on the **test step**, then click on either the **Forbidden** icon or the **ellipsis** button to open a dropdown list of **Test Step Settings**. Select the **Disable step** option from this list to temporarily deactivate the selected step in the test case. This will prevent the test step from running during execution. 
+
+---
+
+## **Ignore Step Result**
+
+Click on the **test step**, and then click the **ellipsis** icon to open a dropdown list of **Test Step Settings**, then select the **Ignore Step Result** option from this list to exclude the outcome of a specific step from the overall test result. 
+
+---
+
+## **Enable Visual Testing**
+
+Click on the **test step**, and then click the **ellipsis** icon to open a dropdown list of **Test Step Settings**. Select the **Enable Visual Testing** option from this list to capture and compare how the user interface of an application looks between different builds or versions. Refer to [Visual Testing](https://testsigma.com/docs/visual-testing/configure-test-steps/) for more information. 
+
+---
+
+## **Clone Step**
+
+Click on the **test step**, then click the **ellipsis** icon to open a dropdown list of **Test Step Settings** and select the **Clone Step** option. It will create an identical copy of the selected step, which saves time when you need multiple similar steps within the same test case. 
+
+---
+
+## **Delete Step**
+
+Click on the **test step**, then click the **ellipsis** icon to open a dropdown list of **Test Step Settings**. Select the **Delete Step** option from this list, permanently removing the selected step from the test case, helping streamline test maintenance and organisation. 
+
+---
+
+## **Steps Above and Below**
+
+You can add steps above and below a test step by clicking on **Step Above** & **Step Below**.
+
+If you click on **Step Above**, you can add another step above the test step, while if you click on **Step Below**, you can add another step below the test step.
+
+
+
+---
+
+## **Reorder Test Step**
+
+Follow these steps to reorder test steps within a test case:
+
+1. Create a **test case** with a list of the **test steps**.
+2. You will find an **⋮⋮** (**vertical ellipsis**) icon before each test step. This icon represents the drag-and-drop handle for reordering.
+3. Hover your cursor over the **⋮⋮** icon for the test step you wish to move, then click and hold the icon to grab the test step and reorder it.
+4. Drag the test step to the desired position within the test case's list of test steps while holding it. As you move the test step, you will see a visual indicator of where the test step will be placed once you release it.
+5. Drop the test step into its new position by releasing the mouse button. Testsigma will automatically update the test step order in the test case after you release the test step.
+6. After reordering your test steps, click the **Save New Order** option in the screen's top right corner to save the new order.
+
+Here is a quick GIF demonstrating how to reorder test steps in Testsigma.
+
+
+
+---
diff --git a/src/pages/docs/test-cases/create-test-steps/actions-and-options-manual/step-settings.md b/src/pages/docs/test-cases/create-test-steps/actions-and-options-manual/step-settings.md
new file mode 100644
index 00000000..3f38a91a
--- /dev/null
+++ b/src/pages/docs/test-cases/create-test-steps/actions-and-options-manual/step-settings.md
@@ -0,0 +1,67 @@
+---
+title: "Test Step Settings"
+page_title: "Test Step Settings | Testsigma Documentation"
+metadesc: "Configure wait times, retries, visuals, and other settings for efficient test automation in Testsigma using Test Step Settings and customise test execution."
+noindex: false
+order: 4.612
+page_id: "test-step-settings-testsigma"
+warning: false
+contextual_links:
+- type: section
+ name: "Contents"
+- type: link
+ name: "Prerequisites"
+ url: "#prerequisites"
+- type: link
+ name: "Use Test Step Settings"
+ url: "#use-test-step-settings"
+- type: link
+ name: "Update Step Settings"
+ url: "#update-step-settings"
+---
+
+---
+
+In Testsigma, you can control how each test step behaves in your test cases by using test step settings. These settings allow you to decide how your test cases run and show results. You can also use them to set step conditions and attempt them again if required.
+
+---
+
+## **Prerequisites**
+
+
+- You should know about [projects](https://testsigma.com/docs/projects/overview/) in Testsigma.
+
+- You should know how to [manage a test case](https://testsigma.com/docs/test-cases/manage/add-edit-delete/).
+
+- You should know how to [manage test steps](https://testsigma.com/docs/test-cases/step-types/natural-language/).
+
+---
+
+## **Use Test Step Settings**
+
+To use **test step settings**, click either the **Settings** icon or the **ellipsis** icon on a particular test step. Then, choose **Step Settings** from the list that appears to open the **Test Step Settings** panel on the test case page.
+
+Below is a summary of the available settings:
+
+| **Settings** | **Description** |
+|:------------------|:-------------|
+|**Max wait time**|Set the Maximum Wait Time limit for completing the test step. It will fail if the test step takes longer than the specified time (up to a maximum of 120 seconds).|
+|**No. of Retries on Step Failure**|Select the **Number of Retries on Step Failure** from the dropdown menu (up to 10 times) to decide how many times you want to attempt to execute the test step again if it fails.|
+|**Pre-Requisite**|Select a prerequisite step from the list of available steps in the same test case. This step must be successfully done before the current step runs.|
+|**Stop Test Case execution on Test Step**|It allows you to terminate test execution if the test fails at any step. By default, this option is checked, and test case execution will stop if the test step fails.|
+|**Ignore this step result in Test Case Result**|It allows you to exclude the outcome of a particular step from the overall test result.|
+|**Disable Step**|It allows you to capture and compare the visual appearance of an application's user interface between different builds or versions.|
+|**Enable Visual Testing for the Step**|You can disable the test step by choosing this option, and the test step will not run. By default, this option is unchecked.|
+
+Here is a quick GIF demonstrating the above workflow: 
+
+---
+
+## **Update Step Settings**
+
+To update several test steps, click the **checkboxes** next to the **test steps** you want to update and then click on **Update Settings** in the menu bar to open a popup window where you can make changes to the settings. 
+
+[[info | NOTE:]]
+| Update Step Setting does not allow updating the **Pre-Requisite** and **Number of Retries on Step Failure**. You should use **Test Step Settings** for each step individually.
+
+---
\ No newline at end of file
diff --git a/src/pages/docs/test-cases/create-test-steps/actions-and-options-recorder/bulk-actions.md b/src/pages/docs/test-cases/create-test-steps/actions-and-options-recorder/bulk-actions.md
new file mode 100644
index 00000000..e7cef727
--- /dev/null
+++ b/src/pages/docs/test-cases/create-test-steps/actions-and-options-recorder/bulk-actions.md
@@ -0,0 +1,61 @@
+---
+title: "Bulk Actions"
+metadesc: "This article discusses bulk actions you can perform on recorded test steps in Testsigma’s test recorder UI for an android, iOS or a web project"
+noindex: false
+order: 4.624
+page_id: "Test Recorder - Bulk Actions in a Web Project"
+warning: false
+contextual_links:
+- type: section
+ name: "Contents"
+- type: link
+ name: "Prerequisites"
+ url: "#prerequisites"
+- type: link
+ name: "Bulk Actions on Test Steps"
+ url: "#bulk-actions-on-test-steps"
+---
+
+---
+
+When test steps are recorded using test recorder, Testsigma gives you the option to select multiple test steps at a time and then perform bulk actions on your selection. In this document, we will discuss bulk actions and how to perform them.
+
+
+---
+
+## **Prerequisites**
+
+- You should know about [projects](https://testsigma.com/docs/projects/overview/) in Testsigma.
+
+- You should have [Testsigma's step test recorder](https://testsigma.com/docs/test-step-recorder/install-chrome-extension/) installed.
+
+- You should know how to [manage a test case](https://testsigma.com/docs/test-cases/manage/add-edit-delete/).
+
+---
+
+## **Bulk Actions on Test Steps**
+
+Once the steps are recorded, click the **checkboxes** next to each test step to select the **steps** you want to include in the **bulk action**.
+
+
+
+You can perform following actions on selected test steps:
+- **Bulk Update**: You can use this option to update settings for the selected test steps all at once.
+
+ 
+
+- **Create Block**: Use this option to create a block from the selected test steps. This will help you manage and structure your test cases.
+
+ 
+
+- **Delete Selected**: You can delete the selected test steps in bulk if they are no longer needed.
+
+ 
+
+
+
+Here's a quick GIF demonstrating how to perform bulk actions on test steps.
+
+
+
+---
\ No newline at end of file
diff --git a/src/pages/docs/test-cases/create-test-steps/actions-and-options-recorder/controls-and-actions.md b/src/pages/docs/test-cases/create-test-steps/actions-and-options-recorder/controls-and-actions.md
new file mode 100644
index 00000000..35f8f0ef
--- /dev/null
+++ b/src/pages/docs/test-cases/create-test-steps/actions-and-options-recorder/controls-and-actions.md
@@ -0,0 +1,78 @@
+---
+title: "Controls and Actions"
+page_title: "Controls and Actions in Android Test Recorder"
+metadesc: "You can generate test steps in plain English by recording your actions for android & iOS apps. Learn controls & actions available in Testsigma application"
+noindex: false
+order: 4.623
+page_id: "Controls and Actions"
+warning: false
+contextual_links:
+- type: section
+ name: "Contents"
+- type: link
+ name: "Prerequisites"
+ url: "#prerequisites"
+- type: link
+ name: "Controls and Actions Available in Test Recorder"
+ url: "#controls-and-actions-available-in-test-recorder"
+---
+
+---
+
+The test recorder in Testsigma lets you generate test steps automatically in plain English by recording your actions in the application UI. This article discusses the control options and actions in Testsigma's Test Recorder for Android and iOS applications.
+
+---
+
+## **Prerequisites**
+- You should know [how to create test cases](https://testsigma.com/docs/test-cases/manage/add-edit-delete/).
+- You should know [how to create test steps using the recorder](https://testsigma.com/docs/test-cases/create-steps-recorder/android-apps/overview/).
+- An Androiod or iOS app to test.
+
+---
+
+## **Controls and Actions Available in Test Recorder**
+
+The recording screen will have two sections:
+- **Device Controlling Section**
+
+
+- **Test Steps Section**
+
+
+Let’s review all the options available in the **Device Controlling Section**.
+1. **Mirroring mode**: Mirror mode will allow you to use the app via Testsigma to mirror real live physical device use.
+
+
+2. **Select Element**: You can click on elements and get more information about them.
+
+
+For example, if we click on **Login**, the information will be displayed under the section **Selected element attributes**. If you click on **Tap**, the step recorder will create the step as ***Tap on Login***.
+
+
+3. **Swipe By Coordinates**: The swiping action will be recorded with this option.
+
+
+4. **Tap By Coordinates:** It lets you click on an element on the screen and record the coordinates of the click.
+
+
+5. **Search Element**: This option can be used to search for an element in the app source.
+
+
+6. **Go back**: This button records the **go back** action from the current screen.
+
+
+7. **Home**: This button displays the home screen of the device.
+
+
+8. **Hide Keyboard**: This button lets you hide the keyboard in the application.
+
+
+9. **Change to landscape mode**: This button lets you switch between landscape and portrait mode.
+
+
+The **Test Steps Section** will display the actions performed on the device.
+
+[[info | **NOTE**:]]
+| **Controls and Actions** are same for both Android and iOS applications.
+
+---
diff --git a/src/pages/docs/test-cases/create-test-steps/actions-and-options-recorder/multiple-webviews.md b/src/pages/docs/test-cases/create-test-steps/actions-and-options-recorder/multiple-webviews.md
new file mode 100644
index 00000000..a3817fb7
--- /dev/null
+++ b/src/pages/docs/test-cases/create-test-steps/actions-and-options-recorder/multiple-webviews.md
@@ -0,0 +1,41 @@
+---
+title: "Recording Tests with WebView for Hybrid Apps"
+metadesc: "Recording tests with webview for hybrid apps | Learn how to switch the app from NATIVE to HYBRID app view in Testsgima app while recording tests"
+noindex: false
+order: 4.625
+page_id: "Recording tests with webview for hybrid iOS apps"
+warning: false
+---
+---
+
+While inspecting mobile elements using Testsigma's Mobile Inspector, there are instances where the mobile UI is blank or has no selectable element. In such cases, refresh the page again. If the refresh action does not show you the intended mobile UI, the app is a hybrid app that may have some WebViews that are not being rendered.
+
+In a hybrid app, web components are run completely inside a WebView control of the application. Hence, we need to switch the context between NATIVE and HYBRID to access the elements inside the WebView. Note that the context is all the relevant information that specifies the current/active state of the application and its interaction with the user. It also specifies how the server interprets commands and which commands are available to the user.
+
+Currently, Testsigma supports two contexts: **NATIVE** and **HYBRID**. By default, the mobile app is launched in a NATIVE context. To switch the app from NATIVE to HYBRID app view, click **H** from the mobile inspector panel and select WebView from the drop-down menu.
+
+
+
+The below NLP is recorded while switching to HYBRID app context:
+
+***Switch to Webview context***
+
+While switching back to NATIVE context the following NLP is recorded
+
+***Switch to Native App Context***
+
+[[info | **NOTE**:]]
+| The NLP’s are recorded to store user actions of switching views, please do not delete them if you want the execution to continue on the selected WebView.
+
+On switching to HYBRID context the drop-down shows the WebViews associated with the application. Here in the below example, there is a webview with the name **WEBVIEW_6890.1**.
+
+
+On selecting the WebView the following NLP is added,
+
+**Switch to context with name *WEBVIEW_6890.1***
+
+
+[[info | **NOTE**:]]
+| Recording tests with multiple webviews will be the same for Android and iOS applications.
+
+---
\ No newline at end of file
diff --git a/src/pages/docs/test-cases/create-test-steps/actions-and-options-recorder/step-options.md b/src/pages/docs/test-cases/create-test-steps/actions-and-options-recorder/step-options.md
new file mode 100644
index 00000000..5e6c5583
--- /dev/null
+++ b/src/pages/docs/test-cases/create-test-steps/actions-and-options-recorder/step-options.md
@@ -0,0 +1,149 @@
+---
+title: "Test Step Options"
+page_title: "Test Step Actions on the Test Recorder for a Web Project"
+metadesc: "This article discusses all actions available in Testsigma test recorder to control and customize various aspects of test execution"
+noindex: false
+order: 4.621
+page_id: "Actions you can take on recorded Test Steps in a Web Project"
+warning: false
+contextual_links:
+- type: section
+ name: "Contents"
+- type: link
+ name: "Prerequisites"
+ url: "#prerequisites"
+- type: link
+ name: "Actions on Recorded Test Steps"
+ url: "#actions-on-recorded-test-steps"
+- type: link
+ name: "Add Step"
+ url: "#add-step"
+- type: link
+ name: "Edit Step"
+ url: "#edit-step"
+- type: link
+ name: "Edit Element"
+ url: "#edit-element"
+- type: link
+ name: "Clone Step"
+ url: "#clone-step"
+- type: link
+ name: "Step details"
+ url: "#step-details"
+- type: link
+ name: "Delete Step"
+ url: "#delete-step"
+- type: link
+ name: "Steps Above and Below"
+ url: "#steps-above-and-below"
+- type: link
+ name: "Record Test Steps Anywhere"
+ url: "#record-test-steps-anywhere"
+---
+
+---
+
+In Testsigma, you can customize recorded test steps within a test case using test step options. These options allow you to control and customize various aspects of test execution, such as data inputs, assertions, and behavior, enhancing the test scenario's flexibility and accuracy. This article discusses all test step options available for recorded test steps in Testsigma.
+
+---
+
+## **Prerequisites:**
+
+- You should have [Testsigma's step test recorder](https://testsigma.com/docs/test-step-recorder/install-chrome-extension/) installed.
+
+
+- You should know how to create **test steps** and [manage a test case](https://testsigma.com/docs/test-cases/manage/add-edit-delete/).
+
+---
+
+## **Actions on Recorded Test Steps**
+
+Here's a quick GIF demonstrating all the actions available on recorded test steps in Testsigma.
+
+
+
+
+
+---
+
+## **Add Step**
+
+When you hover over a recorded test step, you see two buttons labeled **+** as shown below. This options lets you add step manually to the test case.
+
+
+
+---
+
+## **Edit Step**
+
+You can use this option to edit the test step.
+
+
+
+Alternatively, you can also edit the test steps inline, steps to be followed are:
+1. Click on the test step that needs to be changed.
+2. The required test step should become editable.
+3. Do the changes inline.
+4. Click outside the step.
+5. The change should be saved.
+
+---
+
+## **Edit Element**
+
+You can use this option to edit element in the test step.
+
+
+
+---
+
+## **Clone Step**
+
+Clicking on **Clone Step** will create an identical copy of the selected step, which saves time when you need multiple similar steps within the same test case.
+
+
+
+---
+
+## **Step Details**
+
+You can check details about a test step by clicking on the option **Step details**.
+
+
+
+---
+
+## **Delete Step**
+
+You can use this option to delete the test step.
+
+
+
+---
+
+## **Steps Above and Below**
+
+Hover on one of the test steps:
+
+
+
+
+Clicking **+** button lets you record another step before the current step. Clicking the **+** below lets you record another test step below the current step. You can also add steps manually.
+
+
+---
+
+## **Record Test Steps Anywhere**
+
+Create a test case and perform the actions you need to automate, and the recorder will capture them in steps. If you want to add steps in between, you can **click, hold, and drag** the highlighted field to add the step wherever you want.
+
+
+
+Click on **Update** to save the changes. You can use the same option to reorder the test steps as well.
+
+
+[[info | **NOTE**:]]
+| **Test Step Actions** on the Test Recorder will be the same across all application types.
+
+
+---
\ No newline at end of file
diff --git a/src/pages/docs/test-cases/create-test-steps/actions-and-options-recorder/step-settings.md b/src/pages/docs/test-cases/create-test-steps/actions-and-options-recorder/step-settings.md
new file mode 100644
index 00000000..c6ac9444
--- /dev/null
+++ b/src/pages/docs/test-cases/create-test-steps/actions-and-options-recorder/step-settings.md
@@ -0,0 +1,62 @@
+---
+title: "Test Step Settings"
+metadesc: "With test step settings, you can control how each test step behaves in your test cases | This article discussses test step settings in Testsigma"
+noindex: false
+order: 4.622
+page_id: "Test Recorder - Test Step Details for Web Project"
+warning: false
+contextual_links:
+- type: section
+ name: "Contents"
+- type: link
+ name: "Prerequisites"
+ url: "#prerequisites"
+- type: link
+ name: "Using Test Step Settings"
+ url: "#using-test-step-settings"
+
+---
+
+---
+
+In Testsigma, you can control how each test step behaves in your test cases by using Test Step Settings. These settings allow you to decide how your test cases run and show results. This article discusses all test step settings in Testsigma's test step recorder.
+
+---
+
+
+## **Prerequisites**
+
+
+- You should have [Testsigma's step test recorder](https://testsigma.com/docs/test-step-recorder/install-chrome-extension/) installed.
+
+
+- You should know how to create **test steps** and [manage a test case](https://testsigma.com/docs/test-cases/manage/add-edit-delete/).
+
+---
+
+## **Using Test Step Settings**
+
+1. Hover on one of the recorded test steps and click on **Step Details**.
+
+
+
+2. On **Step Details** prompt, you can edit the following options.
+
+
+
+| **Settings** | **Description** |
+|:------------------|:-------------|
+|**Max wait time**|Set the Maximum Wait Time limit for completing the test step. It will fail if the test step takes longer than the specified time (up to a maximum of 120 seconds).|
+|**Pre-Requisite**|Select a prerequisite step from the list of available steps in the same test case. This step must be successfully done before the current step runs.|
+|**Stop Test Case execution on Test Step**|It allows you to terminate test execution if the test fails at any step. By default, this option is checked, and test case execution will stop if the test step fails.|
+|**Ignore this step result in Test Case Result**|It allows you to exclude the outcome of a particular step from the overall test result.|
+|**Enable Visual Testing for the Step**|You can disable the test step by choosing this option, and the test step will not run. By default, this option is unchecked.|
+|**Disable Step**|It allows you to capture and compare the visual appearance of an application's user interface between different builds or versions.|
+
+
+
+Here's a quick GIF exploring all options available in test step setttings.
+
+
+
+---
\ No newline at end of file
diff --git a/src/pages/docs/test-cases/create-test-steps/overview.md b/src/pages/docs/test-cases/create-test-steps/overview.md
new file mode 100644
index 00000000..85e8083f
--- /dev/null
+++ b/src/pages/docs/test-cases/create-test-steps/overview.md
@@ -0,0 +1,167 @@
+---
+title: "Create Test Steps in Testsigma"
+metadesc: "This article discusses creating test steps manually using simple English (NLPs) as well as with a recorder for web, mobile web, Android, & iOS app in Testsigma"
+noindex: false
+order: 4.60
+page_id: "Create Test Steps in Testsigma"
+warning: false
+contextual_links:
+- type: section
+ name: "Contents"
+- type: link
+ name: "Prerequisites"
+ url: "#prerequisites"
+- type: link
+ name: "Creating Test Steps Manually"
+ url: "#creating-test-steps-manually"
+- type: link
+ name: "Creating Test Steps Using Test Recorder"
+ url: "#creating-test-steps-using-test-recorder"
+---
+
+---
+
+In Testsigma terminology, each automated action executed by the test script is a test step. For example, in a login form, **Enter <username> in the <username> field** is a test step. This article discusses creating test steps for web, mobile web, Android, and iOS applications using Testsigma recorder & simple English (NLPs).
+
+---
+
+## **Prerequisites**
+
+- You should have Testsigma recorder installed.
+
+- You should know about [test step types](https://testsigma.com/docs/test-cases/step-types/overview/).
+
+- Web/Android/iOS application you want to test.
+
+
+---
+
+## **Creating Test Steps Manually**
+
+### **Web & Mobile Web**
+
+1. Navigate to **Create Tests > Test Cases**, and click on **Create Test Cases**.
+
+
+
+2. Enter **Name** and click on **Add new step**.
+
+
+
+3. Use NLPs to create test steps as per the test case scenario. For example, if you’re creating test steps for the login page, your test steps will be:
+
+ 1. Navigate to https://simply-travel.testsigma.com/
+ 2. Click on **Login/Sign Up**
+ 3. Click on **Login**
+ 4. Enter <**email**> in the <**email address**> field
+ 5. Click on **Continue**
+ 6. Enter <**password**> in the <**password**> field
+ 7. Click on **Submit**
+
+Here's a screenshot of reproduced test steps in Testsigma application.
+
+
+
+### **iOS Apps**
+
+1. Navigate to **Create Tests > Test Cases**, and click on **Create Test Cases**.
+
+
+
+2. Enter **Name** and click on **Add new step**.
+
+
+
+3. Use NLPs to create test steps as per the test case scenario.
+
+### **Android Apps**
+
+1. Navigate to **Create Tests > Test Cases**, and click on **Create Test Cases**.
+
+
+
+2. Enter **Name** and click on **Add new step**.
+
+
+
+3. Use NLPs to create test steps as per the test case scenario.
+
+[[info | **NOTE**:]]
+| - By default the first step for Android and iOS applications is **Launch App**.
+| - You can also add steps above and below a test step by clicking on **Step Above** & **Step Below**.
+| 
+
+
+
+Here's a sample GIF demonstrating creating test steps manually for a Web Application.
+
+
+
+
+---
+
+## **Creating Test Steps Using Test Recorder**
+
+### **Web & Mobile Web**
+
+1. Navigate to **Create Tests > Test Cases**, and click on **Create Test Case**.
+
+
+
+
+2. Create a test step using the URL that you want to automate and click on **Create Step**.
+
+
+
+
+3. Click on **Record**.
+
+
+
+
+4. A new window will open the given URL and you can record the test steps.
+
+
+
+
+[[info | **NOTE**:]]
+| Please wait a few seconds until the web page is fully loaded so the extension can collect information from the page in the background.
+
+5. Once the first web page is fully loaded, start interacting and performing actions on the page.
+
+
+6. The actions will be recorded and added to the test case in the background.
+
+
+7. Once the required actions are complete, click on **Done** to switch back to the test case details page.
+
+
+8. You can see the steps recorded in the test case details page.
+
+
+
+### **Android & iOS Apps**
+
+1. Navigate to **Create Tests > Test Cases**, click on **Create Test Case**.
+
+
+2. On **Test Case Details** page, click on **Record**.
+
+
+3. On **Record test steps** overlay, select **Test Lab**, **Test Machine** and **App Source** you want to test.
+
+
+4. Click on **Record**.
+
+
+5. Perform the actions on the application and once the required actions are complete, stop the recording to switch back to the test case details page.
+
+6. The test case details page will display the steps performed on the application.
+
+
+
+Here's a sample GIF demonstrating creating test steps using the recorder for a Web Application.
+
+
+
+---
\ No newline at end of file
diff --git a/src/pages/docs/test-cases/step-types/overview.md b/src/pages/docs/test-cases/step-types/overview.md
index 9479a7b4..29fc6b93 100644
--- a/src/pages/docs/test-cases/step-types/overview.md
+++ b/src/pages/docs/test-cases/step-types/overview.md
@@ -1,46 +1,68 @@
---
title: "Test Step Types - Overview"
-pagetitle: "Test Step Types in Testsigma"
-metadesc: "What are Test Step types in Testsigma and how to create and use them"
+pagetitle: "Test Step Types"
+metadesc: "There are test step types that logically simulate user interactions on a web/android/iOS screen. This article discusses test step types available in Testsigma"
noindex: false
order: 4.22
page_id: "Test Step Types - Overview"
warning: false
+contextual_links:
+- type: section
+ name: "Contents"
+- type: link
+ name: "Prerequisites"
+ url: "#prerequisites"
+- type: link
+ name: "Steps to Add Test Step Types"
+ url: "#steps-to-add-test-step-types"
---
---
-An automated test case is a step by step logic which simulates user interactions on a web browser / android screen / iOS screen or in the back end as an API. The step-by-step logic is implemented via test steps in Testsigma.
+An automated test case is a step-by-step logic that simulates user interactions on a web browser/android/iOS screen or in the back end as an API. The step-by-step logic is implemented via test steps in Testsigma. This article gives an overview of the different types of test steps that can be created in Testsigma.
-In this document, we will give an overview of the different types of test steps that can be created in Testsigma.
+---
+
+## **Prerequisites**
+
+- You should have Testsigma account.
+
+
+---
-**Navigation**: Select Project > Test Development > Create Test Case > Test Steps page
+## **Steps to Add Test Step Types**
- 1. Go to Test Development
- 2. In Test Cases, create a new test case as shown in the screenshot below
- 3. Once you click on the create button, you will be taken to the test steps page as shown below
- 4. Once you are in the test steps page, click on the icon beside the first test step or any other test step if available to see the different types of test steps as shown below
+1. Navigate to **Create Tests > Test Cases**, and click on **Create Test Cases**.
-
+
- 5. This will open the test steps menu from where you can choose different test steps. Read more about the different test steps and how to create them in the links below:
-
- * [Natural Language](https://testsigma.com/docs/test-cases/step-types/natural-language/)
- * [Step Groups](https://testsigma.com/docs/test-cases/step-types/step-group/)
+2. Enter **Name** and click on **Add new step**.
- * [While Loops](https://testsigma.com/docs/test-cases/step-types/while-loop/)
+
- * [For Loops](https://testsigma.com/docs/test-cases/step-types/for-loop/)
- * [If Conditions](https://testsigma.com/docs/test-cases/step-types/if-condition/)
+3. Click on the option on the left side of the test step.
- * [REST API](https://testsigma.com/docs/test-cases/step-types/rest-api/)
+
-
+4. This will open a side panel from where you can choose different test steps.
+
-
+You can choose the type of test step you want to add to your test case from the panel. Read more about the different test steps and how to create them in the links below:
+- [Natural Language](https://testsigma.com/docs/test-cases/step-types/natural-language/)
+- [REST API](https://testsigma.com/docs/test-cases/step-types/rest-api/)
+- [Step Group](https://testsigma.com/docs/test-cases/step-types/step-group/)
+
+- [For Loop](https://testsigma.com/docs/test-cases/step-types/for-loop/)
+
+- [While Loop](https://testsigma.com/docs/test-cases/step-types/while-loop/)
+
+- [If Condition](https://testsigma.com/docs/test-cases/step-types/if-condition/)
+
+
+---
diff --git a/src/pages/docs/test-data/types/mailbox.md b/src/pages/docs/test-data/types/mailbox.md
index c2e1d94d..bd0c9bce 100644
--- a/src/pages/docs/test-data/types/mailbox.md
+++ b/src/pages/docs/test-data/types/mailbox.md
@@ -44,7 +44,7 @@ Testsigma provides a digital inbox called Mail Box to verify OTP accuracy, check
Before using Mailbox Test Data, ensure that you understand specific concepts such as creating a [Test Case](https://testsigma.com/docs/test-cases/manage/add-edit-delete/#creating-a-test-case), managing [Test Steps](https://testsigma.com/docs/test-cases/step-types/natural-language/), and effectively using them with [Test Data Types](https://testsigma.com/docs/test-data/types/overview/) and [Data Generators](https://testsigma.com/docs/test-data/types/data-generator/). Additionally, familiarise yourself with [Regular expressions](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions) if necessary.
[[info | NOTE:]]
-| You can enable Mail Box for your account by contacting [Testsigma Support](support@testsigma.com) or using the **Instant Chat** option.
+| You can enable Mail Box for your account by contacting **support@testsigma.com** or using the **instant chat** option.
---
diff --git a/src/pages/docs/test-management/test-plans/distributed-testing.md b/src/pages/docs/test-management/test-plans/distributed-testing.md
index 6fc8609a..2da097d2 100644
--- a/src/pages/docs/test-management/test-plans/distributed-testing.md
+++ b/src/pages/docs/test-management/test-plans/distributed-testing.md
@@ -1,51 +1,88 @@
---
-title: "Distributed testing"
+title: "Distributed Testing"
page_title: "Distributed Testing in Testsigma"
metadesc: "Improve your testing efficiency with Testsigma's distributed testing. Learn how to execute tests across multiple machines and increase test coverage quickly."
noindex: false
order: 8.27
-page_id: "Distributed Testing "
+page_id: "Distributed Testing"
warning: false
contextual_links:
- type: section
- name: "Contents"
+ name: "Contents"
- type: link
- name: "Steps to enable distributed testing"
+ name: "Prerequisites"
+ url: "#prerequisites"
+- type: link
+ name: "Steps to Create Distributed Testing"
url: "#steps-to-enable-distributed-testing"
+---
+
---
+
+Distributed testing means that a test scenario is segmented into several parts, and each of them is performed on a separate machine, either sequentially or in parallel. It also suggests that the test parts interact with each other during a test run, which makes them coordinated and synchronized.
+
+This type of testing is generally used to test distributed software — systems with components that run on different machines and interact with each other, such as a client-server system or an internet-based application web or intranet sites, with significant functional units running in multiple locations.
+
+The goal of distributed testing is to know how different components of the system interact with each other. While multiple computers will run simultaneously during the test, each one will be running a different application component and playing a different role.
+
+Distributed testing is achieved in Testsigma by splitting up test plan execution across multiple machines. To do this, Testsigma lets you select different test suites for each selected test machine, where each test suite encompasses one or more components of the application.
+
---
-*Distributed testing* means that a test scenario is segmented into several parts and each of them is performed on a separate machine either sequentially or in parallel. It also suggests that the test parts interact with each other during a test run which make them coordinated and synchronized.
-This type of testing is generally used to test distributed software — systems with
-components which run on different machines, and interact with each other,
-such as a client-server system, or an Internet-based application web or intranet sites, with major
-functional units running in multiple locations.
+## **Prerequisites**
-The goal of distributed testing is to know how different components of the system interact with each other. While multiple computers will be running simultaneously during the test, each
-one will be running a different component of the application, and will be
-playing a different role.
+- You should know [how to create a test suite](https://testsigma.com/docs/test-management/test-suites/overview/#creating-a-test-suite).
-Distributed testing is achieved in Testsigma by splitting up test plan execution across multiple machines. To do this, Testsigma lets you select different test suites for each selected test machine where each test suite encompasses one or more component of the application.
+- You should know [how to create a test plan](https://testsigma.com/docs/test-management/test-plans/overview/#steps-to-create-a-test-plan).
-
+- You should know [how to manage test machines](https://testsigma.com/docs/test-management/test-plans/manage-test-machines/).
+
+---
## **Steps to enable distributed testing**
+1. Navigate to **Test Plans** and click on **Create Test Plan**.
+
+
-1. Navigate to **Test Machines & Suites Selection** under the **Create test plan** form. *If you are not familiar with creating a test plan, refer to [add, edit,delete a test plan](https://testsigma.com/docs/test-management/test-plans/overview/)*.
+2. On the **Create Test Plan** page, select **Custom test plan** from **Test Plan Type**.
-2. Under the **Test machines & suites selection** tab,select the test suite for which you want to add the test machine for test execution. *For more information refer to [adding test suites](https://testsigma.com/docs/test-management/test-plans/manage-test-suites/)*
+
-3. Once you have selected the test suites, select the test machines to run the coressponding test suite. *For more information refer to [add test machines](https://testsigma.com/docs/test-management/test-plans/manage-test-machines/)*.
-[[info | Note:]]
-|To enable distributed testing you have to select different test suites for different test machines.
+3. Click on **Add Test Suites & Link Machine Profiles**.
-See the below GIF to understand the workflow to enable distributed testing:
+
+4. Click on **Add Test Suites**.
+
+
+5. Select test suites and click on **Add to Plan**.
+
+
+
+6. Click on **Test Machine** to add test machines to run the test suite.
+
+
+
+7. On **Select test machine profiles** overlay, select test machines and click on **Save selections**.
+
+
+
+[[info | **NOTE**:]]
+| For distributed testing, you must select different test suites for different test machines. You can hover over the test suite and click on the test machine corresponding to it to add a different test machine to the test suite.
+
+8. Go to **Test Plan Settings** and click on **Create**.
+
+
+
+
+Here’s a quick GIF demonstrating how to create distributed testing in Testsigma.
+
+---
\ No newline at end of file
diff --git a/src/pages/docs/test-management/test-plans/manage-test-machines.md b/src/pages/docs/test-management/test-plans/manage-test-machines.md
index ae81c7bc..021f5d9b 100644
--- a/src/pages/docs/test-management/test-plans/manage-test-machines.md
+++ b/src/pages/docs/test-management/test-plans/manage-test-machines.md
@@ -1,5 +1,5 @@
---
-title: "Manage test machines in test plans"
+title: "Manage Test Machines in Test Plans"
metadesc: "Easily manage test machines in Test Plans, which helps allocate tests to specific machines. Learn how to allot test machines for test plans in Testsigma."
noindex: false
order: 8.22
@@ -9,61 +9,113 @@ contextual_links:
- type: section
name: "Contents"
- type: link
- name: "Add a test machine to an existing test plan"
- url: "#add-a-test-machine-to-an-existing-test-plan"
+ name: "Prerequisites"
+ url: "#prerequisites"
+- type: link
+ name: "Adding a Test Machine to an Existing Test Plan"
+ url: "#adding-a-test-machine-to-an-existing-test-plan"
+- type: link
+ name: "Adding a Test Machine From Edit Test Plan Page"
+ url: "#adding-a-test-machine-from-edit-test-plan-page"
- type: link
name: "Delete test machine"
url: "#delete-test-machine"
---
+
---
-As discussed under the [create test plan section](https://testsigma.com/docs/test-management/test-plans/overview/#steps-to-create-a-test-plan), you must add at least one test machine to a test plan to create a test plan successfully. Test machines can be added for *cross-browser testing* and *distributed testing*.
+While creating a test plan, you must add at least one test machine to a test suite to develop it successfully. This article discusses how to manage test machines in test plans.
-For *cross-browser testing*, test machines and test suites are selected separately. On execution, all the selected test suites are run on all selected test machines (in parallel or sequentially, depending on your selection).
-For *distributed testing*, you can split test suite execution across multiple machines. To do this, Testsigma lets you select different test suites for each selected test machine. This helps reduce execution time too.
+---
+
+## **Prerequisites**
+
+- You should know how to [create a test suite](https://testsigma.com/docs/test-management/test-suites/overview/#creating-a-test-suite).
+
+- You should know how to [create a test plan](https://testsigma.com/docs/test-management/test-plans/overview/#steps-to-create-a-test-plan).
-The following article discusses adding, editing, or deleting test machines from an existing test plan. *For more information on how to add a test machine while creating a test plan, refer to [test plan](https://testsigma.com/docs/test-management/test-plans/overview/)*.
---
-## **Add a test machine to an existing test plan**
+## **Adding a Test Machine to an Existing Test Plan**
+
+1. Navigate to **Test Plans** and click on an existing test plan.
+
+
-1. Navigate to **Select project**> **Test development**>**Test plan**.
-2. Click on an existing test plan.
-3. In the **Test devices and suites** tab. Click **Add new** to add the test machine for test execution.
+2. On the **Test Plan Details** page, click on **Add Machine**.
-4. Add or edit the necessary details on the **Select test machines/ suites** overlay.
-5. Click **Update**.
+
+3. On **Add test machine/device profile** overlay, add **Name** and click on **Add/Remove Test Suites**.
+
-Alternatively, you can add a new test machine by **editing the test plan**. *For more information on editing the test plan, refer to [updating test plan](https://testsigma.com/docs/test-management/test-plans/overview/#edit-test-plan)*.
+4. Select test suites and click on **Add to Plan**.
-.
+
-1. Navigate to the **Edit test plan** page.
-2. Under the **Test machines & suites selection** tab,select the test suite for which you want to add the test machine for test execution.
-
-3. Once you have selected the test suites that you want to add the test machine for, click on the **Add machine** button.
+5. Click on **Create Machine**.
-4. Select either of the two options **Create new machine** or **Add to existing machine** from the drop-down list.
-
+
- 1. If you want to add the selected test suite to an existing machine then click on the option **Add to existing machine**. A layover **Add Test suites to machineor device** appears with a list of the existing machines as shown in the screenshot below:
-
- Select the machine that you want to execute the test suite on. To finalize the change, click on **Next** and **Update**.
- 2. If you want to create a new machine then click on the option **Create new machine**. A layover **Add machine** appears, as shown in the screenshot below:.Provide the necessary details and click **Create**.
-5. To finalize the change, click on **Next**>**Update**.
+6. A New machine will be added to the test plan.
+
+
+
+Alternatively, you can also add new machines from the edit test plan page.
+
+Here’s the GIF demonstrating how to add test machines to an existing test plan.
+
+
---
-## **Delete test machine**
+## **Adding a Test Machine From Edit Test Plan Page**
+
+1. Navigate to **Test Plan** and click on an existing test plan.
+
+
+
+2. On the test plan details page, click on **Edit**.
+
+
+
+3. Go to **Add Test Suites & Link Machine Profiles** and click on **Test Machine**.
+
+
+
+4. From **Select test machine profiles** overlay, select test machines and click on **Save selections**.
+
+
+
+5. Go to **Test Plan Settings** and click on **Update**.
+
+
+
+6. Selected machines will be added to the test plan.
+
+---
+
+## **Delete Test Machine**
+
+1. Navigate to **Test Plan** and click on an existing test plan.
+
+
+
+2. On the test plan details page, click on **Kebab Menu** and click on **Delete**.
+
+
+
+3. On the **Delete Test Machine?** prompt, enter **DELETE** and click on **I understand, delete this Test Machine**.
+
+
-In case you need to delete an already added test machine in a test plan, follow below steps:
+Here’s the GIF demonstrating how to delete test machines in test plan.
-You can delete the test machine through the **Edit test plan** > **Test machine & suites selection** tab.
+
-1. On the **Test machine & suites selection** tab, hover over the test machine you want to delete and click **Delete** on the test machine.
\ No newline at end of file
+---
\ No newline at end of file
diff --git a/src/pages/docs/test-management/test-plans/manage-test-suites.md b/src/pages/docs/test-management/test-plans/manage-test-suites.md
index 87ccf2ce..53fed7ec 100644
--- a/src/pages/docs/test-management/test-plans/manage-test-suites.md
+++ b/src/pages/docs/test-management/test-plans/manage-test-suites.md
@@ -1,5 +1,5 @@
---
-title: "Manage test suites in test plans"
+title: "Manage Test Suites in Test Plans"
metadesc: "Managing test suites in Test Plans makes test execution more efficient. Learn how to add, remove, and organize test suites in test plans in Testsigma."
noindex: false
order: 8.23
@@ -9,68 +9,94 @@ contextual_links:
- type: section
name: "Contents"
- type: link
- name: "Add or Edit a Test Suite via the Edit Test Plan Page"
- url: "#add-or-edit-a-test-suite-via-the-edit-test-plan-page"
+ name: "Prerequisites"
+ url: "#prerequisites"
- type: link
- name: "Delete a test suite via the edit test plan page"
- url: "#delete-a-test-suite-via-the-edit-test-plan-page"
+ name: "Editing Test Suites in a Test Plan"
+ url: "#editing-test-suites-in-a-test-plan"
- type: link
- name: "Add or edit a test suite via the test plan details specific tab"
- url: "#add-or-edit-a-test-suite-via-the-test-plan-details-specific-tab"
+ name: "Manage Test Suites from Test Plan Details Page"
+ url: "#manage-test-suites-from-test-plan-details-page"
---
---
-As discussed under the [create test plan](https://testsigma.com/docs/test-management/test-plans/overview/) section, at least one *test suite* must be added to a test plan to develop it successfully.
+While creating a test plan, you need to add at least one test suite to the test plan to develop it successfully. This article discusses how to manage test suites in test plans.
-Here, we will discuss how to add, edit, or delete test suites in an existing test plan.
-
-There are two ways to add or edit a test suite in a test plan:
+---
-1. Via the **Edit test plan** page
+## **Prerequisites**
-2. Via the **Test plan details specific** tab
+- You need to know [how to create a test plan](https://testsigma.com/docs/test-management/test-plans/overview/#steps-to-create-a-test-plan).
---
-## **Add or edit a test suite via the edit test plan page**
+## **Editing Test Suites in a Test Plan**
-1. Navigate to **Select project** > **Test development** > **Test plan**.
-2. Click on an existing test plan. 
-3. Click **Edit** on the top right corner of the test plan page.
-4. On the **Edit test plan** page, go to the **Test machines & suites selection** tab.
-5. Under the **Test machines & suites selection** tab - click **Add test suites**.
-[[info | NOTE:]]
-| You should Associate Test Machine with Test Suites to create Test Plan
+1. Navigate to **Test Plans**, create a test plan or click on any existing test plan.
-6. The **Selected Test Suites** window will appear.
-Under the **Filters** section, you can filter the test suites by name. You can enable end-to-end testing if you want to execute test suites across multiple platforms. You can add more test cases by clicking on the **+** icon, and you can remove test cases by clicking on the **-** icon.
-7. Once the **Selected Test Suites** section contains the needed test suites, click **Add**.
+
+
+
+2. Click on **Edit**.
+
+
----
-## **Delete a test suite via the edit test plan page**
+3. On the **Edit Test Plan** page, there are 3 sections.
+ - **Basic Details**: You edit test plan Name, Labels and Test Plan Type on this section.
+ 
-1. Go to the Edit Test Plan page, click **Test machines & suites** tab section.
-2. Under the **Test machines & suites selection** tab, hover over the test suite you want to delete.
-3. Click **delete** corresponding to the test suite you want to delete, this will remove the entry from the **Test suites** section.
-4. Click on **Next** and then **Update** to finalise the changes.
+ - **Add Test Suites & Link Machine Profiles**: You can add/remove test suites and test machines on this section.
+ 
+
+ - **Test Plan Settings**: You can edit **Additional Settings** on this section.
+ 
+
+
+Here’s the GIF demonstrating how to manage test suites in test plans.
+
+
+
+Alternatively, you can also add/remove test suites directly from the test plan details page.
---
-## **Add or edit a test suite via the test plan details specific tab**
+## **Manage Test Suites from Test Plan Details Page**
+
+1. Navigate to Test Plans and click on any existing test plan.
+
+
+
+2. On the test plan details page, hover over the test machine for which you want to add/remove test suites, click on **Kebab Menu**, and click on **Edit**.
+
+
+
+
+3. On the **Edit test machine/device profile** overlay, click on **Add/Remove Test Suites**.
+
+
+
+4. An overlay of **Add test suites to plan** opens.
+
+
+
+5. To add a test suite, click on the ‘**+**’ button of the test suite of your choice from **Available Test Suites**.
+
+
+
+
+6. To remove a test suite, click on the ‘**-**’ button of the test suite of your choice from **Selected for Test Plan**.
-1. Navigate to **Select Project** > **Test Development** > **Test Plan**.
+
-2. Click on an existing test plan.
-3. Click **Edit** on the top right corner of the test plan page.
-4. The test plan details page should look something like this:
+7. Once the Test Suites are added/removed from the test plan, click on **Update Machine** from **Edit test machine/device profile** overlay.
-5. Go to the tab **Test machines & suites** on the test plan details page. A list of test suites will appear. You can **Edit** or **Delete** the test suites by hovering your mouse over the test suite. Click **Add New** to add test suites.
+
-6. **Select Test Machines** & **Selected Test Suites** overlay appear in the screen. Give the required details and click **Add Test Suties**. 
+Here’s the GIF demonstrating how to manage test suites in test plans from test plan details page.
-7. The **Selected Test Suites** pop-up screen appears, and you can add or remove test suites as needed, and then click **Add** at the bottom right. Click **Create** to add new test suites.
+
---
\ No newline at end of file
diff --git a/src/pages/docs/troubleshooting/mobile-apps/test-execution-queued-for-a-long-time.md b/src/pages/docs/troubleshooting/mobile-apps/test-execution-queued-for-a-long-time.md
index 54d9eeae..468dd332 100644
--- a/src/pages/docs/troubleshooting/mobile-apps/test-execution-queued-for-a-long-time.md
+++ b/src/pages/docs/troubleshooting/mobile-apps/test-execution-queued-for-a-long-time.md
@@ -1,29 +1,53 @@
---
-title: "Test execution state is Queued for a long time"
-metadesc: "Understand why your test execution state may be stuck in Queued state for an extended period | Know the possible reasons and solutions to resolve the issue"
+title: "Test Execution State is Queued for a Long Time"
+metadesc: "Understand why your test execution state may be stuck in Queued state for an extended period | Know the possible reasons why your test execution is Queued"
noindex: false
order: 23.6
page_id: "Troubleshooting “Test execution state is Queued for a long time” error"
warning: false
+contextual_links:
+- type: section
+ name: "Contents"
+- type: link
+ name: "Steps to Troubleshoot the Issue"
+ url: "#steps-to-troubleshoot-the-issue"
---
+---
+
+
+If the execution status for your tests has been in the state **Queued** for a long time then, one of the possible reasons is that the number of total parallel runs allowed on your license are already in use.
+
+
+---
+
+## **Steps to Troubleshoot the Issue**
+
+1. On **Dashboard**, click on **Usage details**.
+
+
+
+2. Check the number of **Parallel Tests**.
+
+
+
+
+Here, we have a license for 3 parallel executions & 3 allowed queues. We can set up a maximum of 3 test runs to run in parallel, which means executing up to 3 tests simultaneously. In addition to the 3 tests running in parallel, you can have up to 3 tests in the queue. The queued tests will execute once the ongoing parallel executions are complete.
+
+In the above example, we have **Parallel Tests 2/3**, which means 2 tests are running in parallel, and 3 is the number of parallel runs allowed at a moment.
+3. Suppose the number of parallel runs is equal to the number of parallel licenses for your Testsigma account. In that case, the tests in the queue will remain in the same status until the parallel test runs are completed.
-If the execution status for your tests has been in the state "Queued" for a long time then, one of the possible reasons is that the number of total parallel runs allowed on your license are already in use. To check if this is the issue, follow below steps:
-1. Click on the "Usage Details" button on the Left Navigation Menu, as also highlighted in the screenshot below:
-
+**You can take the following actions to fix the issue:**
-2. Check the number of Parallel Tests.
+- You can wait for other tests to complete execution.
-
+- You can connect with Testsigma support (**support@testsigma.com**) to increase the number of parallel runs allowed on your license.
-In this screenshot, 3/5 means - 3 tests are running in parallel and 5 is the number of parallel runs allowed at a moment.
+
-3. If the number of parallel runs is equal to the number of parallel licenses for your Testsigma account then you can take following actions to fix the issue:
- i. You can wait for other tests to complete execution.
- ii. You can talk to Testsigma support to increase the number of parallel runs allowed on your license.
- iii. You can click on the name of the test displayed in the Usage Details window and check its details. This can only be done if you have access to the test case.
- 
+Here’s the GIF demonstrating how to check the usage details in Testsigma.
+
- iv. If you have appropriate rights, you can also stop the execution of one of the test cases by clicking on the corresponding stop button.
\ No newline at end of file
+---
\ No newline at end of file
diff --git a/src/templates/page.scss b/src/templates/page.scss
index 8032ee5a..b8c6d0c0 100644
--- a/src/templates/page.scss
+++ b/src/templates/page.scss
@@ -662,14 +662,16 @@ table{
// Cookie banner
#hs-banner-parent{
.hs-cookie-notification-position-bottom{
- width: calc(min(28em, 100%));
- left: 14%;
+ width: calc(min(28em, 100%)) !important;
+ left: calc(min(15em, 100%)) !important;
@media only screen and (max-width: 767px) {
left: 3%;
+ bottom: 2%;
width: 95%;
}
@media only screen and (min-width:768px) and (max-width: 1023px) {
left: 20%;
+ bottom: 10%;
width: 35%;
}
#hs-eu-cookie-confirmation-inner{
@@ -685,4 +687,51 @@ table{
}
}
}
-}
\ No newline at end of file
+}
+
+//Black-friday hello bar design
+#leadinModal-4801049{
+ .leadinModal-content {
+ background: linear-gradient(
+ 92deg,
+ #4dd795 37.61%,
+ rgba(96, 217, 188, 0.83) 76.64%
+ ) !important;
+ .leadinModal-content-wrapper {
+ .leadin-content-body {
+ .leadin-preview-wrapper {
+ h4 {
+ @apply font-bold;
+ font-size: 1.6rem;
+ line-height: normal;
+ color: #000000 !important;
+ margin: 0 auto;
+ margin-left: auto !important;
+ margin-right: auto;
+ text-align: center !important;
+ font-style: normal;
+ }
+ .advance-wrapper {
+ @media (max-width: 767px) {
+ @apply mt-8;
+ }
+ .leadin-button {
+ @apply font-bold text-center;
+ font-size: 1.4rem;
+ color: #fff !important;
+ border-radius: 3px;
+ background-color: #191919 !important;
+ font-style: normal;
+ height: 2.7rem;
+ }
+ }
+ }
+ }
+ }
+ .leadinModal-close{
+ &::before{
+ color: #000000 !important;
+ }
+ }
+ }
+}