-
Notifications
You must be signed in to change notification settings - Fork 37
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
Parallelize testing #64
Comments
I love this suggestion, @ZevEisenberg. I'm thinking there should be a spike to measure how much, if any, parallezing the tests improves performance. I have a concern that because I'm having a hard time conceptualizing the performance impacts of a concurrency model for Muter because of how much it depends on other executables which ultimately determine its runtime, and because concurrency is also hard. 😞 A spike of this feature suggestion could be as simple as parallezing the application of mutation operators and the execution of the test suite under test. These changes should be instrumented to prove there is an actual performance improvement. |
Muter should run tests in parallel to make the overall test run faster. Maybe we only do this if the testing scheme we are using has the "parallelize tests" option enabled, to make it opt-in. Care should be taken when collecting the results at the end to make sure it is done in a thread-safe way.
The text was updated successfully, but these errors were encountered: