[rspec-users] RSpec interacting with Test::Unit: weird "is already defined" error

Jo Liss joliss42 at gmail.com
Tue Nov 30 15:11:37 EST 2010

On Tue, Nov 30, 2010 at 7:21 PM, David Chelimsky <dchelimsky at gmail.com> wrote:
> Or is there a problem you're trying to solve by intermingling them?
> I'd recommend keeping specs under the spec directory and run them separately from Test::Unit tests.

Ah, I see -- thanks for the quick reply!

So, I'm really trying to write test code, not specs.  There are a
bunch of existing Test::Unit tests.  But since I'm using
rspec/expectations's "should" assertions in my test code already (as
described on http://relishapp.com/rspec/rspec-expectations/v/2-0/dir/test-frameworks/test-unit-integration
), I figured I might use RSpec instead of Test::Unit to structure my
tests, as RSpec has this awesome nesting feature.

But from your reply I take it that trying to squeeze my test code into
RSpec (even if I migrated all my Test::Unit tests to RSpec tests) is
going to result in ugly code and unhappiness?


More information about the rspec-users mailing list