Kotest couldn't run tests parallel
See original GitHub issueProbably this issue is related to #1257 . Current issue is with beta-3
jvm version.
Steps to reproduce:
- Create project with ~30 subprojects
- Add tests, etc.
- Run
gradlew build --parallel
Expected result: Tests from different projects are executed in parallel Tests from the same project are executed simultaneously
Actual result: Looks like, only one test could be executed at the same moment. E.g. event if tests are in different projects, they couldn’t be executed in parallel.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Run tests in single Spec in parallel ini kotest - Stack Overflow
I'm using kotest for my e2e API testing. All tests are independent and should have no problem running them in parallel. But with...
Read more >Changelog - Kotest
Fix issues running tests for native targets on Kotlin 1.7+ (#3107) ... Fix for bug in gradle which doesn't support parallel test events;...
Read more >Runs in AWS Device Farm
Device Farm runs tests in parallel as devices become available. ... with antipiracy measures, Device Farm cannot re-sign and run tests against the...
Read more >Testing - Spring
In this context, the term “test suite” means all tests run in the same JVM — for ... However, this does not mean...
Read more >Micronaut Test
io.micronaut.test.extensions.kotest.annotation.MicronautTest for Kotest. ... When you run a test within @MicronautTest it is running your real application.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I coulnd’t find correct way of reproducing.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.