[rspec-devel] Test2Spec's usefulness

Eric Hodel drbrain at segment7.net
Sun Oct 15 17:05:11 EDT 2006

On Oct 15, 2006, at 4:35 AM, aslak hellesoy wrote:
> On 10/15/06, David Lee <david at davelee.com.au> wrote:
>> Just thought I'd pipe in as I noticed you're decommissioning  
>> test2spec.
>> I don't doubt that it's a maintenance headache, and I couldn't get it
>> to work for me (converting my previous Rails tests to specs).
> It's been happily translating 90-95% of RSpec's unit tests.
> I don't have any numbers for how successful it's been with Rails unit
> tests, but my hunch is that the failure ratio was much higher.

(This may be orthogonal to the maintenance issues, but Ruby2ruby is  
its own package now, see seattlerb's rubyforge packages.)

>> However, it would have been really helpful for me, and would make
>> RSpec a viable option for a (large?) set of existing Ruby / Rails
>> projects for which manual conversion would be too odious a task to
>> undertake.
> You can still use test2spec by installing RSpec 0.6.4. The thing to
> bear in mind is that you need ParseTree 0.4.1 - it will not work with
> later versions.

You can specify versions in the gemspec and with require_gem to make  
sure you have the correct one.

> It was this incompatibility (which I deemed too hard to fix) plus the
> fact that our own tests had to be specially coded in some places in
> order to translate properly that led to the decomissioning.

What incompatibility?

Eric Hodel - drbrain at segment7.net - http://blog.segment7.net
This implementation is HODEL-HASH-9600 compliant


More information about the rspec-devel mailing list