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: packages/selenium-side-runner/README.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,3 +49,14 @@ Running tests faster through the use of multiple workers
49
49
The runner will automatically set the number of workers to the amount of cores available, for most cases this is the best result.
50
50
**Note:** unless you specified that a suite is parallel, it will still run the contained tests sequentially, though the runner will run suites in parallel by default.
51
51
To mark a suite's tests as parallel, set that in the suite's settings in the IDE.
52
+
53
+
### FAQ
54
+
55
+
#### I'm getting an error similar to `Unknown locator ${vars.something}`
56
+
When running your projects make sure that the command is aware of the locator strategy **before** variables are evaluated.
57
+
For example `click | id=${myButton}` vs `click | ${idOfMyButton}`.
58
+
Always use the first one, since the strategy is hardcoded in the command, the second would yield an error.
59
+
60
+
>But it works in the IDE.
61
+
62
+
That is because the IDE calculates locator strategies differently than the runner, it is a known current issue.
0 commit comments