-
Notifications
You must be signed in to change notification settings - Fork 34
Replaced GIFs with screenshots #816
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Santhosh-testsigma
wants to merge
2
commits into
dev
Choose a base branch
from
DOC-354-1
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -50,9 +50,16 @@ Dynamic locators are necessary for data-driven testing because they help adjust | |
| We are using the Simply Travel Flight website as an example and sorting the city names and the variable part of the element's ID attribute in the test data profile. | ||
|
|
||
| 1. Navigate to the website containing the elements you want to copy the **XPath**. | ||
| 2. **Right-click** on the desired and select **Inspect** to open **Chrome Developer Tools**. | ||
| 3. Use the **Select Element** icon to locate and inspect the element, then right-click the HTML tag and copy the **XPath**. | ||
| 4. We will use the Simply Travel Flight website as an example of the above test steps. Click **Select from Cities** and copy the **XPath** values for the cities.  | ||
|
|
||
| 2. We will use the Simply Travel Flight website as an example of the above test steps. Click **Select from Cities** and copy the **XPath** values for the cities. | ||
|  | ||
|
|
||
| 3. **Right-click** on the desired and select **Inspect** to open **Chrome Developer Tools**. | ||
|  | ||
|
|
||
| 4. Use the **Select Element** icon to locate and inspect the element, then right-click the HTML tag and copy the **XPath**. | ||
|  | ||
|
|
||
| 5. The table below explains how the city names and their corresponding XPath for an element. | ||
| <table> | ||
| <tr> | ||
|
|
@@ -78,37 +85,57 @@ We are using the Simply Travel Flight website as an example and sorting the city | |
| </table> | ||
|
|
||
| 6. In the provided XPath examples, the IDs of the cities have a common portion, **city-**, followed by a variable digit from **1** to **4**. We will parameterise this by storing the city and the variable portion using a Test Data profile. | ||
| 7. Navigate to **Test Data** > **Test Data Profile**. Click on **Create Test Data Profile**.  | ||
| 8. Below is the created Test Data profile for storing element ID attributes:  | ||
| 7. Navigate to **Test Data** > **Test Data Profile**. Click on **Create Test Data Profile**. | ||
|  | ||
|
|
||
| 8. Below is the created Test Data profile for storing element ID attributes: | ||
|  | ||
|
|
||
| --- | ||
|
|
||
| ## **Creating Dynamic Elements using Parameter** | ||
|
|
||
| 1. Use NLP to create a new step in the Test Case and include a placeholder for the element.  | ||
| 1. Use NLP to create a new step in the Test Case and include a placeholder for the element. | ||
|  | ||
|
|
||
| [[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. | ||
|  | ||
|
|
||
| 3. Manually enter the **Element Name**, **Screen Name**, and **Element Type** in the **Create Element** overlay screen. | ||
|  | ||
|
|
||
| 4. Provide the dynamic element value **//*[@id="@|cities|"]/div[2]/span[1]**, where **cities** is the parameter name containing dynamic data. | ||
| 5. Click **Create Element** to complete element creation and then **Create Step**.  | ||
|  | ||
|
|
||
| 5. Click **Create Element** to complete element creation and then **Create Step**. | ||
|  | ||
|
|
||
| --- | ||
|
|
||
| ## **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**.  | ||
|  | ||
|
|
||
| 3. Enable the **Data-Driven** toggle and select **Filter Type**, **Comparison Metric**, and **Data Iteration**. | ||
|  | ||
|
|
||
| --- | ||
|
|
||
| ## **Run Results for Dynamic Elements using Parameter** | ||
|
|
||
| 1. Once the test step created with the dynamic Element, execute the Test Case. | ||
| 2. Wait until the Test Case execution is completed. | ||
| 3. The Test Case will iterate as many times as there are **Test Data Sets (rows)** in the Test Data Profile, resulting in four iterations based on the provided example.  | ||
|  | ||
|
|
||
| --- | ||
| 2. Wait until the Test Case execution is completed. | ||
|
|
||
| 3. The Test Case will iterate as many times as there are **Test Data Sets (rows)** in the Test Data Profile, resulting in four iterations based on the provided example. | ||
|
Comment on lines
+137
to
+138
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Remove unnecessary indentation on blank line. Line 137 contains trailing whitespace. Clean it up for consistency. -2. Wait until the Test Case execution is completed.
-
+2. Wait until the Test Case execution is completed.
+
🤖 Prompt for AI Agents |
||
|  | ||
|
|
||
| --- | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clarify reference to prior steps.
Line 54 states "example of the above test steps" but no procedural steps precede this statement—only a general introduction. Revise for clarity.
📝 Committable suggestion
🤖 Prompt for AI Agents