From 2262b0004aa4b8832507e1cb3d63a7ff10951fc2 Mon Sep 17 00:00:00 2001
From: Bharath Krishna <118433150+bharathk08@users.noreply.github.com>
Date: Mon, 25 Mar 2024 15:38:24 +0530
Subject: [PATCH] Removing duplicates from docs site (#380)
---
.../deleting-users-from-a-project.md | 61 -------
.../docs/configuration/reset-password.md | 90 ----------
src/pages/docs/configuration/storage-types.md | 83 ---------
.../creating-locators-manually-strategies.md | 19 --
.../android-apps/supported-locator-types.md | 30 ----
.../creating-locators-manually-strategies.md | 19 --
.../ios-apps/supported-locator-types.md | 31 ----
.../getting-started/introduction-community.md | 55 ------
.../docs/getting-started/setup/docker.md | 169 ------------------
.../testsigma-community-cloud.md | 37 ----
src/pages/docs/reports/runs/rerun.md | 45 -----
.../docs/reports/runs/test-case-reports.md | 50 ------
.../docs/reports/runs/test-machine-reports.md | 66 -------
.../docs/reports/runs/test-suite-reports.md | 53 ------
.../test-cases/step-types/create-steps.md | 82 ---------
15 files changed, 890 deletions(-)
delete mode 100644 src/pages/docs/collaboration/deleting-users-from-a-project.md
delete mode 100644 src/pages/docs/configuration/reset-password.md
delete mode 100644 src/pages/docs/configuration/storage-types.md
delete mode 100644 src/pages/docs/elements/android-apps/creating-locators-manually-strategies.md
delete mode 100644 src/pages/docs/elements/android-apps/supported-locator-types.md
delete mode 100644 src/pages/docs/elements/ios-apps/creating-locators-manually-strategies.md
delete mode 100644 src/pages/docs/elements/ios-apps/supported-locator-types.md
delete mode 100644 src/pages/docs/getting-started/introduction-community.md
delete mode 100644 src/pages/docs/getting-started/setup/docker.md
delete mode 100644 src/pages/docs/getting-started/testsigma-community-cloud.md
delete mode 100644 src/pages/docs/reports/runs/rerun.md
delete mode 100644 src/pages/docs/reports/runs/test-case-reports.md
delete mode 100644 src/pages/docs/reports/runs/test-machine-reports.md
delete mode 100644 src/pages/docs/reports/runs/test-suite-reports.md
delete mode 100644 src/pages/docs/test-cases/step-types/create-steps.md
diff --git a/src/pages/docs/collaboration/deleting-users-from-a-project.md b/src/pages/docs/collaboration/deleting-users-from-a-project.md
deleted file mode 100644
index 1af6ec46..00000000
--- a/src/pages/docs/collaboration/deleting-users-from-a-project.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: "Delete Users from Project"
-page_title: "Delete Users from Project"
-metadesc: "A guide to managing Projects within Testsigma, including editing, deleting projects, and enabling/disabling multiple Application/Versions"
-noindex: false
-order: 3.5
-page_id: "Manage Projects"
-warning: false
-contextual_links:
-- type: section
- name: "Contents"
-- type: link
- name: "Delete user via Project settings"
- url: "#delete-user-via-project-settings"
-- type: link
- name: "Delete user via Settings"
- url: "#delete-user-via-settings"
----
-
----
-In Testsigma, you can delete users from your project. This article will discuss how to delete users from your project.
-
-*For more information on user management, refer to [users & role Management](https://testsigma.com/docs/collaboration/users-roles/).*
-
-[[info | NOTE:]]
-| You can only delete users if you're the super administrator of the project.
-
----
-
-##**Delete user via Project settings**
-
-1. Go to **Project Settings** and select the project from which you want to delete users.
-
-
-2. Click on **Project members** to see users associated with that project.
-
-
-3. Hover your mouse over the users and click on **Delete** to delete the user from the project.
-
-
-4. On the pop-up window, click on **Yes, Delete** to confirm the deletion.
-
-5. The user will be successfully removed from the project.
-
----
-
-## **Delete user via Settings**
-
-1. Navigate to **Settings** > **Users**.
-
-
-2. Hover over the user you want to delete.
-3. Click on three dots, and click **Delete**.
-
-
-4. On the pop-up window, click on **Yes, Delete** to confirm the deletion.
-
-
-5. The user will be successfully removed from the project.
-
----
\ No newline at end of file
diff --git a/src/pages/docs/configuration/reset-password.md b/src/pages/docs/configuration/reset-password.md
deleted file mode 100644
index 36a135f9..00000000
--- a/src/pages/docs/configuration/reset-password.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: "Reset Password"
-page_title: "How to reset password in Testsigma Community Edition"
-order: 19.3
-page_id: "Reset password"
-metadesc: "Learn steps in detail on how to reset username and password in Testsigma Community Edition. Follow these steps to reset username and password."
-search_keyword: "Reset password"
-warning: false
-contextual_links:
-- type: section
- name: "Contents"
-- type: link
- name: "Prerequisite (zip)"
- url: "#zip-prerequisite"
-- type: link
- name: "Reset password (zip)"
- url: "#zip-reset-passwrod"
-- type: link
- name: "Reset User Name (zip)"
- url: "#zip-reset-user-name"
-- type: link
- name: "Prerequisite (Docker)"
- url: "#docker-prerequisite"
-- type: link
- name: "Reset password (Docker)"
- url: "#docker-reset-passwrod"
-- type: link
- name: "Reset User Name (Docker)"
- url: "#docker-reset-user-name"
----
-
----
-## [(I). Via Downloadable package](#)
-
----
-## [Prerequisite](#zip-prerequisite)
- 1. Download the testsigma_opensource latest build [click here](https://testsigma.com/docs/getting-started/setup/downloadable-package/)
- 2. Run nginx server
- 3. Run testsigma server
- 4. Register with username and password
-
----
-## [If you want to reset the password follow the steps below:](#zip-reset-passwrod)
-
- 1. Stop all the servers currently running.(i.e, nginx and testsigma server)
- 2. Navigate to testsigma server folder from downloads
- 3. Go to authentication properties
- 4. And Change the password (authentication.form.password = type your new password)
- 5. Save the file
- 6. Start the nginx
- 7. Testsigma servers and login with new credentials.
-
----
-## [If you want to reset the username :](#zip-reset-user-name)
-
- 1. Stop all the servers currently running.(i.e, nginx and testsigma server)
- 2. Navigate to testsigma server folder from downloads
- 3. Go to authentication properties
- 4. change the username (authentication.form.username = enter new user name)
- 5. save the file
-
-
-
-
-## [(II). Downloaded Via Docker](#)
-
----
-## [Prerequisite](#docker-prerequisite)
- 1. Download the docker [click here](https://testsigma.com/docs/getting-started/setup/docker/)
- 2. Register with username and password
-
----
-## [If you want to reset the password follow the steps below:](#docker-reset-passwrod)
- 1. Go to docker the folder
- 2. Go to the ts-data folder
- 3. Edit the Authentication properties file
- 4. Change the password (authentication.form.password = type your new password)
- 5. Save the file
-
----
-## [If you want to reset the username :](#zip-reset-user-name)
-
- 1. Go to docker the folder
- 2. Go to the ts-data folder
- 3. Edit the Authentication properties file
- 4. change the username (authentication.form.username = enter new user name)
- 5. Save the file
-
-
-
diff --git a/src/pages/docs/configuration/storage-types.md b/src/pages/docs/configuration/storage-types.md
deleted file mode 100644
index 9ba98904..00000000
--- a/src/pages/docs/configuration/storage-types.md
+++ /dev/null
@@ -1,83 +0,0 @@
----
-title: "Storage Types Supported in Testsigma"
-page_title: "How to configuration Storage Types in Testsigma Community Edition"
-order: 19.4
-page_id: "Storage Types Supported in Testsigma"
-metadesc: "Storage allows you to store files on your integrated cloud storage provider. How to configuration Storage Types in Testsigma Community Edition"
-search_keyword: "Storage Types"
-warning: false
-contextual_links:
-- type: section
- name: "Contents"
-- type: link
- name: "Why is storage required?"
- url: "#why-storage"
-- type: link
- name: "Types of storage allowed in Testsigma open source"
- url: "#storage-types"
----
-
----
-## [Why is storage required?](#why-storage)
-
-Storage allows you to access and store files on your preferred already integrated cloud storage provider. You can access files from Testsigma when needed and also push execution details to your cloud storage for downstream use.
-
----
-## [Prerequisite](#prerequisite)
-1. login with valid credentials
-2. goto settings >> storage
-
-
-
----
-## [Types of storage allowed in Testsigma open source](#storage-types)
-
-1. [On premise](#on-premise)
-2. [Testsigma cloud](#testsigma-cloud)
-3. [Amazon s3](#amazon-s3)
-4. [Azure Cloud](#azure-cloud)
-
----
-## [On premise:](#on-premise)
-
-This is your local server storage to store datasets like logs,files and screenshots. When you click on view details, Testsigma will show the local directory where all files are stored.
-
-
-
-## [Testsigma cloud:](#testsigma-cloud)
-
-This is Testsigma own hosted cloud storage. You can push and access files from the Testsigma cloud just like your local storage or any other cloud provider.
-
----
-## [Amazon s3](#amazon-s3)
-If you already have a subscription for AWS S3 storage, you can use the same storage with Testsigma. Testsigma can access these files during execution and also push screenshots or logs to S3 for your team
-
-
-
-- Bucket Name: Name of your S3 bucket in one of the AWS Regions.
-- Endpoint: It is the address/url of the server where you want to store
-- Region: Region your bucket is set up in, you can mention the region code of the bucket configured in AWS.
-- Access key: It's a common access key used to get connected to their respective bucket.
-- Secret key: This is double authentication verification key. It’s the unique key that need to connect to their respective bucket.
-
-
-
-
----
-## [Azure cloud:](#azure-cloud)
-
-If you already have an Azure cloud account, you can use the subscription with Testsigma to store and access files. Testsigma can access files stored here and push execution files like logs and screenshots here for storage.
-
-
-
-- Container Name: Container name which is created/present in Azure storage account.
-- Connection String: A connection string includes the authorization information required for your application to access data in an Azure Storage account.
-
-
-
-
-
-
-
-
-
diff --git a/src/pages/docs/elements/android-apps/creating-locators-manually-strategies.md b/src/pages/docs/elements/android-apps/creating-locators-manually-strategies.md
deleted file mode 100644
index b2dce019..00000000
--- a/src/pages/docs/elements/android-apps/creating-locators-manually-strategies.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: "Different ways to create Elements in an Android Project"
-metadesc: "Elements refer to the different objects in your android application. Learn about various ways to create elements for an android project in Testsigma."
-noindex: false
-order: 6.36
-page_id: "Different ways to create Elements in an Android Project"
-warning: false
----
-
----
-
-Elements here refer to the different objects in your android application that form the UI of the application. There are two ways you can create them in Testsigma:
-
-1. **Manual Creation:** Here, you manually give the details of the element to create them. See [creating elements manually](https://testsigma.com/docs/elements/android-apps/create-manually/).
-2. **Via mobile test recorder:** Here, you access your application’s UI via the mobile test recorder and inspect the elements that you want to capture. See [capturing elements via the mobile test recorder](https://testsigma.com/docs/elements/android-apps/capture-single-element/).
-
-
-
----
\ No newline at end of file
diff --git a/src/pages/docs/elements/android-apps/supported-locator-types.md b/src/pages/docs/elements/android-apps/supported-locator-types.md
deleted file mode 100644
index a3c78ecc..00000000
--- a/src/pages/docs/elements/android-apps/supported-locator-types.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: "Supported Locator Types in an Android Project"
-metadesc: "Supported locator types for creating elements for an android application in Testsigma. Learn five ways to uniquely identify or locate elements in your automated tests."
-noindex: false
-order: 6.35
-page_id: "Supported Locator Types in an Android Project"
-warning: false
----
-
----
-
-When creating elements for an application, you need to provide a way to identify them uniquely. Testsigma supports five ways to identify or locate these elements for your automated tests uniquely. The five supported locator types are:
-
-1. **Accessibility ID:** This is the most preferred locator to use to automate your tests, as this attribute would remain the same for other platforms like iOS, too, and makes it easier to port the same tests to different platforms. This attribute is also least likely to be changed during a structural change in the source.
-
-2. **ID:** After accessibility ID, this is the second preferred locator. Every element is supposed to have a unique ID.
-
-[[info | NOTE:]]
-| If you are facing difficulty finding IDs for your elements, you should talk to your developer about it.
-
-3. **XPATH:** XPath stands for XML Path Language and will parse the source code to get the value of the referred element.
-
-4. **Class Name:** This will be the value assigned to the attribute **Class Name** for the element you want to capture.
-
-5. **Name:** This will be the value assigned to the attribute **Name** for the element you want to capture.
-
-6. **Resource ID:** This will be the value assigned to the attribute **Resource ID** for the element you want to capture. Resource ID allows alphanumeric values along with special characters like dot(.), underscore(_), colon(:), and forward-slash(/).
-
-
----
diff --git a/src/pages/docs/elements/ios-apps/creating-locators-manually-strategies.md b/src/pages/docs/elements/ios-apps/creating-locators-manually-strategies.md
deleted file mode 100644
index d9d9c32c..00000000
--- a/src/pages/docs/elements/ios-apps/creating-locators-manually-strategies.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: " Different ways to create Elements in an iOS Project"
-metadesc: "Elements refer to the different objects in your iOS application. Leaen two ways to create/locate Elements in Testsigma Application."
-noindex: false
-order: 6.46
-page_id: "Different ways to create Elements in an iOS Project"
-warning: false
----
-
----
-
-Elements here refer to the different objects in your iOS application that form the UI of the application. There are two ways you can create them in Testsigma:
-
-1. **Manual Creation:** Here, you manually give the details of the element to create them. See [creating elements manually](https://testsigma.com/docs/elements/ios-apps/create-manually/).
-2. **Via Test recorder:** Here, you access your application’s UI via the Test recorder and inspect the elements that you want to capture. See [capturing elements via the Test recorder](https://testsigma.com/docs/elements/ios-apps/capture-single-element/).
-
-
-
-
diff --git a/src/pages/docs/elements/ios-apps/supported-locator-types.md b/src/pages/docs/elements/ios-apps/supported-locator-types.md
deleted file mode 100644
index 5e031778..00000000
--- a/src/pages/docs/elements/ios-apps/supported-locator-types.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: "Supported Locator Types in an iOS Project"
-metadesc: "Supported locator types for creating elements for an iOS application in Testsigma. Learn five ways to uniquely identify or locate elements in your automated tests."
-noindex: false
-order: 6.45
-page_id: "Supported Locator Types in an iOS Project"
-warning: false
----
-
----
-
-When creating elements for an application, you need to provide a way to uniquely identify them. Testsigma supports five ways to uniquely identify or locate these elements for your automated tests. The five supported locator types are:
-
-1. **Accessibility ID:** This is the most preferred locator to use to automate your tests, as this is an attribute that would remain the same for other platforms like iOS too, and makes it easier to port the same tests to different platforms. This attribute is also least likely to be changed during a structural change in the source.
-2. **ID:** After accessibility ID, this is the second preferred locator to use. Every element is supposed to have a unique ID.
-[[info | NOTE:]]
-| If you are facing difficulty finding IDs for your elements, you should talk to your developer about it.
-3. **XPATH:** XPath stands for XML Path Language, and will parse the source code to get the value of the referred element.
-4. **Class Name:** This will be the value assigned to the attribute ‘Class Name’ for the element you want to capture.
-5. **Name:** This will be the value assigned to the attribute ‘Name’ for the element you want to capture.
-6. **iOS Chain:** A hybrid between XPath and predicate strings
-7. **Predicate String:** For basic comparisons and matching.
-8. **Resource ID:** This will be the value assigned to the attribute **Resource ID** for the element you want to capture. Resource ID allows alphanumeric values along with special characters like dot(.), underscore(_), colon(:), and forward-slash(/).
-
-
-To know how these can be used while creating elements in Testsigma, please refer to the documents below:
-
-1. [Manual Creation of Elements](https://testsigma.com/docs/elements/ios-apps/create-manually/)
-2. [Create an element via Test recorder](https://testsigma.com/docs/elements/android-apps/capture-single-element/)
-
-
diff --git a/src/pages/docs/getting-started/introduction-community.md b/src/pages/docs/getting-started/introduction-community.md
deleted file mode 100644
index b9aeb5d3..00000000
--- a/src/pages/docs/getting-started/introduction-community.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: "Intro: Testsigma Community Edition"
-metadesc: "What is Testsigma Cloud and how to get started with it."
-noindex: false
-order: 1.2
-page_id: "Introduction to Testsigma Community Edition"
-warning: false
-contextual_links:
-- type: section
- name: "Contents"
-- type: link
- name: "Introduction"
- url: "#introduction"
-- type: link
- name: "Setup Testsigma Community Edition"
- url: "#setup-testsigma-community-edition"
-- type: link
- name: "Getting help"
- url: "#getting-help"
-- type: link
- name: "Telemetry Opt-In"
- url: "#telemetry-opt-in"
-
----
-
----
-
-
-Testsigma Community Edition is an open-source end-to-end test automation platform. It packages libraries, APIs, classes, and more that you can install on your workstation and use to start test automation without building a test framework from scratch.
-
-
-
----
-
-## **Setup Testsigma Community Edition**
-[Deploy Testsigma on my workstation](https://testsigma.com/docs/getting-started/setup/overview/)
-
-
----
-
-## **Getting help**
-- Learn how to use, build, and extend the platform. Visit [documentation](https://testsigma.com/docs/).
-- Connect with product experts on the team and in the Community on our [Discord](https://discord.com/invite/5caWS7R6QX).
-- Troubleshooting problems? Report bugs as [Github issues](https://github.com/testsigmahq/testsigma/issues).
-- Refer to our [FAQs](https://testsigma.com/docs/getting-started/faqs/) section for answers to commonly asked questions.
-- Reach out to us at [support@testsigma.com](mailto:support@testsigma.com).
-
-
----
-
-## **Telemetry Opt-In**
-
-As a standard practice, we collect anonymous telemetry data during and after Testsigma is installed on your local machine. You can learn more about Telemetry data and opt-in [here](https://testsigma.com/docs/getting-started/telemetry/).
-
----
\ No newline at end of file
diff --git a/src/pages/docs/getting-started/setup/docker.md b/src/pages/docs/getting-started/setup/docker.md
deleted file mode 100644
index 698ff4e8..00000000
--- a/src/pages/docs/getting-started/setup/docker.md
+++ /dev/null
@@ -1,169 +0,0 @@
----
-title: "Testsigma Docker Setup"
-page_title: "Testsigma Community Edition Docker Setup"
-metadesc: "How to setup Testsigma Community Edition with Docker"
-noindex: false
-order: 1.32
-page_id: "Testsigma Docker Setup"
-warning: false
-contextual_links:
-- type: section
- name: "Contents"
-- type: link
- name: "Prerequisites"
- url: "#prerequisites"
-- type: link
- name: "Setting up Testsigma Community Edition with Docker"
- url: "#setting-up-testsigma-community-edition-with-docker"
-- type: link
- name: "Verifying the installation"
- url: "#verifying-the-installation"
-- type: link
- name: "Connecting to External MySQL"
- url: "#connecting-to-external-mysql"
-- type: link
- name: "Update to new Version(Testsigma Server)"
- url: "#update-to-new-versiontestsigma-server"
-- type: link
- name: "Update to new Version(Testsigma Agent)"
- url: "#update-to-new-versiontestsigma-agent"
-- type: link
- name: "Troubleshooting"
- url: "#troubleshooting"
-- type: link
- name: "Next Steps"
- url: "#next-steps"
----
-
----
-
-This guide will help you setup [Testsigma Server](https://github.com/testsigmahq/testsigma) and MySQL as Docker containers using Docker Compose. This is the easiest way to set up Testsigma on your local machines.
-
----
-
-## **Prerequisites**
- * [Docker](https://docs.docker.com/install/)
- * [Docker Compose](https://docs.docker.com/compose/install/)
-
----
-
-## **Setting up Testsigma Community Edition with Docker**
-
-Create a folder called **testsigma** where you would like to install Testsigma and store the logs and runtime data.
-
-**cd** cmd into this installation folder (testsigma)
-
----
-
-## **Step 1: Download docker-compose.yml file**
-
-Download docker-compose.yml file into the testsigma installation folder from [here](https://github.com/testsigmahq/testsigma/tree/dev/deploy/docker). Download the appropriate file based on your OS.
-
-
-[[info | NOTE:]]
-| - If you are using Apple M1 machines then you should replace the testsigmahq/server image version in docker-compose.yml with the M1 docker image tag. For example if the version is v1.0.0 then you should add "-m1" and make it v1.0.0-m1. So the final image name looks like this "testsigmahq/server:v1.0.0-m1"
-
----
-
-## **Step 2: Run Testsigma Server**
-
-The following command will run Testsigma along with a MySQL database to store data.
-
-```
-$ docker-compose up -d
-```
-
-Check if the containers are running using the following commands
-
-
-```
-$docker ps
-
-CONTAINER ID IMAGE … STATUS PORTS Names
-580db1ec9ad1 testsigmahq/server:m1 … …. 443->443/tcp, 9090->9090/tcp, 9090/tcp testsigma\_server
-318c46259b15 mysql:5.7 … …. 33060/tcp, 55581->3306/tcp testsigma\_mysql
-```
-
-You should see a message: “Testsigma is Running!” once the container is ready.
-
-
-Your Testsigma server should be up and running now. Testsigma server will be accessible at https://local.testsigmaos.com/ui
-
----
-
-## **Verifying the installation**
-
-By default folders db\_data, ts\_data will be created in the installation folder to store the application data and MySQL data. If you want to change this folder path you can open **docker-compose.yml** and change the db\_data volume path under mysql service and ts\_data path under testsigma_server.
-
----
-
-## **Connecting to External MySQL**
-
-If you want to connect to an external/existing MySQL database, add the below environment variables
-
-MYSQL\_HOST\_NAME = < mysql \_host\_name> where mysql\_host\_name is your database url
-MYSQL\_PORT = < port\_number> where mysql is running
-MYSQL\_DB\_NAME = < db\_name> where you want to save data
-MYSQL\_USER = < username>
-MYSQL\_PASSWORD = < password>
-
----
-
-## **Step 3: Install and configure Testsigma Agent**
-
-When we run the Testsigma server using Docker it runs in a separate container(child process), where it cannot access the applications installed in the host machine. But in order to automate Web and Mobile Apps the Testsigma Server (running in docker) has to access Browsers and Mobile Devices connected to the host machine.
-
-To achieve this we use Testsigma Agent that connects the Testsigma Server with the host machine to access the browsers and mobile devices connected.
-
-### **Download and Install Testsigma Agent**
-
-Login to https://local.testsigmaos.com/ui and follow the steps mentioned here([Setup: Windows, Mac, Linux](https://testsigma.com/docs//agent/setup-on-windows-mac-linux/)) to Install and configure the the Agent
-
----
-
-## **Update to new Version(Testsigma Server)**
-
- 1. Stop the Docker images/container with name testsigma in Docker Desktop, alternatively you can use the below commands to kill the processes
- a. `sudo su`
- b. `docker container kill $(docker ps -q)`
- 2. Download the latest version of docker-compose.yml file into the testsigma installation folder from [here](https://github.com/testsigmahq/testsigma/tree/dev/deploy/docker).
- 3. Run
- `
- $ docker-compose up -d
- `
- 4. Verify the status by running `$docker ps` command
- 5. Now login to check the updated version of Testsigma Server here https://local.testsigmaos.com/ui
-
----
-
-## **Update to new Version(Testsigma Agent)**
-
- 1. Stop the running agent by executing the stop.sh
- 2. Delete the TestsigmaAgent folder
- 3. Login to https://local.testsigmaos.com/ui
- 4. Go to Agents menu to download the latest version of Testsigma Agent
- 5. Now start the Agent by executing start.sh
-
-[[info | NOTE:]]
-|- If you are facing any issues after updating Testsigma Agent refer to [Agent - Startup and Registration Errors](https://testsigma.com/docs/agent/troubleshooting/setup-issues/) .
-|- If you are still facing the issue, delete the [agent manually](https://testsigma.com/docs/agent/force-delete/) and install again.
-
----
-
-## **Troubleshooting**
-
-- If you encounter any errors during this process, check out our guide on [debugging deployment errors](https://testsigma.com/docs/troubleshooting/setup/server-docker-deployment-errors/) and for [logs](https://testsigma.com/docs/troubleshooting/setup/server-docker-deployment-errors/#checking-logs)
-- If you are still facing any issue, please reach out to [support@testsigma.com](mailto:support@testsigma.com) or join our [Discord Server](https://discord.com/invite/5caWS7R6QX) to speak to the Testsigma team directly!
-
----
-
-## **Next Steps**
-
-1. [Get Started with Automating Web Applications](https://testsigma.com/tutorials/getting-started/automate-web-applications/)
-2. [Get Started with Automating Mobile Web Applications](https://testsigma.com/tutorials/getting-started/automate-mobile-web-applications/)
-3. [Get Started with Automating Android Apps](https://testsigma.com/tutorials/getting-started/automate-android-applications/)
-4. [Get Started with Automating iOS Apps](https://testsigma.com/tutorials/getting-started/automate-ios-applications/)
-5. [How to automate tests for Android Apps using local devices](https://testsigma.com/tutorials/test-cases/mobile-apps/build-tests-using-local-android-devices/)
-6. [How to automate tests for iOS Apps using local devices](https://testsigma.com/tutorials/test-cases/mobile-apps/build-tests-using-local-ios-devices/)
-
----
\ No newline at end of file
diff --git a/src/pages/docs/getting-started/testsigma-community-cloud.md b/src/pages/docs/getting-started/testsigma-community-cloud.md
deleted file mode 100644
index bb30bb9f..00000000
--- a/src/pages/docs/getting-started/testsigma-community-cloud.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: "Testsigma Community Cloud"
-metadesc: "How to register for Testsigma Community Cloud."
-noindex: false
-order: 1.4
-page_id: "Testsigma Community Cloud"
-warning: false
-contextual_links:
-- type: section
- name: "Contents"
-- type: link
- name: "Registering for Testsigma Community Cloud"
- url: "#registering-for-testsigma-community-cloud"
----
-
----
-
-As a Testsigma CE user, you can integrate your self-hosted open-source platform with our Community Cloud and get free access to:
-- **Test Lab**: Up to 200 minutes/month access to 800+ browsers/OS and real Android and iOS devices.
-- **Storage**: Store up to 5GB of your data on the cloud monthly, including your apps, attachments, screenshots, video recordings, logs, and more.
-- **Visual Testing**: Compare up to 1000 application screens per month to ensure the pixel-level quality of your UI by saving baseline visuals and comparing all future app versions against it.
-- **iOS App Testing**: You can create a Provisioning Profile in Testsigma cloud and run your automated iOS app tests on your physical device.
-- **Add-ons Marketplace**: Cover a wide range of automation and test scenarios by installing a comprehensive set of custom add-ons built and tested by the Testsigma community and engineering team.
-- **Testsigma Discord Community**: Connect with some of the most experienced and creative test automation practitioners worldwide.
-
----
-
-## **Registering for Testsigma Community Cloud**
-
-On your Testsigma application,
-- Go to **Settings**.
-- Click on **Testsigma Cloud (CE)** option.
-- Register using one of the options provided.
-
-You’re now connected to the Cloud!
-
----
\ No newline at end of file
diff --git a/src/pages/docs/reports/runs/rerun.md b/src/pages/docs/reports/runs/rerun.md
deleted file mode 100644
index e2a9bde6..00000000
--- a/src/pages/docs/reports/runs/rerun.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: "Rerun Test Cases from Run Results"
-metadesc: "Learn in detail how to rerun failed test cases, all test cases, or custom test cases from a particular test run result in Testsigma application"
-noindex: false
-order: 13.22
-page_id: "How to rerun test cases from test run results in Testsigma"
-warning: false
-contextual_links:
-- type: section
- name: "Contents"
-- type: link
- name: "Steps to Rerun from run results"
- url: "#steps-to-rerun-from-run-results"
----
-
-
-
-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. Here's how you can Rerun Test Cases from Test Run Results in Testsigma.
-
-Here is a quick GIF demonstrating how to Rerun Test Cases from Run Results in Testsigma.
-
-
----
-
-## **Steps to Rerun from run results**
-1. Navigate to **Test Development > Run Results**.
-
-2. Hover over to Test Plan for which you need the report and click on **View Reports**.
-
-3. Click on **Rerun**.
-
-4. On the **Re-run configuration** 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.
- - Click on **Select Cases for Re-Run**.
- 
- - From **Select Cases for Re-Run** prompt,
- - Select all test cases you want to Re-run.
- 
- - If there are data-driven test cases, you can also select the iterations you want to run in that specific case.
- 
-
-6. Click on **Start** to rerun.
-
\ No newline at end of file
diff --git a/src/pages/docs/reports/runs/test-case-reports.md b/src/pages/docs/reports/runs/test-case-reports.md
deleted file mode 100644
index f4b5f454..00000000
--- a/src/pages/docs/reports/runs/test-case-reports.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: "Test Case Reports in Testsigma"
-metadesc: "This article helps you understand how to view test run results on the basis of test cases executed in Testsigma. Steps to generate Test Case Reports"
-noindex: false
-order: 13.26
-page_id: "Test Case Reports in Testsigma"
-warning: false
-contextual_links:
-- type: section
- name: "Contents"
-- type: link
- name: "Prerequisites"
- url: "#prerequisites"
-- type: link
- name: "Steps to generate Test Case Reports"
- url: "#steps-to-generate-test-case-reports"
----
-
----
-
-Test case reports provide detailed information about the test cases executed, their results, and insights. This article discusses how to export test case reports in Testsigma.
-
----
-
-## **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 plan](https://testsigma.com/docs/test-management/test-plans/overview/#steps-to-create-a-test-plan).
-
----
-
-## **Steps to generate Test Case Reports**
-1. On your dashboard click on **Run Results**.
-
-
-2. Click anywhere on the test plan result for which you need the report.
-
-
-3. Results are available in **Test Case**, **Test Suite**, and **Test Plan** level. Click on **Test Case** to view the results grouped by **Test Cases**.
-
-
-[[info | **NOTE**:]]
-| You can also download the report in Junit and MS Excel Sheet by following the steps below:
-| 1. Click on the Export icon.
-|
-| 2. Select the format from the drop down in which you want to export.
-|
-
-Here’s a quick GIF demonstrating how to generate Test Case Reports.
-
----
\ No newline at end of file
diff --git a/src/pages/docs/reports/runs/test-machine-reports.md b/src/pages/docs/reports/runs/test-machine-reports.md
deleted file mode 100644
index 6afc51ea..00000000
--- a/src/pages/docs/reports/runs/test-machine-reports.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: "Test Machine Reports in Testsigma"
-metadesc: "How to view test run results by the test machines that the test cases were executed on in Testsigm alpplication"
-noindex: false
-order: 13.24
-page_id: "Test Machine Reports in Testsigma"
-warning: false
-contextual_links:
-- type: section
- name: "Contents"
-- type: link
- name: "Steps to get a Test Machine Report"
- url: "#steps-to-get-a-test-machine-report"
-- type: link
- name: "How to generate Test Machine Reports:"
- url: "#how-to-generate-test-machine-reports"
----
-
----
-
-If you run your tests on multiple test machines/devices of different configurations to test for compatibility across browsers and devices, you should also be able to generate a test report for each one of these test machines/devices.
-
-In Testsigma, you can group reports by Test Machines when you need to understand:
-1. Do the same tests fail on the same machine every time?
-2. If yes, then can you modify our application specifically to solve test failures only in a specific machine?
-
-
----
-## **Steps to get a Test Machine Report**
-
-This gif demonstrates how to group reports on the basis of test machines:
-
-
-
----
-## **How to generate Test Machine Reports:**
-
-1. Select the project for which you need the reports
-2. Navigate to **Test Development > Run Results**, you should see a page like this:
-
- 
-
-3. Click on the Test Plan for which you need the report, you should see a test runs page like this:
-
- 
-
-4. In the drop-down menu in the middle column, choose “Test Machine Results”. The drop-down is highlighted below for your reference:
- 
-
-5. You will be able to view the results grouped by Test Machines.
-
-
- There are multiple actions that you can take on these results. These actions can be initiated via the buttons available on the top right column of the results column:
- 
-
- These actions are:
-
- 1. **Search the results:** the run results can be filtered by name here
- 2. **Rerun the failed test cases or rerun all test cases:** You can click on any of the options to initiate reruns of the test cases accordingly. Read more about [test reruns](https://testsigma.com/docs/reports/runs/rerun/).
- 3. **Export the results:** Here, you can export the run results in the form of xls or xml. Read more about [exporting as xls](https://testsigma.com/docs/reports/export-reports/export-report-xls/) and [exporting as Junit](https://testsigma.com/docs/reports/export-reports/export-reports-junit/).
- 4. **Filter the results:** You can filter the results by different criteria that appear on click on the filter button, read more about it here.
- 5. **Display details of the result:** There is a toggle button in the end for more run details.
-
-
-
-
diff --git a/src/pages/docs/reports/runs/test-suite-reports.md b/src/pages/docs/reports/runs/test-suite-reports.md
deleted file mode 100644
index f1b9511d..00000000
--- a/src/pages/docs/reports/runs/test-suite-reports.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: "Test Suites Reports in Testsigma"
-metadesc: "A Test Suite is a collection of test cases. Learn how to view test run results on the basis of test suites executed in Testsigma"
-noindex: false
-order: 13.25
-page_id: "Test Suites Reports in Testsigma"
-warning: false
-contextual_links:
-- type: section
- name: "Contents"
-- type: link
- name: "Steps to generate Test Suite Reports"
- url: "#steps-to-generate-test-suite-reports"
----
-
----
-
-A Test Suite is a collection of test cases grouped on the basis of a specific feature or a requirement. In Testsigma, you can run multiple test suites at once, and analyze test reports grouped by Test Suites.
-
-Here is a quick gif that demonstrates how to group reports on the basis of test suites.
-
-
-
-
----
-## **Steps to generate Test Suite Reports:**
-
-1. Select the project for which you need the reports
-2. Navigate to **Test Development > Run Results**.
- 
-
-3. Click on the **Test Plan** for which you need the report.
-
- 
-
-4. From the drop-down menu, click on **Test Suite Results**. The drop-down is also highlighted below for your reference:
-
- 
-
-5. You will be able to view the results grouped by Test Suites.
-
-
- There are multiple actions that you can take on these results. These actions can be initiated via the buttons available on the top right column of the results column as also shown in the screenshot below:
-
- 
-
----
-## **These actions are:**
-1. **Search the results:** the run results can be filtered by name here
-2. **Rerun the failed test cases or rerun all test cases:** You can click on any of the options to initiate reruns of the test cases accordingly. Read more about [test reruns](https://testsigma.com/docs/reports/runs/rerun/).
-3. **Export the results:** Here, you can export the run results in the form of xls or xml. Read more about [exporting as xls](https://testsigma.com/docs/reports/export-reports/export-report-xls/) and [exporting as xml](https://testsigma.com/docs/reports/export-reports/export-reports-junit/).
-4. **Filter the results:** You can filter the results by different criteria that appear on click on the filter button, read more about it [here](https://testsigma.com/docs/reports/runs/filter-custom-reports/).
-5. **Display details of the result:** There is a toggle button in the end for more run details.
diff --git a/src/pages/docs/test-cases/step-types/create-steps.md b/src/pages/docs/test-cases/step-types/create-steps.md
deleted file mode 100644
index 476a27de..00000000
--- a/src/pages/docs/test-cases/step-types/create-steps.md
+++ /dev/null
@@ -1,82 +0,0 @@
----
-title: "Create Test Steps in Testsigma"
-metadesc: "How to create Test Steps in Testsigma "
-noindex: false
-order: 4.21
-page_id: "Create Test Steps in Testsigma"
-warning: false
-contextual_links:
-- type: section
- name: "Contents"
-- type: link
- name: "Pre-requisites"
- url: "#pre-requisites"
-- type: link
- name: "Ways to create Test Steps"
- url: "#ways-to-create-test-steps"
-- type: link
- name: "Web & Mobile Web"
- url: "#web--mobile-web"
-- type: link
- name: "iOS"
- url: "#ios"
-- type: link
- name: "Android"
- url: "#android"
----
-
----
-
-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.
-
-[[info | NOTE:]]
-|In Testsigma we will be writing test steps in simple English, which automatically gets converted into automated actions.
-
-
-
----
-##**Pre-requisites:**
-
-This document assumes that you know how to [Create a test case](https://testsigma.com/docs/test-cases/manage/add-edit-delete/).
-
-
-
----
-##**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.
-
-
-
-Follow the links to know how to use these approaches for:
-
----
-##**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/)
-
-
-
----
-##**iOS**
-
- * [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/)
-
-
-
-
-
-
-
-