[rspec-users] RSpec on Ruby 1.9: before(:all) (Not Yet Implemented) pending messages instead of tests

Shot (Piotr Szotkowski) shot at hot.pl
Wed Jan 2 03:06:55 EST 2008


David Chelimsky:

> On Dec 27, 2007 4:28 PM, Shot (Piotr Szotkowski) <shot at hot.pl> wrote:

>> I happily hand-compiled Ruby 1.9.0-0 into /home/shot/opt/ruby today
>> and I'm running into a strange error with RSpec – all my examples work
>> perfectly with Ruby 1.8 but are considered pending on Ruby 1.9.

>> How can I bugtrack/fix this?

> RSpec's tracker can be found at http://rspec.lighthouseapp.com.

Right; I’m not too fluent in RSpec yet (in particular, I didn’t use
any pending specs yet), so I just wanted to ask around before filing
a ticket.

> The "Not Yet Implemented" issue you had is fixed in trunk now.

Most appreciated! I’ll wait for RSpec 1.1.2
before switching to Ruby 1.9 in full then.

BTW: The tracker says 1.1.2 ‘is 11 months late’ and ‘Expected: Jan 17th,
2007’. Is 1.1.2 expected in two weeks’ time and it should be 2008 there?

>> I had to patch RSpec in the below manner to get it running
>> on Ruby 1.9, but I doubt these fixes can be the culprit.

>> --- lib/spec/runner/options.rb.orig     2007-12-27 16:36:03.000000000 +0100
>> +++ lib/spec/runner/options.rb  2007-12-27 16:36:28.000000000 +0100
>> @@ -102,7 +102,7 @@
>>        def colour=(colour)
>>          @colour = colour
>>          begin; \
>> -          require 'Win32/Console/ANSI' if @colour && PLATFORM =~ /win32/; \
>> +#         require 'Win32/Console/ANSI' if @colour && PLATFORM =~ /win32/; \
>>          rescue LoadError ; \
>>            raise "You must gem install win32console to use colour on Windows" ; \
>>          end

> The change to be.rb has already been applied, but not the change
> to options.rb. I'm not sure I see any relationship between that and
> problems you might be experiencing with 1.9 (unless win32console does
> not yet support 1.9).

Sorry for not explaining this one. This is with using `spec -c -D u` on
Ubuntu (with diff-lcs installed) – I keep running into an ‘uninitialized
constant Spec::Runner::Options::PLATFORM’ error, hence the simplest
above workaround. Might be a bug in Ruby 1.9 not scoping the class
constants properly, though.

> Feel free to submit a ticket to the tracker on this one.

#215 filed:
http://rspec.lighthouseapp.com/projects/5645-rspec/tickets/215

-- Shot
-- 
> So, this guy gets into Guinness by riding a 70-foot wave,
> toppling the previous record-holder's 68-footer. How do they
> measure the height of the waves to that degree of accuracy?
With a barometer, silly.         -- John Hatpin and Stan, afca
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/rspec-users/attachments/20080102/1efb7789/attachment.bin 


More information about the rspec-users mailing list