Annoying output from test unit/ mini test #7328

Closed
rkcudjoe opened this Issue Aug 11, 2012 · 7 comments

Comments

Projects
None yet
2 participants
@rkcudjoe

I get this annoying output even though I'm not using test unit and I passed in --no-test-unit when I generated the app.

/home/rkcudjoe/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/test/unit.rb:167:in block in non_options': file not found: db:migrate (ArgumentError) from /home/rkcudjoe/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/test/unit.rb:146:inmap!'
from /home/rkcudjoe/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/test/unit.rb:146:in non_options' from /home/rkcudjoe/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/test/unit.rb:207:innon_options'
from /home/rkcudjoe/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/test/unit.rb:52:in process_args' from /home/rkcudjoe/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/minitest/unit.rb:891:in_run'
from /home/rkcudjoe/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/minitest/unit.rb:884:in run' from /home/rkcudjoe/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/test/unit.rb:21:inrun'
from /home/rkcudjoe/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/test/unit.rb:326:in block (2 levels) in autorun' from /home/rkcudjoe/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/test/unit.rb:27:inrun_once'
from /home/rkcudjoe/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/test/unit.rb:325:in `block in autorun'

@steveklabnik

This comment has been minimized.

Show comment
Hide comment
@steveklabnik

steveklabnik Aug 11, 2012

Member

... you get the output when you do what?

Member

steveklabnik commented Aug 11, 2012

... you get the output when you do what?

@rkcudjoe

This comment has been minimized.

Show comment
Hide comment
@rkcudjoe

rkcudjoe Aug 11, 2012

The output I'm showing is from bundle exec rake db:migrate, something similar happened when I generated a controller as well.

The output I'm showing is from bundle exec rake db:migrate, something similar happened when I generated a controller as well.

@steveklabnik

This comment has been minimized.

Show comment
Hide comment
@steveklabnik

steveklabnik Aug 11, 2012

Member

Okay! Is this a fresh app, or are there other things going on?

Member

steveklabnik commented Aug 11, 2012

Okay! Is this a fresh app, or are there other things going on?

@rkcudjoe

This comment has been minimized.

Show comment
Hide comment
@rkcudjoe

rkcudjoe Aug 11, 2012

Fresh app, I'm working on it now.

Fresh app, I'm working on it now.

@steveklabnik

This comment has been minimized.

Show comment
Hide comment
@steveklabnik

steveklabnik Aug 11, 2012

Member

I cannot reproduce this issue. I literally just reinstalled my rubies, gems, and everything (yay mountain lion!) and I get zero bad output.

Is there any way you can help me reproduce this?

Member

steveklabnik commented Aug 11, 2012

I cannot reproduce this issue. I literally just reinstalled my rubies, gems, and everything (yay mountain lion!) and I get zero bad output.

Is there any way you can help me reproduce this?

@rkcudjoe

This comment has been minimized.

Show comment
Hide comment
@rkcudjoe

rkcudjoe Aug 11, 2012

You are right, the problem is with the shoulda gem, I was only able to reproduce it when added shoulda. Thanks for your help.

You are right, the problem is with the shoulda gem, I was only able to reproduce it when added shoulda. Thanks for your help.

@steveklabnik

This comment has been minimized.

Show comment
Hide comment
@steveklabnik

steveklabnik Aug 11, 2012

Member

Awesome! Thanks.

Member

steveklabnik commented Aug 11, 2012

Awesome! Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment