[rspec-users] Can't run specs after upgrading gems... get 0 tests, 0 assertions...

Brian Takita lists at ruby-forum.com
Mon Nov 2 00:49:06 EST 2009

Actually, I think this is more of a bug with test/unit.

If you are going to override inherited, be a good citizen and call 
super. :-)
Same with method_missing or any other "core" method you override.

Anyways, I do have a fix. It's to monkey-patch test/unit. How do I also 
submit the patch to test/unit?
David Chelimsky wrote:
> On Sun, Oct 4, 2009 at 6:35 PM, Stephen Eley <sfeley at gmail.com> wrote:
>> Test::Unit gem into RSpec? �And then require the bundled Test::Unit
>> directly on its path instead of the gem and Ruby loadpaths?
>> Sure, for stock Ruby 1.8 users this would be redundant, but they
>> wouldn't really lose anything. �And everyone on 1.9 or running the
>> Test::Unit gem for other purposes gains reliability and a much easier
>> path to getting RSpec running the first time. �It's not an ideal
>> solution but it'd be quick to set up. �Is there a reason why this
>> wouldn't work or shouldn't be done?
> I'll give this some thought, though I'd much rather just solve the
> problem. For the 1.2.9 release I added a message. When you run specs
> w/ test/unit interop (which is implicit in rspec-rails) it senses
> whether t/u 1.2.3 is loaded - if not it raises an error explaining
> your options.
> In terms of solving the problem, there are a few paths:
> 1. Figure out why ruby 1.9 + rubygems + activesupport is allowing two
> different versions of the same gem to be loaded.
> 2. Get rspec to play nice w/ test-unit-2.0.3
> 3. Get rspec to play nice w/ minitest.
> 4. Some combination of 1, 2, and 3.
> This probably won't get resolved (by me) until we release rspec-2,
> work on which has begun but it's waiting for me to get the book off to
> print before it gets the full love and attention it needs. If anybody
> out there wants to help w/ any of the above, please fork the repo, get
> it to work, and if it works well I'll be glad to merge it back in.
> Cheers,
> David

Posted via http://www.ruby-forum.com/.

More information about the rspec-users mailing list