-
Notifications
You must be signed in to change notification settings - Fork 54
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
CollectionPerMethod support | parallel test execution #92
Comments
Feel free to raise a PR! |
I has release 8.9.0, please verify that your problem has been resolved. |
When I enable ParallelizationMode I do see the tests are being run in parallel however they only finish when all tests have finished executing. This is a problem for me because iam running a api test with a database behind it. I pool the databases so the tests have to spend less time on running migrations. After a test is finished the database is cleaned and returned to the pool. However since the tests never finish before all tests have finished running the database is never returned to the pool. To give a example of the current faulty behavior lets say I have 100 tests and I run 20 tests in parallel this is what happens: In the above example 100 databases are created. I would expect more something like this: In the above example only 20 databases are created because of pooling. |
Upgrade Xunit.DependencyInjection to 9.3.0, xunit to 2.8.0 |
I was trying to use solution from https://www.meziantou.net/parallelize-test-cases-execution-in-xunit.htm which allow to run tests inside class in parallel.
It works fine with default XUnitTestFramework, but doesn't work with xunit.DependencyInjection with errors like
'The following constructor parameters did not have matching fixture data: ITest test
Exception doesn't have a stacktrace'
The above solution is to create unique collection for each test method, but it doesn't compatible with method RunTestCases in DependencyInjectionTestFrameworkExecutor
Here we group tests by classes, not by collections.
If I remove this grouping just by ommiting TestClassComparer.Instance everything will works fine.
Why we need to group tests by class?
The text was updated successfully, but these errors were encountered: