Fix double run! (Issue #26) #29

Merged
merged 1 commit into from Apr 20, 2013

Conversation

Projects
None yet
1 participant
Contributor

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.

@soffes soffes Exit with a BANG!
This prevents MiniTest from autoloading the test suite after running a portion of it.
17b586d
Contributor

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 referenced this pull request Apr 19, 2013

Merged

Fix double run #31

@soffes soffes merged commit 17b586d into qrush:master Apr 20, 2013

1 check failed

default The Travis build failed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment