Replies: 3 comments 3 replies
-
Hi there, from what I have gathered it should indeed not spawn that many workers as this should have been tackled in this PR #4531 from what I can tell. Seems like this could be a bug. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Should I report as a bug? |
Beta Was this translation helpful? Give feedback.
2 replies
-
Any updates on this? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there, how are you guys doing. Been using your framework for a number of years.
So the issue I am having is what I thought would have been addressed in this article, unless I am not understanding the difference between workers and sessions: https://webdriver.io/blog/2019/11/01/spec-filtering/. It states that sessions will automatically be filtered by cucumber tags.
In our wdio config, we have
There are only two tests with @runOnlyThis, but it is creating 276 workers according to the console log. That would be the number of features we have in total, it is not filtering the number of workers by the cucumber tags.
After about 25 minutes or it will eventually start, I think after it tries to start that many workers.
The only alternative we found to only run worker for the 2 tests was adding an extra outer array in the specs value:
but then we are getting a cucumber html report that doesn't separate the tests by feature file. @runThisOnly
Anyway, is the framework working as expected, or is this a webdriver io issue?
Beta Was this translation helpful? Give feedback.
All reactions