-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
Running tests in parallel #153
Comments
Maybe only slightly related, but I'd also love to easily be able to use kaocha for example. |
@mixedCase This should be solved by #196. Once that PR ready and merged, you could write your own custom test runner to @svdo There will be a custom koacha test runner that @imrekoszo is developing. Once the custom test runner support is there, you can plug it in. |
Awesome! 😎 |
With parallel execution support coming to kaocha and #196 coming to Polylith, this should be a possibility soon. |
Hi guys ! Now when it's possible to run tests using Kaocha in the latest 0.2.15-alpha release, can we close this issue? |
I believe so. Can't test myself as I don't find myself working in Clojure anymore but I think that does it. Closing. |
Is your feature request related to a problem? Please describe.
I'd like to parallelize the execution of most of my tests in order to speed up their execution.
To be more specific I've a series of tests that heavily bottleneck on IO not only during execution but also in their fixtures. While an asynchronous IO runtime on the Java-side would be best I don't think that's going to be viable for a few years at least, so having multiple threads to nanny the syscalls is the next best thing and the only alternative to projects who are actually bottlenecking on CPU instead.
Describe the solution you'd like
To be able to set metadata to specific
deftest
s as well asns
declarations (which should be equivalent to marking all of its deftests as parallel), to indicate that these tests can become part of a grand pool of tests that can be executed in parallel by a group of workers before the synchronized tests run.Nice to haves:
Describe alternatives you've considered
The text was updated successfully, but these errors were encountered: