-
Notifications
You must be signed in to change notification settings - Fork 768
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run tests from the same collection in parallel #1227
Comments
The entire purpose for test collections is shared state (the collection fixture). There is currently no way to override this, as it's a fundamental design decision. |
Are there any other suitable options? |
The only options here would involve extensive extensibility changes (unlikely that someone would stumble into the solution without help from one of us who knows the APIs very well). If another test framework already offers you the parallelization options you desire, that would be a lot less painful. |
To anyone who needs this. Here's a description of how to use NUnit 3 to have parallel test execution for a single data driven test method: https://dev.to/franndotexe/parallel-test-execution-within-the-context-of-mstestv2-nunit3-and-vstestconsole-3f39 |
It's my understanding that tests within the same collection cannot run in parallel. When you are running tests that share no state, for example, smoke tests or UI tests against an actual implementation, it's quite handy to be able to run them in parallel. Splitting tests into separate classes reduces cohesiveness and also introduces issues if you have one time setup for the fixture i.e using ICollectionFixture.
Is there a way to override the documented behaviour? Is it feasible to implement this?
The text was updated successfully, but these errors were encountered: