Skip to content
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 double run! (Issue #26) #29

Merged
merged 1 commit into from Apr 20, 2013
Merged

Fix double run! (Issue #26) #29

merged 1 commit into from Apr 20, 2013

Conversation

soffes
Copy link
Contributor

@soffes soffes commented Mar 6, 2013

Exit with a BANG! This prevents MiniTest from autoloading the test suite after running a portion of it.

Fixes issue #26.

This prevents MiniTest from autoloading the test suite after running a portion of it.
@soffes
Copy link
Contributor Author

soffes commented Mar 6, 2013

Ugh. So this broke a bunch of tests. From what I can see, it all actually works fine. I can't figure out how to fix the tests though.

The tests run this command (from m/test):

$ ruby -I../lib -I. ../bin/m examples/active_support_example_test.rb:12 2>&1
Run options: -n "/(test_carrot)/" --seed 17434

# Running tests:

.

Finished tests in 0.010998s, 90.9256 tests/s, 90.9256 assertions/s.

1 tests, 1 assertions, 0 failures, 0 errors, 0 skips

and everything is fine. If I write the output to file and then cat it, it's different though:

$ rm -f log.txt; ruby -I../lib -I. ../bin/m examples/active_support_example_test.rb:12 2>&1 >> log.txt; cat log.txt
Run options: -n "/(test_carrot)/" --seed 61876

# Running tests:

.%

My shell scripting skills are definitely lacking in this area. Any idea how to make this match what I see if you just run the command by itself?

@ngauthier ngauthier mentioned this pull request Apr 19, 2013
@soffes soffes merged commit 17b586d into qrush:master Apr 20, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant