** with the random string associated with your WDA build.
+
+6. Generating a New WDA for Installation
+
+Run the following commands to create a new WDA package for installation.
+
+ ```
+ xcodebuild -scheme WebDriverAgentRunner -sdk iphoneos -configuration Release -derivedDataPath /tmp/derivedDataPath
+ cd /tmp/derivedDataPath/Build/Products/Release-iphoneos
+ mkdir -p Payload
+ mv WebDriverAgentRunner-Runner Payload
+ zip Payload wda.zip
+ mv wda.zip wda.ipa
+ ```
+
+The above commands will generate a new **wda.ipa** file.
+
+---
diff --git a/src/pages/docs/desired-capabilities/network-logs.md b/src/pages/docs/desired-capabilities/network-logs.md
index 048819c5..f7433bfe 100644
--- a/src/pages/docs/desired-capabilities/network-logs.md
+++ b/src/pages/docs/desired-capabilities/network-logs.md
@@ -1,15 +1,18 @@
---
title: "Network Logs"
-page_title: "Network Logs in Testsigma: Track and Analyze Application Network Activity"
-metadesc: "Use Testsigma's Network Logs feature to track and analyze network activity. You can gain insights into requests, responses, and performance optimization. Start optimizing your application's network behavior today."
+page_title: "Network Logs: Analyse Application Network Activity"
+metadesc: "Explore comprehensive network log features for insightful test execution analysis. Capture, analyse, and debug network interactions seamlessly."
noindex: false
order: 15.92
-page_id: "Network Logs"
+page_id: "network-log-management"
search_keyword: ""
warning: false
contextual_links:
- type: section
name: "Contents"
+- type: link
+ name: "Prerequisites"
+ url: "#prerequisites"
- type: link
name: "Enable Network Logs in Test Case"
url: "#enable-network-logs-in-test-case"
@@ -27,45 +30,39 @@ Testsigma allows you to capture and analyse network traffic during test executio
This documentation will guide you on how to enable the network log in Test Case and Test Plan, access, view the status, and download network logs in the ad-hoc run page and the run test case page.
-[[info | NOTE:]]
-| Network Log will be enabled by default for Web and Mobile Web applications, but you must manually enable it for Android and iOS applications.
-
---
-### **Prerequisites**
+## **Prerequisites**
Before starting, understand the concepts of [Projects](https://testsigma.com/docs/projects/overview/), [Test Cases](https://testsigma.com/docs/test-cases/manage/add-edit-delete/), [Test Plans](https://testsigma.com/docs/test-management/test-plans/overview/), [Ad-hoc Runs](https://testsigma.com/docs/runs/adhoc-runs/), and [Test Machines](https://testsigma.com/docs/test-management/test-plans/manage-test-machines/) in Testsigma. Familiarising yourself with these concepts will make working with the Network Log feature easier.
+[[info | Note:]]
+| By default, Network Log is enabled for Web and Mobile Web applications, but for Android and iOS applications, you need to enable it manually.
+
+
---
## **Enable Network Logs in Test Case**
-1. Click **Run** in the top right corner of the screen on the **Test Case** page. 
-2. Select **BrowserStack** as a **Test Lab** on the **Ad-hoc Run** page on the right side of the screen, enable the **Network Log toggle**, and click **Run Now** to start Test Execution. 
-
-Here is a quick GIF demonstrating the above workflow: 
+1. Click **Run** in the top right corner of the screen on the Test Case details page.
+2. Select **BrowserStack** as a Test Lab on the **Ad-hoc Ru**n page on the right side of the screen, enable the **Network Log** toggle, and click **Run Now** to start Test Execution. 
---
## **Enable Network Logs in Test Plan**
-1. Navigate to the **Test Machines & Suites Selection** tab on the **Create** or **Edit Test Plan** page.
-2. Click on **Add Machine/Device** to add a test machine, and click on the **Edit** button in Created Test Machines/Device to edit an existing machine. 
-3. On the **Add** or **Edit Machine/Device** page, select **Test Lab Type** as **BrowserStack**, enable the **Network Log toggle**, and click **Update**. 
-
-Here is a quick GIF demonstrating the above workflow: 
+1. Navigate to the **Add Test Suites & Link Machine Profiles** tab on the **Create** or **Edit Test Plan** page.
+2. Click the **Test Machine Settings** icon, and the **Adding** or **Editing Test Machine/Device Profiles** overlay will appear.
+3. On the **Add** or **Edit Machine/Device Profile** overlay, select Test Lab Type as **BrowserStack**, enable the **Network Log** toggle, and click **Create/Update**. 
---
## **Network Log Management**
-To access and analyse the captured network logs in Testsigma, follow the steps outlined below after completing the test execution on the Run Test Case Page.
-
-1. Navigate to the **Logs** tab on the **Run Test Case** page. 
-2. You will find a section dedicated to the **Network Logs** under the **Logs** tab.
-3. You can see a summary of the captured network activity in the **Network Logs Preview**. The preview displays key information, such as request URLs, HTTP methods, status codes, and response sizes. You can quickly scan through the logs to identify any anomalies or errors in the network interactions. 
-4. Click **Download** in the top-right corner of the screen to download the network log file in **har** format if you want to analyse the network logs offline.
+After completing the test execution on the Run Test Case Page, you should follow these steps to access and analyse the captured network logs:
-Here is a quick GIF demonstrating the above workflow: 
+1. Click the **Show Logs** button on the Run Results page and locate the section dedicated to **Network Logs** under the **Logs** tab.
+2. In the **Network Logs** Previews, you can see a summary of captured network activity, including request URLs, HTTP methods, status codes, and response sizes. Quickly scan through the logs to identify anomalies or errors in the network interactions.
+3. Click **Download Log** File at the top-right of the screen to retrieve the network log file in **HAR** format. You can then analyse the network logs offline. 
---
diff --git a/src/pages/docs/desired-capabilities/overview.md b/src/pages/docs/desired-capabilities/overview.md
index 87a361da..d9bdbc7a 100644
--- a/src/pages/docs/desired-capabilities/overview.md
+++ b/src/pages/docs/desired-capabilities/overview.md
@@ -38,7 +38,7 @@ Desired Capabilities are a set of properties used for customizing the Test Envir
## **Desired Capabilities Format**
Desired Capabilities are entered as **key-value** pairs. Enter the details for Desired Capabilities as specified below:
-- **Key:** Enter the name of the capability.
+- **Key:** Specific properties or attributes that can be set for the test environment.
- **Data Type:** The data type of the value of the specific Desired Capability.
- **Value:** The value of the Desired Capability.
diff --git a/src/pages/docs/elements/auto-healing.md b/src/pages/docs/elements/auto-healing.md
new file mode 100644
index 00000000..3b8853cc
--- /dev/null
+++ b/src/pages/docs/elements/auto-healing.md
@@ -0,0 +1,101 @@
+---
+title: "AI Enabled Auto-Healing"
+metadesc: "Auto Healing helps prevent object flakiness when there are minor changes to the elements. This article discusses how to enable Auto Healing Feature in Testsigma"
+noindex: false
+order: 6.91
+page_id: "Auto Healing"
+warning: false
+contextual_links:
+- type: section
+ name: "Contents"
+- type: link
+ name: "Prerequisites"
+ url: "#prerequisites"
+- type: link
+ name: "Steps to Enable Auto Healing Feature"
+ url: "#steps-to-enable-auto-healing-feature"
+- type: link
+ name: "Use Case for Auto Healing"
+ url: "#use-case-for-auto-healing"
+- type: link
+ name: "Auto Healing Insights"
+ url: "#auto-healing-insights"
+---
+
+---
+
+
+Auto Healing helps prevent object flakiness and ensures your tests are reliable even when there are minor changes to the elements, and the locators fail to identify the element based on their previous attributes. This article discusses Auto Healing feature in Testsigma.
+
+---
+
+## **Prerequisites**
+
+- You should know how to [create a test case](https://testsigma.com/docs/test-cases/manage/add-edit-delete/).
+
+- You should know how to [create elements](https://testsigma.com/docs/elements/overview/).
+
+---
+
+## **Steps to Enable Auto Healing Feature**
+
+1. Navigate to **Settings > Preferences**.
+
+
+
+2. On the **Preferences** page, enable the toggle on **Auto Healing** widget.
+
+
+
+Your tests are ready to execute without manual intervention whenever there are changes in the build. The Auto Healing feature will take care of correcting the elements.
+
+Here’s the GIF demonstrating how to enable the Auto Healing feature.
+
+
+---
+
+## **Use Case for Auto Healing**
+
+Let’s say we are testing a login page for https://simply-travel.testsigma.com/.
+
+Here are steps to produce:
+1. Navigate to https://simply-travel.testsigma.com/.
+2. Click on Login/SignUp.
+3. Click on Login.
+4. Enter bsk08@gmail.com in the email field.
+5. Click on Continue.
+6. Enter 98764321 in the password field.
+7. Click on Submit.
+
+Consider that the XPATH for Login button on the step 3 changed from **//BUTTON[@id='login']** to **//BUTTON[@id='login-popUp']**.
+
+On executing the test case with **Auto Healing** feature enabled, the test lab will successfully locate the element with the new XPATH.
+
+
+
+---
+
+## **Auto Healing Insights**
+
+On successful completion of test execution, you can check the auto healing insights from the results page. Follow the steps below:
+
+1. Click on the test step in which the element is auto healed.
+
+
+
+2. Go to the step result and click on **Auto Heal**. This will open the **Auto Healing Details** overlay.
+
+
+
+3. You can check the **Auto Healing Insights** here.
+
+
+
+Here’s the GIF demonstrating how to check the Auto Healing insights.
+
+
+
+
+
+
+---
\ No newline at end of file
diff --git a/src/pages/docs/faqs/web-apps/how-to-enter-non-text-keys-in-test-cases.md b/src/pages/docs/faqs/web-apps/how-to-enter-non-text-keys-in-test-cases.md
index 55f160b3..62ded0c8 100644
--- a/src/pages/docs/faqs/web-apps/how-to-enter-non-text-keys-in-test-cases.md
+++ b/src/pages/docs/faqs/web-apps/how-to-enter-non-text-keys-in-test-cases.md
@@ -3,7 +3,7 @@ title: "Entering Non-Text Keys in Test Cases"
page_title: "Efficiently enter Non-Text Keys in Test Cases for Testing"
metadesc: "Learn how to simulate non-text key inputs seamlessly in your test cases, ensuring precise testing outcomes. Explore the guide for effective testing strategies."
noindex: false
-order: 24.2
+order: 24.14
page_id: "Enter non-text keys in Test Cases"
warning: false
contextual_links:
diff --git a/src/pages/docs/getting-started/testsigma-sample-apps.md b/src/pages/docs/getting-started/testsigma-sample-apps.md
index e37badfa..a6f7fbfc 100644
--- a/src/pages/docs/getting-started/testsigma-sample-apps.md
+++ b/src/pages/docs/getting-started/testsigma-sample-apps.md
@@ -25,9 +25,10 @@ This article provides a few sample applications for users to practice testing in
*For more information on how to create test cases, refer to [test cases](https://testsigma.com/docs/test-cases/overview/).*
-2. Use the following links for practicing mobile app testing.
+2. Use the following apps for practicing mobile app testing.
- [Sample IPA Application](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/SimplyTravel.ipa)
- [Sample APK Application](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/appdebug.apk)
+ - [SMS Forwarder Application](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/smsforward.apk)
*For more information on uploading mobile apps for testing, refer to [upload android and iOS apps](https://testsigma.com/docs/uploads/upload-apps/).*
diff --git a/src/pages/docs/runs/test-locally-hosted-applications.md b/src/pages/docs/runs/test-locally-hosted-applications.md
index 1ba473fd..fb001475 100644
--- a/src/pages/docs/runs/test-locally-hosted-applications.md
+++ b/src/pages/docs/runs/test-locally-hosted-applications.md
@@ -13,16 +13,18 @@ warning: false
Testsigma’s access to applications deployed on your local machine/network is limited for security reasons. As a result, there may be times when Testsigma servers are unable to access your locally hosted applications. To prevent this, try one of the methods below.
---
+
### IP Whitelisting
In development/QA environments, it is common to keep your application hosted on servers with restricted Access from Unknown Sources. One of the ways you can use Testsigma Labs to execute tests is by whitelisting Testsigma IP Addresses on your server.
Testsigma Labs has reserved the following IP blocks for our services. Please whitelist these IP addresses to allow traffic in a restricted network setting.
-Login to https://app.testsigma.com and go to **Settings > About** to see the IP range to whitelist
+Login to https://app.testsigma.com and go to **Settings > Testsigma IP info** to see the IP range to whitelist.
-
+
---
+
### Hybrid Execution
Hybrid Executions are local executions that use your local machines to run the tests instead of devices available on the cloud. To perform this, you need to install the 'Testsigma Agent'.
@@ -30,6 +32,10 @@ Hybrid Executions are local executions that use your local machines to run the t
The Testsigma Agent connects the Testsigma server to your local machine. Learn more about [Testsigma Agent](https://testsigma.com/docs/agent/overview/).
---
+
### Secure Tunnel/VPN
Contact support **[(support@testsigma.com)](mailto:support@testsigma.com)** to learn more about this. Our team will set up this for you.
+
+
+---
\ No newline at end of file
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
index a3817fb7..f3b93b42 100644
--- 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
@@ -5,6 +5,12 @@ noindex: false
order: 4.625
page_id: "Recording tests with webview for hybrid iOS apps"
warning: false
+contextual_links:
+- type: section
+ name: "Contents"
+- type: link
+ name: "Executing Native Android/iOS App Tests in Hybrid Model"
+ url: "#executing-native-androidios-app-tests-in-hybrid-model"
---
---
@@ -38,4 +44,50 @@ On selecting the WebView the following NLP is added,
[[info | **NOTE**:]]
| Recording tests with multiple webviews will be the same for Android and iOS applications.
+---
+
+## **Executing Native Android/iOS App Tests in Hybrid Model**
+
+Considering you already have a Test Suite containing iOS Application Test Cases, the procedure for executing a native iOS Application using Testsigma in a local environment is as follows:
+
+**1. Register a Local Agent.**
+
+We need to add a local agent in Testsigma and link this agent as a Test Machine to Test Suites while creating the Test Plan.
+
+
+**2. Setup the Local Mac and iOS Device for Hybrid Execution.**
+
+We must configure the local machine once the local agent is added to Testsigma. This is done so that the local machine can accept communication in the form of HTTP packets from Testsigma servers. This step is preconfigured in other Cloud Execution Models such as Testsigma Labs, Sauce Labs, and BrowserStack. If you prefer the easy method, use the cloud execution models to select the execution environment from the list of available devices.
+
+Continuing with the Hybrid Execution setup, we must first set up the Testsigma agent on the local Mac. Please check the following article for a detailed guide on [setting up Testsigma Agent](https://testsigma.com/docs/agent/setup-on-windows-mac-linux/).
+
+Assuming you already have the prerequisites, such as Appium and XCode configured, we will run tests once the Testsigma Agent is configured.
+
+**2. Create Execution and add Execution Configuration.**
+
+While creating the Execution Configuration for iOS, we need to provide some extra information in case of Hybrid Executions for Testsigma to properly connect to the local iOS device. The most important fields on the page are:
+
+**Machine:** Select the local System we added in the previous Step. This is the Mac device which Testsigma directly communicates with, and from there, the communication data is passed to the Test iOS device connected to this Mac.
+
+**OS Version:** Select the iOS version in the Test Device.
+
+**Appium URL:** Enter the Appium URL you started the server with. If you used the default configuration, the URL would be:
+http://0.0.0.0:4723/wd/hub
+
+**Device Name:** Enter the serial number of the iOS Device.
+
+**UDID:** Enter the unique device identifier UDID code for your iOS device. Here's a guide to finding your UDID using Itunes App on your Mac - WhatsmyUDID
+
+**BundleID:** Use this option if the app has already been installed on the Test iOS device (Recommended).
+- **BundleID:** BundleID is the unique identifier of an iOS App. Here's a guide to finding your App BundleID - [Finding the App Bundle ID](https://pspdfkit.com/guides/ios/faq/finding-the-app-bundle-id/)
+
+**App Path:** Use this option if the app to be tested is located on the Mac and you want to avoid installing it on the test device.
+- **Use IPA:** Specify the local Mac machine's path to the IPA file.
+
+Once the Execution Configuration is created, we can finalize the Execution creation by clicking on the Create button.
+
+
+[[info | **NOTE**:]]
+| The steps remain the same for executing native Android tests in the hybrid model as well. We use APK files instead of IPA for Android tests.
+
---
\ No newline at end of file
diff --git a/src/pages/docs/test-cases/image-injection.md b/src/pages/docs/test-cases/image-injection.md
index b1837c2b..58fb2681 100644
--- a/src/pages/docs/test-cases/image-injection.md
+++ b/src/pages/docs/test-cases/image-injection.md
@@ -1,14 +1,17 @@
---
title: "Image Injection"
-pagetitle: "Image Injection Testsigma: Enhance Mobile App Testing"
-metadesc: "Image Injection feature elevates mobile app testing. You can seamlessly integrate QR codes and images to create realistic test scenarios on Android and iOS."
+pagetitle: "Image Injection in Testsigma: Enhance Mobile App Testing"
+metadesc: "Enhance your testing process by seamlessly incorporating images into test steps using Image Injection. Streamline workflows and improve accuracy."
noindex: false
order: 4.70
-page_id: "Image Injection"
+page_id: "image-injection-testsigma"
warning: false
contextual_links:
- type: section
name: "Contents"
+- type: link
+ name: "Prerequisites"
+ url: "#prerequisites"
- type: link
name: "Manual Image Injection using NLP"
url: "#manual-image-injection-using-nlp"
@@ -19,35 +22,38 @@ contextual_links:
---
-Testsigma allows you to enhance your testing process by inserting images into your test steps using Image Injection. You can use this feature, particularly for scenarios where you must interact with images, QR codes, or visual elements within your application. This documentation will guide you through both methods of injecting images into your test case: manual image upload and camera image injection.
-
-[[info | Note:]]
-| - You can utilise the Image Injection feature, exclusively available for **Android** and **iOS** apps.
-| - Ensure you upload image files in **PNG** format and wait a few seconds while the scanner scans the image.
+Testsigma enables you to enhance your testing process by inserting images into your test steps through Image Injection. This feature is handy for scenarios that require interactions with images, QR codes, or visual elements within your application. This documentation will guide you through both methods of injecting images into your test case: manual image upload and camera image injection while recording.
---
-### **Prerequisites**
+## **Prerequisites**
Before using Image Injection, you must understand specific concepts such as creating [Projects](https://testsigma.com/docs/projects/overview/), [Test Cases](https://testsigma.com/docs/test-cases/manage/add-edit-delete/), [Test Steps](https://testsigma.com/docs/test-cases/create-steps-nl/overview/), [Test Data Types](https://testsigma.com/docs/test-data/types/overview/), [Uploading Applications](https://testsigma.com/docs/uploads/upload-apps/), [Uploading Files](https://testsigma.com/docs/uploads/upload-files/), recording steps for [Android](https://testsigma.com/docs/test-cases/create-steps-recorder/android-apps/reorder/) and [iOS](https://testsigma.com/docs/test-cases/create-steps-recorder/ios-apps/reorder/), and performing Ad-hoc runs in [Android](https://testsigma.com/docs/runs/adhoc-runs/#android-application) and [iOS](https://testsigma.com/docs/runs/adhoc-runs/#ios-application).
+[[info | Note:]]
+| Ensure that you upload image files in **PNG** format for Image Injection, which is exclusively available for **Android** and **iOS** apps, and allow a few seconds for the scanner to complete the image scan.
+
---
## **Manual Image Injection using NLP**
-Using NLP in this method, you can manually add image injection steps to your test case. You can replace **test-data** with the image to add QR code images stored in your uploads.
+You can manually add image injection to test steps using NLPs. Use the NLP to have the placeholders for **test data** and replace **test data** with the **˄ Upload** to add QR code images stored in your uploads.
-1. Select the **NLP - Scan image from test data** from the dropdown list of suggestions that appears in the test step by searching.
-2. Click the **test data** placeholder to replace it, and then select the **˄|Upload|** from the **Test Data Types** dropdown menu. Select the file you want to add to the test step from the **˄ Uploads** section on the right side of the screen. 
-3. Remember, using the image scanning feature, you can execute your **Test Cases** and **Test Plans**. You can turn on **Camera Image Injection** for both **Ad-hoc runs** and when **adding a machine or device** to a **Test Plan**. When you run the test case, you can use the image you added using NLP for image injection.
+1. Use the NLP - **Scan image from test data** from the dropdown list of suggestions that appears in the test step by searching.
+2. Click the **test data** placeholder to replace it by selecting the **˄ Upload** from the **Test Data Types** dropdown menu.
+3. Select the file you want to add to the test step from the **˄ Uploads** section on the right side of the screen. 
+4. Remember to enable the **Camera Image Injection** toggle for both **Ad-hoc runs** and when **Adding** or **Editing Test Machine/Device Profiles** before running tests. 
---
## **Camera Image Injection during Recording**
-During test step recording, you can simplify the image injection process by using the camera image injection feature to insert QR code images directly.
+Simplify the image injection process during the test step recording using the camera image injection feature to insert QR code images directly.
-1. Click the **Record** button at the screen's top right corner to bring up the Record Test Steps overlay. Then, choose the **Version**, **Device**, and **Application**. Enable the toggle button for **Camera Image Injection** while recording test steps. Finally, start recording the test step by clicking the **Record** button again.
-2. Click the **Scan Image (Camera)** icon in the right sidebar of the **Recording** Overlay to upload the QR code image. Select the file you want to add to the test step from the **˄ Uploads** overlay. 
+1. Click the **Record** button at the screen's top right corner to bring up the Record Test Steps overlay.
+2. Choose the **Version**, **Device**, and **Application**.
+3. Enable the toggle button for **Camera Image Injection** while recording test steps.
+4. Start recording the test step by clicking the **Record** button again. 
+5. Click the **Scan Image (Camera)** icon in the right sidebar of the Recording page to upload the QR code image. Select the file you want to add to the test step from the **˄ Uploads** overlay. 
---
\ No newline at end of file
diff --git a/src/pages/docs/test-data/types/mailbox.md b/src/pages/docs/test-data/types/mailbox.md
index bd0c9bce..acc1f802 100644
--- a/src/pages/docs/test-data/types/mailbox.md
+++ b/src/pages/docs/test-data/types/mailbox.md
@@ -27,7 +27,12 @@ contextual_links:
- type: link
name: "Generate Mail Box Alias for Test Cases Execution"
url: "#generate-mail-box-alias-for-test-cases-execution"
-
+- type: link
+ name: "Sample Test Case for 2FA using Mailbox"
+ url: "#sample-test-case-for-2fa-using-mailbox"
+- type: link
+ name: "Creating Test Case for 2FA Using MailBox"
+ url: "#creating-test-case-for-2fa-using-mailbox"
---
---
@@ -137,4 +142,50 @@ With Testsigma, you can generate new mailbox aliases every time during test case
Below is a screenshot showing a test case generating a mailbox alias and getting content from the email.
+
+
+---
+
+
+## **Sample Test Case for 2FA using Mailbox**
+
+Two-factor authentication provides additional protection for your application. With Testsigma, you can easily set up Mailbox, retrieve OTP using mailbox functions, and perform tests securely. This article discusses testing 2FA for MailBox.
+
+### **Prerequisites:**
+
+- You should know how to [create a test case](https://testsigma.com/docs/test-cases/manage/add-edit-delete/).
+
+- You should know how to use [mailbox](https://testsigma.com/docs/test-data/types/mailbox/) & [data generator](https://testsigma.com/docs/test-data/types/data-generator/) test data types.
+
+- You need to have a dedicated Mailbox for your account. Contact **support@testsigma.com** for more information.
+
+---
+
+## **Creating Test Case for 2FA Using MailBox**
+
+1. Navigate to **Create Tests > Test Cases**, and click on **Create Test Case**.
+
+
+
+2. On the **Test Case details** page, create test steps manually or using the recorder.
+
+
+
+ - For Step 4, we use **& Mailbox** and enter the email linked to the account in the email input field.
+ 
+
+
+ - In Step 5, we click on the **! Data Generator**. This will open **! Data Generator** overlay.
+ 
+
+
+ - On the **! Data Generator** overlay, select **Type**, **Function Type**, **Function**, **Enter Regex**, **Runtime Variable**, **Timeout** and click on **Save**. Here, we add regex [0 - 9]+, which extracts the first encountered series of numbers. The extracted data, which is OTP, will be stored in the runtime variable. For more information on examples of regex, refer to https://regex101.com/.
+ 
+
+ - This will help fetch OTP and enter it in the input element.
+ 
+
+3. Click on **Run** to execute the test case.
+
+
---
diff --git a/src/pages/docs/test-data/types/phone-number.md b/src/pages/docs/test-data/types/phone-number.md
index ef5a3aff..fee51809 100644
--- a/src/pages/docs/test-data/types/phone-number.md
+++ b/src/pages/docs/test-data/types/phone-number.md
@@ -18,6 +18,9 @@ contextual_links:
- type: link
name: "Using Phone Number Type Test Data"
url: "#using-phone-number-type-test-data"
+- type: link
+ name: "Set Up and Use Message Forwarding"
+ url: "#set-up-and-use-message-forwarding"
---
---
@@ -63,4 +66,77 @@ We will use the test data generators available in Testsigma to fetch the OTP fro
We have successfully created a test case for 2FA authentication.
+---
+
+
+## **Set Up and Use Message Forwarding**
+
+Providing phone numbers for OTP and login purposes is restricted in certain countries. In this case, you can use Testsigma SMS forwarder app that sends SMS messages to a designated mailbox, and you retrieve the OTPs from the mailbox. This section discusses how to set up the Testsigma SMS forwarder app and perform OTP verifications using this app.
+
+---
+
+## **Prerequisites**
+
+- You should have Testsigma SMS Forwarder application.
+
+
+---
+
+### **Install the App & Setup the Account**
+
+1. Install the app on a device.
+
+2. Click on the icon in the top-left corner to access settings.
+
+3. Sign in to the app.
+
+4. If you're using Google accounts, select the Gmail API.
+
+
+### **Filter Set-up**
+
+1. Tap on **Filters** and click the plus icon.
+
+2. On the **Set up recipients** screen, click the plus icon.
+
+3. On **Add** overlay, tap on Enter Phone Number.
+
+4. Enter the **phone number** to which you want to forward messages.
+
+
+[[info | **NOTE**:]]
+| Alternatively, you can enter the automation email ID to forward messages to an email address.
+
+5. Swipe left to access the **Forwarding conditions** screen. Here, set the forwarding rule. You can specify rules for messages from a specific number or messages containing specific text.
+
+6. Swipe left to access **Change the content** screen. Here, you can add the phone number of the initial sender of the message and specific words of your choice.
+
+7. Swipe left to access the **More Settings** screen. Here, you can change the filter name and enable options for notifications and results.
+
+8. On completing all the steps, click **Save**.
+
+Here's a GIF demonstrating how to install, add phone numbers, and set up filters for message forwarding.
+
+
+
+---
+
+
+## **Use Case for Message Forwarding**
+
+1. Navigate to the URL
+
+2. Click on Login or Sign Up
+
+3. Enter phone number in the phone number input field
+
+4. Wait for 30 Seconds
+
+5. Use Data Generator to Fetch OTP
+
+6. Submit OTP
+
+Here's a quick GIF demonstrating how to create test case after setting up sms forwarder app.
+
+
---
\ No newline at end of file
diff --git a/src/pages/docs/troubleshooting/agent/mobile-device-not-displayed-recorder.md b/src/pages/docs/troubleshooting/agent/mobile-device-not-displayed-recorder.md
index f7b2abad..dc9de8d9 100644
--- a/src/pages/docs/troubleshooting/agent/mobile-device-not-displayed-recorder.md
+++ b/src/pages/docs/troubleshooting/agent/mobile-device-not-displayed-recorder.md
@@ -1,120 +1,121 @@
---
-title: "Testsigma Agent not detecting local devices for mobile test recorder"
-page_title: " Troubleshooting “Testsigma Agent not detecting Local Devices for Mobile Test Recorder” error"
+title: "Testsigma Agent's Failure to Detect Local Devices for Mobile Test Recorder"
+page_title: "Resolve Mobile Test Recorder Issue Device Detection Failures"
metadesc: "Know the possible reasons why Testsigma Agent not detecting Local Devices for Mobile Test Recorder and learn steps to fix the issue by troubleshooting"
noindex: false
order: 23.2
-page_id: "Testsigma Agent not detecting Local Devices for Mobile Test Recorder"
+page_id: "troubleshoot-testsigma-agent-mobile-test-recorder-page"
warning: false
contextual_links:
- type: section
name: "Contents"
- type: link
- name: "Causes"
- url: "#Causes"
+ name: "Common Causes"
+ url: "#common-causes"
- type: link
- name: "Android device"
- url: "#Android-device"
+ name: "Android Device"
+ url: "#android-device"
- type: link
- name: "ADB does not recognize the device connected to the system"
+ name: "ADB does not Recognize the Device Connected to the System"
url: "#adb-does-not-recognize-the-device-connected-to-the-system"
- type: link
- name: "iOS device"
- url: "#iOS-device"
+ name: "iOS Device"
+ url: "#ios-device"
---
---
-
-This article provides methods to solve the error Testsigma agent not detecting local devices for mobile test recorder for Android and iOS devices.
-
-## **General causes**
+This guide offers solutions to the issue of Testsigma Agent not detecting local devices for the mobile test recorder on Android and iOS devices. Below, it provides potential causes and steps to resolve them.
-Testsigma agent may be unable to detect your local mobile device for the test recorder for the following reasons:
-
+---
-- Testsigma Agent is not up-to-date: Testsigma Agent includes an automatic update feature. However, if the auto-update fails due to bad network conditions or incorrect configuration, you can update the Agent manually. For more information refer to,
-updating Testsigma agent manually.
-
+## **Common causes**
-- Damaged or faulty USB ports or cables: In this case, you should try connecting to a different the USB port or use a different cable.
-- A weak Wi-Fi signal, if your device is connected via Wi-Fi.
+Testsigma agent may be unable to detect your local mobile device for the test recorder for the following reasons:
+
+- Testsigma Agent is not up-to-date: Ensure you keep Testsigma Agent up-to-date. The Agent's automatic update may fail due to network issues or incorrect configurations. Refer to the guide on updating Testsigma Agent manually to update Agent manually.
+- Damaged or faulty USB ports or cables: Try connecting to a different USB port or using an alternative cable if your current one is damaged.
+- Weak Wi-Fi Signal: If you have connected your device wirelessly, ensure a stable Wi-Fi connection.
---
-## **Android device**
+## **Android Device**
+
+### **Common Causes for Android Devices**
-**Causes**
-- Developer options and USB debugging are disabled: To enable developer options and USB debugging, refer to setting up local Android device.
+
- Disabled Developer Options and USB Debugging: Follow the steps to set up a local Android device to enable Developer Options and USB debugging.
+- Android Debug Bridge (ADB) Recognition Failure: Verify the ADB recognition by following the steps below if ADB does not recognize the device connected to the system .
+- Desired Capabilities Not Modified: Use the guide on desired capabilities to modify desired capabilities according to your device or application.
+- Driver installation error: If you encounter a Failed to install drivers message, follow these steps:
+
+ - Allow time for the driver installation to finish.
+ - Check device memory for sufficient space.
+ - Uninstall AppiumSettings and UI Automator Server apps, then restart the agent.
+
-- Android Debug Bridge (ADB) fails to recognize the device connected to the system: To verify if ADB recognizes your device, refer to the section below (ADB does not recognize the device connected to the system).
-- Desired capabilities are not modified as per device or application. To modify desired capabilities, refer to desired capabilities and a list of desired capabilities.
-- Driver installation error: Testsigma agent installs AppiumSettings and UIAutomator Server apps to aid running executions on Android devices. If this fails, a notification is displayed reading Failed to install drivers. In such instances, ensure your device remains connected for some time to finish installing drivers.
-## **Android Debug Bridge does not recognize the device connected to the system**
+---
+
+## **ADB does not Recognize the Device Connected to the System**
-To verify if the ADB interface does not recognize your Android device, follow the below steps:
+If Android Debug Bridge (ADB) fails to recognize your connected Android device, you should follow these steps to troubleshoot the problem.
-* Navigate to the folder containing ADB and open the command prompt. From the command line, type adb devices.If connected, you will see the list of devices attached. If the device is connected successfully, the response would be as shown in the figure below:
+### **Verification Steps**:
- where `AVY9KA90322022030`is the device ID.
+1. Navigate to the folder containing ADB.
+2. Open the command prompt and type **adb devices**.
+3. If you connect, the command prompt will display a list of attached devices, as shown in the example below: 
+ Here, **AVY9KA90322022030** is the device ID.
-* If your device is not displayed in the response, it indicates a hardware or communication problem between Android and your PC. Follow the below steps to troubleshoot the issue.
+### **If Your Device Is Not Displayed**:
+If the response does not display your device, it indicates a hardware or communication problem between Android and your PC. Follow the steps below to troubleshoot the issue.
[[info | NOTE:]]
-|We need to make sure that the Android SDK is installed in the system and its environment path is set, before running the ADB command.
+| Ensure you have installed the Android SDK on your system and set its environment path before running the ADB command.
-### **How to troubleshoot**
-
-- Restart your Android device.
-- If restarting does not resolve the issue, then try the following:
-
- - On your device, turn off USB debugging and then turn it back on again.
- - Plug the USB cable into a different USB port on your computer.
- - Unplug or replug the USB cable from your Android device. Ensure that the USB cable fits tightly into your Android device’s USB port, then try syncing again.
- - Try replacing the USB cable with one that fits more tightly into your Android device's USB port.
-
-
+### **Troubleshooting Android Device**
+
+1. **Restart Your Android Device**: Begin by restarting your Android device.
+2. **Turn Off and On USB Debugging**: On your device, turn off USB debugging and then re-enable it.
+3. **Change USB Port**: Plug the USB cable into a different USB port on your computer.
+4. **Unplug and Replug USB Cable**: Disconnect and reconnect the USB cable from your Android device, ensuring it fits securely into the device's USB port. Then, attempt syncing again.
+5. **Replace USB Cable**: Try using a different USB cable that fits more securely into your Android device's USB port.
---
-## **iOS device**
+## **iOS Device**
+
+Refer to the following information to troubleshoot and resolve common issues if you encounter problems with your iOS device.
-###**Causes**
+### **Common Causes for iOS Devices**
-- Device locked: iOS devices require the device to be unlocked to allow Testsigma Agent to mount developer image and run apps on the device.
-If the device is locked, a notification is displayed reading 'Unlock device'.
-- Computer not trusted: iOS devices require the connected computer running Testsigma Agent to be Trusted. This is required to mount developer image and run apps on the device.To Trust your computer,select your device in Finder and click Trust.
-- Developer image could not be mounted: iOS devices require developer disk image to be mounted to allow Testsigma Agent run apps on the device. Ensure provisioning profile is added on Settings > iOS Settings page.
-If profile is not configured, a notification reading 'Ensure profile exists in iOS Settings' is displayed.
+- Device locked: You must unlock iOS devices to enable Testsigma Agent to mount the developer image and run apps. A notification displaying 'Unlock device' is shown if the device is locked. If the device is locked, a notification reads 'Unlock device'.
+- Computer not trusted: You must trust the connected iOS device to ensure that Testsigma Agent functions correctly. To establish trust, select your device in Finder and click Trust'.
+- Developer Image Not Mounted: Testsigma Agent requires mounting the developer disk image on iOS devices to run apps. You should ensure that the provisioning profile is added in Settings > iOS Settings. A notification indicating a configuration issue says, 'Ensure profile exists in iOS Settings'.
-For iOS devices follow the below steps to resolve the issue.
+### **Troubleshooting iOS Device**
-### **How to troubleshoot**
+Troubleshoot and resolve issues with iOS devices by following these steps.
-- Turn off the iOS device.
-- Turn off the Testsigma agent.
-- Open Task Manager on your computer, and terminate the following applications or processes:
-
-- NodeJS
-- tidevice
-
-- Delete Testsigma agent logs. For more information on locating agent logs, refer to fetching agent test logs.
-
-- Restart the Testsigma agent.
-- Restart the iOS device and connect it to your computer.
-- If the iOS device does not appear on the list of connected devices, connect the device with a different USB port on your computer.
+- Turn Off iOS Device: Begin by turning off your iOS device.
+- Turn Off Testsigma Agent: Turn off Testsigma Agent.
+- Terminate Applications or Processes: Open Task Manager on your computer and terminate the following applications or processes NodeJS, tidevice.
+- Delete Testsigma Agent Logs: Locate and delete Testsigma Agent logs. For more information, refer to fetching agent test logs.
+- Restart Testsigma Agent: Restart the Testsigma agent.
+- Restart iOS Device and Connect: Reboot your iOS device and connect it to your computer.
+- Change USB Port: If the iOS device does not appear on the list of connected devices, connect the device with a different USB port on your computer.
-If the above troubleshooting steps did not help and the issue persists, [connect with Testsigma Support on Discord](https://discord.com/invite/5caWS7R6QX) or reach out to s [support@testsigma.com](mailto:support@testsigma.com).
+[[info | NOTE:]]
+| If the troubleshooting steps above do not resolve the problem, you can contact **Testsigma Support** on [Discord](https://discord.com/invite/5caWS7R6QX) or [support@testsigma.com](mailto:support@testsigma.com). You can also use the **Instant Chat** Options for prompt assistance.
---
\ No newline at end of file
diff --git a/src/pages/docs/troubleshooting/mobile-apps/click-tap-failure.md b/src/pages/docs/troubleshooting/mobile-apps/click-tap-failure.md
new file mode 100644
index 00000000..c1e0b13b
--- /dev/null
+++ b/src/pages/docs/troubleshooting/mobile-apps/click-tap-failure.md
@@ -0,0 +1,64 @@
+---
+title: "Most Common causes for Click/Tap NLP failure"
+metadesc: "Understand the functionality of click or tap NLP while creating a test step inside a test case & learn most common causes for Click/Tap NLP failure"
+noindex: false
+order: 23.91
+page_id: Common causes for Click/Tap NLP failure
+warning: false
+contextual_links:
+- type: section
+ name: "Contents"
+- type: link
+ name: "Click or Tap Action Checkpoints"
+ url: "#click-or-tap-action-checkpoints"
+- type: link
+ name: "Troubleshooting/Debugging"
+ url: "#troubleshootingdebugging"
+---
+
+---
+
+
+Click/ Tap is one of the most used NLP in our product and it has been observed that many first time users often get an error message while using this NLP initially. So, this article will help you understand the functionality of click/tap NLP while creating a test step inside a test case.
+
+
+---
+
+## **Click or Tap Action Checkpoints**
+
+Generally, when we use click/Tap functionality in Testsigma while clicking or tapping on any element with suitable UI Identifier we make sure of these following things:
+
+**1. The element is 'enabled'**
+In case the element is disabled, it will throw an error message "Element is either hidden or disabled". So, before we click on any element, we need to make sure that it is enabled.
+
+
+**2. The element is 'visible'**
+Our second criteria is to make sure that the element that you are trying to click is visible/not hidden. In case it is not visible, it will throw the same error message mentioned above.
+It is possible that the element that you are trying to click is present below the scroll view. So for that, we are internally using the Scroll functionality to find the element that you want to click.
+
+**3. Correct Xpath**
+Our third criterion is to ensure the element is being clicked or tapped by providing the correct Xpath. You can use our Chrome Extension for getting the Xpath for UI Identifier or you can write Xpath manually.
+
+---
+
+## **Troubleshooting/Debugging**
+
+**Appium Inspector to debug Mobile Apps**
+In case any user wants to check whether the element is visible and enabled, they can use Appium Inspector to debug and inspect the element as shown below to check if the 'enabled' and 'visible' attributes are 'true'.
+
+
+
+The above image is for elements for which Tap NLP would probably fail since it doesn't satisfy the second condition.
+
+**Developer tools to inspect Web Apps**
+
+
+
+The above image is for elements for which Click NLP would probably fail since it doesn't satisfy the first condition.
+
+
+The **click/Tap** NLP will have a smooth run once these criteria are met.
+
+In case you have any problem regarding the Click/Tap NLP, please make sure that these criteria are being met.
+
+---
\ No newline at end of file
diff --git a/src/pages/docs/troubleshooting/setup/prerequisites-for-cloud-executions.md b/src/pages/docs/troubleshooting/setup/secured-business-application-support.md
similarity index 98%
rename from src/pages/docs/troubleshooting/setup/prerequisites-for-cloud-executions.md
rename to src/pages/docs/troubleshooting/setup/secured-business-application-support.md
index c1dd6bc9..20d5e3c7 100644
--- a/src/pages/docs/troubleshooting/setup/prerequisites-for-cloud-executions.md
+++ b/src/pages/docs/troubleshooting/setup/secured-business-application-support.md
@@ -3,7 +3,7 @@ title: "Secured Business Application Support"
metadesc: "In Testsigma, some prerequisites are necessary to avoid issues and enhance the flexibility. This article discusses prerequisites for cloud executions"
noindex: false
order: 23.2
-page_id: "Testsigma Sample Apps"
+page_id: "Secured Business Application Support"
warning: false
contextual_links:
- type: section
diff --git a/src/pages/docs/troubleshooting/setup/troubleshooting-restricted-access.md b/src/pages/docs/troubleshooting/setup/troubleshooting-restricted-access.md
new file mode 100644
index 00000000..ad9f2f7c
--- /dev/null
+++ b/src/pages/docs/troubleshooting/setup/troubleshooting-restricted-access.md
@@ -0,0 +1,41 @@
+---
+title: "Troubleshooting Restricted Access to Testsigma"
+metadesc: "This article discusses accessing the Testsigma application by whitelisting the necessary URLs, if you have network restrictions set by your administrator"
+noindex: false
+order: 23.3
+page_id: "Troubleshooting Restricted Access"
+warning: false
+contextual_links:
+- type: section
+ name: "Contents"
+- type: link
+ name: "Blocking Exceptions to Access Testsigma"
+ url: "#blocking-exceptions-to-access-testsigma"
+---
+
+---
+
+If you cannot access the Testsigma application due to network restrictions set by your administrator, you need to request whitelisting the necessary URLs required for Testsigma. This article discusses how to access Testsigma under restricted environments.
+
+---
+
+## **Blocking Exceptions to Access Testsigma**
+
+### **1. Application Access**
+
+- To access the application, ensure that the following domain is whitelisted:
+ - ``` *.testsigma.com ```
+- To automate secured business applications refer to [secured business application support](https://testsigma.com/docs/troubleshooting/setup/prerequisites-for-cloud-executions/).
+
+
+### **2. Customer Support Portals**
+
+- **Testsigma Chat Support**: Testsigma chat support services ensure seamless communication with the Testsigma support team. For support queries via live chat.
+
+- **Testsigma Help Desk**: Allows you to create tickets and check the status of ticket inquiries. If you have any problems using Testsigma application, you can raise a ticket through Testsigma Help Desk. The support team will address all your queries.
+
+**Domains to whitelist to access customer support portals**:
+- ``` *.freshchat.com```
+- ```*.freshdesk.com```
+
+---
\ No newline at end of file
diff --git a/src/pages/docs/troubleshooting/web-apps/issues-with-ui-Identifiers.md b/src/pages/docs/troubleshooting/web-apps/issues-with-ui-Identifiers.md
new file mode 100644
index 00000000..e7060a5c
--- /dev/null
+++ b/src/pages/docs/troubleshooting/web-apps/issues-with-ui-Identifiers.md
@@ -0,0 +1,175 @@
+---
+title: "Most Common Issues Caused When Using UI Identifiers"
+metadesc: "When locating an element we need to make sure that the attribute value is unique. This article discusses most common issues caused when using UI identifiers"
+noindex: false
+order: 23.5
+page_id: "Most Common Issues Caused When Using UI Identifiers"
+warning: false
+contextual_links:
+- type: section
+ name: "Contents"
+- type: link
+ name: "Element Not Found"
+ url: "#element-not-found"
+- type: link
+ name: "Duplicate UI Identifiers"
+ url: "#duplicate-ui-identifiers"
+- type: link
+ name: "Hidden or Disabled Elements"
+ url: "#hidden-or-disabled-elements"
+- type: link
+ name: "Incorrect or Invalid UI Identifiers"
+ url: "#incorrect-or-invalid-ui-identifiers"
+- type: link
+ name: "Empty UI Identifiers"
+ url: "#empty-ui-identifiers"
+- type: link
+ name: "Element not Clickable or Interactable"
+ url: "#element-not-clickable-or-interactable"
+- type: link
+ name: "Stale Element Exception"
+ url: "#stale-element-exception"
+---
+
+---
+
+When locating a Web Element using any of its attributes (id, title, name, type, placeholder, class, text e.t.c), we need to make sure that the attribute value is unique. For example, if there are two buttons with the name 'submit' on the same page, we cannot use that attribute. In cases where no other unique Identifiers are present, we will make use of Xpath locators or CSS locators. However, there can be a number of issues when using UI Identifiers for your Test Steps.
+
+---
+
+## **Element Not Found**
+
+
+
+There can be mainly three reasons for the error:
+
+**1. Element not present in current page**
+**Cause:** The Element is not present on the current page. One of the previous steps might have passed but not run as expected.
+**Solution:** Check the screenshot of the previous steps to know where it failed and correct the Step there. Please feel free to contact Support on chat if you need more help.
+
+**2. UI Identifier value is incorrect**
+**Cause:** The UI Identifier might be incorrect and therefore Testsigma is not able to find an Element with the given UI Identifier. The above-given image is an example of this error. You can see there is a typo in the UI Identifier (xpath value) in this case.
+**Solution:** Check and correct the UI Identifier value or use Testsigma Recorder. If the element was recorded using Testsigma Recorder, please feel free to contact the Support on chat to report the issue.
+
+**3. Element is located in an external frame**
+**Cause:** The Element is inside an Internal Frame rather than the Body of the HTML Document.
+**Solution:** You need to switch to the Frame first where the element is located before interacting with the element using **Click** or **Type** Statements. You can use any of the following Grammar:
+- Switch to the frame UI identifier
+- Switch to the frame by index test data
+- Switch to the frame with name test data
+
+---
+
+## **Duplicate UI Identifiers**
+
+In this case, the Test Step might not actually fail. The Test Step will pass and the execution will continue although the correct Element was not selected. This is undesirable.
+
+
+
+**Cause:** As you can see above, we used the xpath //input[@type='password'] and there are two matching Elements as shown in the image for the same xpath. This is a case of duplicate UI Identifiers and even if we need to select the second field, the first Element with the corresponding UI Identifier will always be selected.
+**Solution:** Use a different XPath that is unique for the element.
+
+---
+
+## **Hidden or Disabled Elements**
+
+Element is either hidden or disabled exception
+
+
+
+**1. Dynamic Elements not available at runtime**
+**Cause:** Sometimes, the element might be created dynamically and might not be present in the Web page at that instant.
+Solution: Wait for the element to be present by adding a wait step.
+
+
+
+**2. Disabled or hidden Element**
+**Cause:** The given UI Identifier is hidden or disabled. Elements are sometimes hidden or disabled by the developer if they are not meant to be interacted with.
+
+
+
+In the above image, you can see the type='hidden' for these input elements. An element may be hidden also using class names such as 'hide', 'hidden' or attributes(angular directives) such as 'ng-hide'.
+
+**Solution:** If the element is hidden, the developer doesn't want the user to interact with it. Find another element that can be interacted upon.
+
+---
+
+## **Incorrect or Invalid UI Identifiers**
+
+The element corresponding to the locator type "id_value" and locator "//*[@id='lgnjs']" is not displayed.
+
+
+
+**1. Mismatch between UI Identifier type and UI Identifier value**
+
+**Cause:** Check the selected locator type corresponds to locator value. Locator type is 'id' but the given locator value is in 'xpath' format.
+**Solution:** Correct the locator value corresponding to the locator type.
+
+
+
+**2. Element is not displayed in page**
+
+**Cause:** We can rule out the mismatch of Locator Type and Locator value in the above message.
+
+**Solution:** Check whether the element is actually displayed in the present page.
+
+---
+
+## **Empty UI Identifiers**
+
+Empty locator value provided for the locator type "id_value".
+
+
+
+
+**Cause:** No value provided for the UI Identifier.
+
+**Solution:** Check the value of the UI Identifier and make sure that ui identifier value is not be empty.
+
+---
+
+## **Element not Clickable or Interactable**
+
+Element not clickable at point (x,y). Other element would receive the click:
+
+
+
+**1. Another Element overlapping temporarily**
+Cause: The Element is covered or overlapped by another element temporarily(during a page load).
+
+Solution: Add a wait step for the overlapping element to go away itself. The overlapping element will disappear automatically once the page loads completely.
+
+
+
+**2. Another Element overlapping until user acts upon it**
+**Cause:** The Element is covered or overlapped by another element that needs to be closed/removed (like sticky menus, drop down menus or alerts).
+**Solution:** Add a Step to close/remove the overlapping Element. For Ad or Survey popups, there would be a close button which can be clicked to close the popup.
+
+
+
+**3. Element out of page view**
+**Cause:** The Element is not visible in the current Browser Window view. Check whether the Element is actually visible in the Test Step Screenshot(inside the Browser view port).
+**Solution:** If the Element is not inside the view, add a Test Step to scroll to the Element.
+
+---
+
+## **Stale Element Exception**
+
+The element corresponding to the locator type "X" and locator "Y" cannot be interacted with since it is no longer appears/exists on the DOM of the page.
+
+**1. The element is no longer attached to the DOM**
+
+**Cause:** The element you are trying to interact with might be a dynamically rendered element that detaches/reattaches itself to the DOM/ HTML Source dynamically after the page load is complete. This is the most common cause.
+
+**Solution 1:** Add a wait step so as to allow time for the element to be added to the DOM using the **Wait for test data seconds** template.
+**Solution 2:** Add a Page Refresh step so that the element is loaded quickly on next reload.
+
+
+**2. The element has been removed from the DOM**
+
+**Cause:** The element has been deleted entirely.
+
+**Solution:** Get the UI Identifier for the element once again.
+
+
+---
\ No newline at end of file