+## **Configuring Test Data Profile in Test Case** +1. In Test Case details page, click **Test Case Settings** in the right-side navbar. +2. Choose the associated **Test Data Profile**. +3. Enable the **Data-Driven** toggle and select **Filter Type**, **Comparison Metric**, and **Data Iteration**.  --- -##**Run Results** -Once the Test Case is updated with the dynamic Element as given above, we can execute the Tests. Please follow this article to know more about executing Tests -
+Dynamic locators are essential in handling web elements that may undergo attribute changes during test execution. Traditional locators like XPath or CSS selectors may lose reliability when these dynamic changes occur. Testsigma offers a solution that enables you to create dynamic locators at runtime, guaranteeing the stability and dependability of your automated tests. This documentation guides you through utilising dynamic locators in Testsigma by storing elements into Runtime Variables. --- -## **Case Study - OrangeHRM** -Here, we will be using a popular application such as OrangeHRM for our demonstration. We will be doing the following steps on the OrangeHRM website: -1. **Navigate to the OrangeHRM website**
-2. **Enter the username**
-3. **Enter the password**
-4. **Store the username to a run-time variable (for reuse in dynamic Element)**
-5. **Click on the login button**
-6. **Verify that an element with the text 'Welcome ' followed by the stored user name is displayed on the page**
+## **Prerequisites** -
+Before implementing dynamic locators using Runtime in Testsigma, ensure you have a solid understanding of key concepts such as creating a [Test Case](https://testsigma.com/docs/test-cases/manage/add-edit-delete/#creating-a-test-case), managing [Runtime Test Data](https://testsigma.com/docs/test-data/types/runtime/) and [Elements](https://testsigma.com/docs/elements/web-apps/capture-single-element/), handling [Test Steps](https://testsigma.com/docs/test-cases/step-types/natural-language/), and effectively utilising different [Test Data Types](https://testsigma.com/docs/test-data/types/overview/). --- -## **Actual Steps - Implementation** -1. **Navigate to https://opensource-demo.orangehrmlive.com**
-This step is self-explanatory. Navigate to the OrangeHRM website using grammar Navigate to test data. -2. **Enter Admin in Username field**
-Enter the user name in the Username field using grammar Type test data in the Element field. -We can create the step with a dummy Element named Username and later update the Element value for the field. +## **Store Element into Runtime Variable** -3. **Enter admin123 in Password field**
-Enter the password in the Password field using grammar Type test data in the Element field. -This step is similar to the above step. You just need to modify the test data and Element. +We will manually create an element and store it in a Runtime Variable to create dynamic locators. This is important because recording dynamic elements may not be reliable. -4. **Store the value displayed in the text box Username field into a variable user_name**
-Store the user name from the Username field to a run-time variable named 'user_name' using the grammar Store the value displayed in the text box Element field into a variable test data. - [[info | NOTE:]] - |In this case, the value 'Admin' from the 'Username' field is stored inside the run-time variable 'user_name' +1. Create a **new step** in your **Test Case** using **NLP**. Use placeholders for **elements** and **test data** to create an element and store it as a Runtime Variable.  -5. **Click on login_button**
-Click on the Login button using the grammar Click on Element. This step is similar to the 2nd and 3rd steps. You just need to modify the Element since there's no test data for this step. + [[info | Example:]] + | Use NLP "Store text from the **element** into a variable **test data**". The NLP helps you store text from an element identified into a variable. -6. **Verify that the current page displays an element welcome_ username_ link**
-Verify that an element(welcome_ username_ link) with dynamic XPath containing the stored run_ time parameter 'user_ name' is present using the grammar Verify that the current page displays an element Element. +2. Click on the element, then select **Create Element** from the dropdown list. The Create Element overlay screen will appear on the right side of the page. Manually enter the **Element Name**, **Screen Name**, **Element Type**, and **Element Value**. Finally, click **Create Element** to complete the element creation.  - +3. Substitute specific **text** for the **test data** placeholder and click **Create Step** to save the test step, storing the element within the text as a Runtime Variable.  -
+ [[info | Example:]] + | - We are using the **Simply Travel Flight** website as an example. If we want to locate the **Login or Sign Up** button and its XPath is **(//\*[@id="login-signup"]/div)**, we can store its value in a runtime variable **($|login|)**. + | - When we run the test, we can use this variable to locate the button. If the value changes later, we can update it without affecting the test. This method works even if the button is used in different test steps and its value changes. --- -## **Creating Dynamic Elements using run-time test data** -In step #6, we are verifying that the page displays an Element 'welcome_ username_ link' containing text 'Welcome Admin'. Here, 'Admin' is the username that we got from the 'Username' field in step #4. - -The username of the currently logged-in user can be dynamic and so we need to create a dynamic XPath containing the current Username. - -For example,
-**//a[@id='welcome'][text()='Welcome Admin']** -We have already got the username of the currently logged-in user 'Admin' into the run-time parameter named 'user_name' in Step #4. We just need to use the same in the dynamic XPath. That can be done as given below: +## **Creating Dynamic Elements using Runtime Test Data** -**//a[@id='welcome'][text()='Welcome $|user_name|']** +1. Use **NLP** to create a **new step** in the **Test Case** and include a placeholder for the **element**.  -Now we can use the above XPath as the Element value of "welcome_ username_ link" and the $|user_ name| part will be translated to the value of runtime parameter 'user_ name' when the Test Step is executed. + [[info | Example:]] + | Utilise NLP "Click on **Element**" to click an element with a given UI Identifier. - +2. Click on the element, then select **Create Element** from the dropdown list. The Create Element overlay screen will appear on the right side of the page. Manually enter the **Element Name**, **Screen Name**, and **Element Type**. +3. Provide Dynamic Element Value **//*["$|login|"]/div**, where '**login**' is the stored Runtime Variable. Click **Create Element** to complete element creation.  + [[info | Example:]] + | During testing, accurately locate the actual 'Login or Sign Up' element on the Simply Travel Flight website with the dynamic XPath **//*["$|login|"]/div** using the Runtime Variable 'login'. -Here's a screenshot of the Test Case: - - -That’s all we need to create Dynamic Elements using Runtime Parameter Test Data. - -Once the Test Case is updated with the dynamic Element as given above, we can execute the Tests. You may also perform a dry run by clicking on the Run button on the Test Case details page. - +--- +## **Implementing Dynamic Locators using Runtime** +With the Runtime Variable in place, follow these steps to implement dynamic locators in your test cases: +1. Add a new step in the test case where interaction with the dynamic element is required. +2. Manually select the dynamic element and proceed with your test steps. Testsigma will dynamically locate the element during test execution.  +--- diff --git a/src/pages/docs/test-cases/step-types/block.md b/src/pages/docs/test-cases/step-types/block.md index 485bba42..b7627b15 100644 --- a/src/pages/docs/test-cases/step-types/block.md +++ b/src/pages/docs/test-cases/step-types/block.md @@ -87,7 +87,6 @@ To delete a Step Block, open the test case containing it and click the **Delete* ## **Actions Possible on a Block** - **Reordering Steps**: Within a Step Block, you can change the order of steps. -- **Copying Block**: You can copy a Step Block and its contained steps and paste it into the same or another test case. - **Moving Block**: You can move a Step Block and its contained steps to a different location within the same test case. --- diff --git a/src/pages/docs/test-step-recorder/install-firefox-extension.md b/src/pages/docs/test-step-recorder/install-firefox-extension.md new file mode 100644 index 00000000..15b9e058 --- /dev/null +++ b/src/pages/docs/test-step-recorder/install-firefox-extension.md @@ -0,0 +1,59 @@ +--- +title: "Install Testsigma Recorder Extension in Firefox" +page_title: "Install Testsigma Recorder Extension in Firefox Easily" +metadesc: "Effortlessly start installing the Testsigma Recorder Extension in Firefox. Follow simple steps to record interactions for efficient testing. Learn more now." +noindex: false +order: 7.12 +page_id: "install-testsigma-recorder-in-firefox" +warning: false +contextual_links: +- type: section + name: "Contents" +- type: link + name: "Add Testsigma Recorder Extension to Firefox" + url: "#add-testsigma-recorder-extension-to-firefox" +- type: link + name: "Enable Access Permissions in Firefox" + url: "#enable-access-permissions-in-firefox" +--- + +--- + +Testsigma Recorder extensions in Firefox allow you to record end-to-end interactions with your web applications effortlessly. The extensions capture and store these interactions as actions in simple English sentences using predefined NLPs. + +--- + +## **Add Testsigma Recorder Extension to Firefox** + +1. Open your **Firefox** browser and navigate to [Testsigma Recorder](https://addons.mozilla.org/en-US/firefox/). +2. Click on **Add to Firefox**. +3. Click **Add** when prompted for permission. + +[[info | NOTE:]] +| Check the box that says **Allow this extension to run in Private Windows** to enable this extension to work in **Private Windows**. + +--- + +## **Enable Access Permissions in Firefox** + +After installing the extension, configure it as follows: + +### **Allow Extension to Access Data** + +1. Click the **Extension** icon in the top right corner. +2. Navigate to **Manage Your Extensions**. +3. In the **Testsigma Recorder** extension and click on the **Menu** icon, then select **Manage**. +4. Under **Testsigma Recorder** details, go to the **Permission** tab and toggle on **Access your data for all windows**  + +### **Privacy & Security Settings** + +1. Click the **Menu** icon and select **Settings**. +2. Go to **Privacy & Security** and choose **Custom** in **Extended Tracking Protection**. +3. In the **Custom settings**, select **Cookies from unvisited websites** from the dropdown next to Cookies. +4. Click **Reload All Tabs** to apply the changes in the browser.  + +[[info | NOTE:]] +| This enables Testsigma Recorder to access all websites within the browser to record interactions. + +--- + diff --git a/src/pages/docs/test-step-recorder/settings-include-exclude-attributes.md b/src/pages/docs/test-step-recorder/settings-include-exclude-attributes.md index 313fc639..82b170c1 100644 --- a/src/pages/docs/test-step-recorder/settings-include-exclude-attributes.md +++ b/src/pages/docs/test-step-recorder/settings-include-exclude-attributes.md @@ -2,7 +2,7 @@ title: "Exclude Attributes/Classes" metadesc: "Learn how to exclude certain attributes/classes while capturing elements from your website | Enhance skills with this doc to exclude certain attributes/classes." noindex: false -order: 7.12 +order: 7.13 page_id: "Exclude Attributes/Classes" warning: false contextual_links: 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 a92a7597..44a42317 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 @@ -50,7 +50,7 @@ Testsigma agent may be unable to detect your local mobile device for the test re
+
- Allow time for the driver installation to finish.
- Check device memory for sufficient space.