-
Notifications
You must be signed in to change notification settings - Fork 11
Tests ran in parallel clash with each other #77
Comments
Hello @oryz, thanks for your question. Before I dive into this, can you please confirm that this is an issue with the plugin and not one of the restrictions of SpecFlow itself? This document describes how SpecFlow handles parallel execution: https://github.com/SpecFlowOSS/SpecFlow/blob/master/docs/Execution/Parallel-Execution.md Also I know of this SpecFlow issue: SpecFlowOSS/SpecFlow#2225 Again, I'm most happy to dive into your issue but I am aware of SpecFlow itself having problems with parallel execution so that's why I'd like to confirm it. Hope you understand! |
Hi Mark and thanks for the response. I understand the concern you raise, to be completely clear we have a mature solution in which we could run tests in parallel successfully before adding this plug in (due to a refactor we needed a better dependency injection framework than the SpecFlow built in one). So the issue is definitely not with SpecFlow itself. Could you first confirm that we should be able to run tests in parallel? |
Ok understood. Marked this as a bug and will investigate. @oryx Sorry for bothering you, but would it be possible to provide an example of what type of parallel tests fail? |
Not sure what we've done or changed but it's all working good now so closing this issue. |
Hi there,
We've been playing around with this SpecFlow plugin, and got it to work for us except for one issue: we don't seem to be able to run tests in parallel.
For example, the ScenarioContext gets shared between different scenarios that execute at the same time. Another example is that we'd get a clash in the [ScenarioDependencies] method if we don't put a lock in it.
Is the reason for this related to the limitations described in PR #74?
The text was updated successfully, but these errors were encountered: