mockk
Suggestion: Recommendations for running parallel tests
I think it would be useful to add a section about running mock with parallel test execution.
I understand now that clearAllMocks is not compatible with parallel tests as it will clear mocks across tests but I was confused about the behavior for a couple of days.
I am using mockk<> coEvery and coVerify with no issues. But if some areas of mockk are not threadSafe or not recommended for parallel test execution that could also be discussed in the parallel execution section.
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. If you are sure that this issue is important and should not be marked as stale just ask to put an important label.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
I'm interested in this as well. We want to have fast tests, so we need to run in parallel. We've been creating classes just to wrap functions for the sake of mocking. IMO, we should be using top level functions, but the inability to use mockkStatic in parallel is preventing us from doing so.
If there's a (future) paradigm where we can run these tests in parallel, I can convince my team on giving up parallel tests for now so we can use all the language features. Otherwise, we're having to give up functionality because of testing, which seems like a huge loss.
Probably mockkConstructor is affected as well. I was just investigating an issue with some flakyness when running tests in our CI environment when I noticed this issue. After disabling parallel execution, the test suite went back to green.
Experiencing a similar issue with clearAllMocks, where my mocks are being cleared mid-execution of some other suites running in parallel. :(
This is known and I guess just accepted behavior https://github.com/mockk/mockk/issues/301#issuecomment-492512079
Leads to some wicked bugs, when not expected.
Should there not be a static mock scope, where we define the mock'ed static method/object/etc to only exist withtin a scope. Doing mockkObject and then unmock feels like a old way of doing things in the Kotlin reality of scopes/blocks/lambdas.
