-
Notifications
You must be signed in to change notification settings - Fork 550
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
Fix order dependencies in unit tests #362
Comments
sferik
changed the title
Fix order dependencies in tests
Fix order dependencies in unit tests
Jan 23, 2015
Sounds good :) |
Closed
I've tried to track this down. It seems that it is related to global configuration settings. Some tests do things like
Not sure if that's the way to go, but it solves the problem. |
hugopeixoto
added a commit
to hugopeixoto/simplecov
that referenced
this issue
Mar 7, 2015
Some tests were changing global configuration settings without restoring them afterwards. Fixes simplecov-ruby#362
hugopeixoto
added a commit
to hugopeixoto/simplecov
that referenced
this issue
Mar 7, 2015
Some tests were changing global configuration settings without restoring them afterwards. Fixes simplecov-ruby#362
Merged and green, thanks a lot for tackling this @hugopeixoto |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After switching from Test::Unit to Minitest, I started noticing some intermittent build failures. These will typically self-correct by restarting the build. They seem to be caused by an order dependency.
Minitest will force the tests to run in alphabetical order if you add the flag
i_suck_and_my_tests_are_order_dependent!
but I think it would be better to just fix the order dependency. 😊There’s a project called minitest-bisect that should make it easier to track down random failures.
The text was updated successfully, but these errors were encountered: