You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guides/selectors.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,7 @@ The best and most simple selector will always be to use an element ID: `#some-id
52
52
53
53
We suggest the use of CSS selectors above XPath selectors when possible.
54
54
55
-
### Do and Do not
55
+
### Writing proper selectors
56
56
57
57
There are correct ways of writing selectors and incorrect ways. These suggestions will help you write better selectors.
58
58
@@ -90,7 +90,7 @@ The `*=` means `contains`. The selector is saying 'find an input whose name cont
90
90
91
91
Similarly here, this will match all elements which contains the class `.add`. This is brittle and susceptible to breaking when new elements/styles are added to the page.
92
92
93
-
#### Being too specific
93
+
#### Avoid being too specific
94
94
95
95
DO NOT make your selectors too specific either. If a selector is too specific, there is a high probability that it will break due to even minor changes to the application being tested.
0 commit comments