-
Notifications
You must be signed in to change notification settings - Fork 980
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
Random execution order of test cases (shuffle) #2
Comments
I like this idea a lot and would be happy to get a pull request with this goal accepted. |
I've implemented this "random execution order of test cases" feature on my fork and I'm going to submit this pull request very soon. |
Can your implementation be fed with a seed to reproduce a "randomized" Thanks much for contributing! This will definitely be a good addition to Cheers, On Tue, Mar 12, 2013 at 6:04 AM, pbhar notifications@github.com wrote:
|
…sert_catches fix no message assert catches
MISRA 2004 rule 19.10: inside macros, surround each parameter usage with parentheses. commit2/3
MISRA 2004 rule 19.10: inside macros, surround each parameter usage with parentheses. commit2/3
Hi folks, I stumbled upon this issue while trying to check whether Unity supports this shuffled random execution order of tests or not. This issue was closed as completed by @mvandervoord, but as far as I am aware, I do not think Unity supports this feature yet, and there are no corresponding relevant pull requests or commits linked to this issue that introduced this feature into Unity. Can I confirm whether this feature has been added to Unity or not? If yes, can I ask how to activate it (and perhaps add those steps to the docs)? If not, then I am willing to raise a PR to add this feature, including adding the aforementioned possibility of using a seed for deterministic reproduction. Thanks! |
This was previously supported in the test runner generator, but was long ago removed from it. I'd be interested in seeing this feature reintroduced in a clean way. :) |
Ah alright then.
Sure thing, I will work on this whenever I manage to get around to it. |
This is a very useful feature that I've come across in GoogleTest (using the --gtest-shuffle option). The main reason you'd want to shuffle tests is to expose any tests that depend on any other test in any way.
I can't use GoogleTest on the embedded target I am working on because it is too heavy weight. Would this be a difficult feature to add?
I'll try toying with an implementation on my fork and submit a pull request when it is ready.
Thanks.
The text was updated successfully, but these errors were encountered: