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
Turn 0.9.3 causes all tests in suite to be run rather than only changed files #72
Comments
So it happens for 0.9.3 but not 0.8.3? I don't see how turn has anything to do with deciding what autotest runs. What is the command line autotest is invoking? |
I fire it up via 'bundle exec autotest'. The test case I sent you should exhibit the same behavior if you add a couple of more tests. I'll leave that repo thru the rest of the week. |
I looked at this some more, and really have no idea why it's including all files in the same directory and not just the changed file. As previously mentioned, I don't know how Turn can even effect this. So I need something more to go on. As for full stack trace. I am not seeing that. If $DEBUG is set to true it will dump a full trace instead of a filtered trace though. I am going to go ahead and release 0.9.3 and then we can go from there and see if we can track these issue down further. |
Same issue here |
Did some digging around, for me all 0.9.x version run all tests all the time. I ran the autotest in verbose mode and it clearly sees that only one files is changed, but for whatever reason it proceeds to run the whole suite. This is the command that autotest is invoking
|
Rails 3.2.1, turn 0.9.3 (from repo), rails-autotest 4.1.0 and 4.1.1, minitest 2.6.2, autotest-fsevent 0.2.7
(color and formatting are back and working)
in test_helper.rb - do NOT have 'require turn/autorun' - but have tried it both ways. Did have Turn.config.ansi = true
Any time any file is changed, entire suite of tests run.
Also, errors dump the entire stack trace - which again defeats pretty printing.
Have reverted to turn 0.8.3.
BTW - I like the PASS/FAIL/SKIP on the left rather than the right because I use really long test names, which makes a
very ragged right edge. If that is configurable, please add a couple of notes to the README
Thanks,
Mike
The text was updated successfully, but these errors were encountered: