Merge branch 'dev' into react-ui-set-5-7

.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:

.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

.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

src/left-nav-title.json

@@ -206,7 +206,7 @@
     "/docs/test-data/create-data-profiles/": "Create Test Data [Parameter]"
   },
   "import-data-profiles": {
-    "/docs/test-data/import-data-profiles/": "Import Test Data [Parameter]"
+    "/docs/test-data/import-data-profiles/": "Import TDP"
   },
   "create-environment-data": {
     "/docs/test-data/create-environment-data/": "Create Test Data [Environment]"
@@ -215,31 +215,31 @@
     "/docs/test-data/data-generators/overview/": "Test Data Generators"
   },
   "elements": {
-    "/docs/elements/": "Elements(Objects)",
+    "/docs/elements/": "Elements (Objects)",
     "/docs/api/elements/": "Elements"
   },
   "record-multiple-elements": {
-    "/docs/elements/web-apps/record-multiple-elements/": "Record Multiple Elements[Recorder]",
-    "/docs/elements/android-apps/record-multiple-elements/": "Record Multiple Elements[Recorder]",
-    "/docs/elements/ios-apps/record-multiple-elements/": "Record Multiple Elements[Recorder]"
+    "/docs/elements/web-apps/record-multiple-elements/": "Record Multiple Elements",
+    "/docs/elements/android-apps/record-multiple-elements/": "Record Multiple Elements",
+    "/docs/elements/ios-apps/record-multiple-elements/": "Record Multiple Elements"
   },
   "capture-single-element": {
-    "/docs/elements/web-apps/capture-single-element/": "Capture Single Element[Recorder]",
-    "/docs/elements/android-apps/capture-single-element/": "Capture Single Element[Recorder]",
-    "/docs/elements/ios-apps/capture-single-element/": "Capture Single Element[Recorder]"
+    "/docs/elements/web-apps/capture-single-element/": "Record Single Element",
+    "/docs/elements/android-apps/capture-single-element/": "Record Single Element",
+    "/docs/elements/ios-apps/capture-single-element/": "Record Single Element"
   },
   "create-manually": {
-    "/docs/elements/web-apps/create-manually/": "Create Elements [Manually]",
-    "/docs/elements/android-apps/create-manually/": "Create Elements [Manually]",
-    "/docs/elements/ios-apps/create-manually/": "Create Elements [Manually]"
+    "/docs/elements/web-apps/create-manually/": "Create Elements",
+    "/docs/elements/android-apps/create-manually/": "Creating Elements Manually",
+    "/docs/elements/ios-apps/create-manually/": "Create Elements"
   },
   "supported-locator-types": {
     "/docs/elements/web-apps/supported-locator-types/": "Supported Locator Types",
     "/docs/elements/android-apps/supported-locator-types/": "Supported Locator Types",
     "/docs/elements/ios-apps/supported-locator-types/": "Supported Locator Types"
   },
   "creating-locators-manually-strategies": {
-    "/docs/elements/web-apps/creating-locators-manually-strategies/": "Different Strategies for Formulating Elements",
+    "/docs/elements/web-apps/creating-locators-manually-strategies/": "Formulating Elements",
     "/docs/elements/android-apps/creating-locators-manually-strategies/": "Different Strategies for Formulating Elements",
     "/docs/elements/ios-apps/creating-locators-manually-strategies/": "Different Strategies for Formulating Elements"
   },
@@ -583,5 +583,23 @@
   },
   "multiple-webviews":{
     "/docs/test-cases/create-test-steps/actions-and-options-recorder/multiple-webviews/": "Tests for Multiple WebViews"
+  },
+  "faqs":{
+    "/docs/getting-started/faqs/": "FAQs"
+  },
+  "manage-execution-stops":{
+    "/docs/collaboration/manage-execution-stops/": "Execution Controls"
+  },
+  "add-values-to-test-data-profile":{
+    "/docs/test-data/add-values-to-test-data-profile/": "Updating Value in TDP"
+  },
+  "ios-apps":{
+    "/docs/elements/ios-apps/overview/": "iOS Apps"
+  },
+  "after-test":{
+    "/docs/test-management/test-plans/after-test/": "AfterTest Case"
+  },
+  "partial-test-plan-run-via-api":{
+    "/docs/test-management/test-plans/partial-test-plan-run-via-api/": "Execute Partial Test Plans via API"
   }
-}
+}

src/pages/docs/addons/ocr-extraction.md

@@ -64,5 +64,3 @@ Before creating the OCR Text Extraction addon, ensure you have met the prerequis
 Once the addon is published, NLPs become available in the application. Follow these GIF below to use the OCR addon in Test Cases: ![Addon GIF](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/ocr_text_extraction_addon.gif)
 
 ---
-
-

src/pages/docs/agent/overview.md

@@ -5,18 +5,32 @@ noindex: false
 order: 11.1
 page_id: "Testsigma Agent - Overview"
 warning: false
+contextual_links:
+- type: section
+  name: "Contents"
+- type: link
+  name: "Important Items on Testsigma Agent"
+  url: "#important-items-on-testsigma-agent"
 ---
 
 ---
 
-Testsigma allows you to run tests on your local machines/devices in addition to Testsigma Cloud machines/devices. For running the tests locally, you need a small Testsigma Agent (Java) utility running on the machine for test orchestration, i.e., queueing tests, running the tests, fetching the test results, etc.
+Testsigma allows you to run tests on your local machines/devices and Testsigma Cloud machines/devices. For running the tests locally, you need a small Testsigma Agent (Java) utility running on the machine for test orchestration, i.e., queueing tests, running the tests, fetching the test results, etc.
 
-Here are some frequently asked questions regarding Testsigma Agent - [Testsigma Agent FAQ](https://testsigma.com/docs/agent/faqs/)
+---
+## **Important Items on Testsigma Agent**
+- Here are some frequently asked questions regarding Testsigma Agent - [Testsigma Agent FAQ](https://testsigma.com/docs/agent/faqs/)
+
+
+- To know the reasons why Testsigma Agent is required for Local Test Plan/Ad-hoc Runs in Testsigma, refer to - [Why do we need Testsigma Agent?](https://testsigma.com/docs/agent/faqs/)
+
+- Here are the [Minimum system requirements for Testsigma Agent](https://testsigma.com/docs/agent/pre-requisite/)
+
+- Your security team might have some questions regarding the working of Testsigma Agent and how the data communication works. Here’s a brief explanation on that - [How does Testsigma Agent work](https://testsigma.com/docs/agent/faqs/)
+
+- If you face any issues during the installation, starting or registering the Testsigma Agent, please check the troubleshooting guide: [Agent - Startup and Registration Errors](https://testsigma.com/docs/agent/troubleshooting/setup-issues/)
 
-To know the reasons why Testsigma Agent is required for Local Test Plan/Ad-hoc Runs in Testsigma, refer to - [Why do we need Testsigma Agent?](https://testsigma.com/docs/agent/faqs/)
 
-Here are the [Minimum system requirements for Testsigma Agent](https://testsigma.com/docs/agent/pre-requisite/)
 
-Your security team might have some questions regarding the working of Testsigma Agent and how the data communication works. Here’s a brief explanation on that - [How does Testsigma Agent work](https://testsigma.com/docs/agent/faqs/)
 
-If you face any issues during the installation, starting or registering the Testsigma Agent, please check the troubleshooting guide: [Agent - Startup and Registration Errors](https://testsigma.com/docs/agent/troubleshooting/setup-issues/)
+---

src/pages/docs/agent/pre-requisite.md

@@ -1,5 +1,5 @@
 ---
-title: " Pre-requisites for Testsigma Agent"
+title: " Prerequisites for Testsigma Agent"
 metadesc: "The pre-requisites or conditions that should be met before you can successfully install and execute Testsigma agent on your devices."
 noindex: false
 order: 11.2
@@ -9,19 +9,23 @@ contextual_links:
 - type: section
   name: "Contents"
 - type: link
-  name: "Hardware Requirements:"
+  name: "Hardware Requirements"
   url: "#hardware-requirements"
 ---
 
 ---
 
 Verify that the workstation where you install the Testsigma Agent satisfies the minimum hardware requirements specified below.
 
-<br>
-
 ---
+
 ## **Hardware Requirements** 
 
-   **Memory:** Minimum 8 GB (dedicated memory for the tests).<br>
-   **Disk space:** Around 20 GB (including reserved space for test resources such as screenshots, downloaded files etc.).<br>
-   **Processor:** Dual-Core Processor or higher.
+- **Memory:** Minimum 8 GB (dedicated memory for the tests).
+
+- **Disk space:** Around 20 GB (including reserved space for test resources such as screenshots, downloaded files etc.).
+
+- **Processor:** Dual-Core Processor or higher.
+
+
+---

src/pages/docs/api/examples/trigger-multiple-test-plans.md

@@ -22,9 +22,10 @@ contextual_links:
 
 ---
 
-This article explains how to trigger multiple Test Plans consecutively. You might need this to run a Mobile Test Plan after executing a Web Test Plan.
+This article explains how to trigger multiple test plans consecutively. You might need this to run a mobile test plan after executing a web test plan.
 
 ---
+
 ## **Sample Test Scenario**
 
 Let’s create a User using the Admin HR portal that is accessible only via a Desktop Browser and then manage that user on the Mobile HR App.
@@ -55,14 +56,16 @@ For example, if there’s a username that you would pass from Admin-TP to Mobile
 
 Here’s a sample Request Body for passing runtime parameters:
 
+```
 {
+  "executionid": "274",
+  "runtimeData": {
+    "data": "$|admin_username|"
+  }
+}
+```
 
-&emsp;&emsp;&emsp;&emsp;"runtimeData" :  {<br>&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;"data":"$|admin_username|"
-<br>&emsp;&emsp;&emsp;&emsp;}<br>}
-
-Here’s a snapshot of the REST API Step in TCTrigger used to trigger the Mobile-TP Test Plan:
 
-![Testsigma REST API Step to trigger new Test Plan](https://docs.testsigma.com/images/trigger-multiple-test-plans/trigger-multiple-test-plans-testsigma-rest-api-step.png)
 
 Once the Test Plan Mobile-TP is triggered by the REST API Step in TCTrigger, the runtime parameter ‘admin\_username’ is also passed to that Test Plan. You can use those parameters in any Test Case within Mobile-TP now.