[rspec-users] rspec with CI
marcus at marcuscrafter.com
Mon Apr 16 22:57:08 EDT 2007
I'm having a similar problem with CC.rb at the moment - from what I
can see, CC.rb is trying to run my spec's using the production
database, rather than the test one:
1) ActiveRecord::StatementInvalid in 'A new Activation object should
be invalid without a name' Mysql::Error: Table
'cms_production.activations' doesn't exist: SHOW FIELDS FROM
Naturally this causes all of the specs to fail. :-/
Running the same 'rake spec' on the command line in my rails app
works as expected.
I don't have a solution just yet but have also asked if others were
having this problem on the cc.rb users mailing list - hopefully we'll
have a solution to it soon.
If this isn't the problem you're having - would be good to know so we
can sort that out too. At least you're not the only one :)
On 17/04/2007, at 12:23 PM, Alex Edwards wrote:
> I am a bit of a rails and rspec noob.
> I am trying to use rspec in conjunction with CruiseControlrb.
> When I run a cruise build having spec errors, the build does not
> indicate a failure. I have tried to track down why this is the case,
> and my best guess is that the spec task is kicking off the spec via a
> ruby() method in rake, and that ruby method does not propagate my spec
> failure back to rake.
> Any help in setting this up would be much appreciated.
> Also, if there is a better alternative to cruisecontrolrb that
> integrates nicely with rspec, please let me know.
> rspec-users mailing list
> rspec-users at rubyforge.org
More information about the rspec-users