add support xpath in playground button #31241
Closed
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.
Using this code, we can see the xpath address for each element in the playground button. This can prevent possible bugs in finding the css element. Also, for this, we need to install the xpath plugin.
"cypress-xpath" plugin: "^2.0.1" added. To find xpath using playground, I remind you that after this change, you must find the elements with the get.xpath command.
According to my experiences using application testers, I found that finding elements using xpath is the best way to write tests. Also, if you don't use this feature like other testers, you will be left behind in the market. CSS is always changing and is not a good option for selecting elements. On the other hand, adding the xpath plugin alone is not enough to make testing easier because we have to manually find the xpaths and add them to the code. The best solution is to use the playground button.