I just went back and tried just removing rspec-rails from the RAILS config. Oh, why I did not try this first is beyond me. Well, rake spec:models works. So, it is not RAILS itself, but the gem rspec- rails that caused the issue. I had just installed it so I could use the default rake tasks it adds to the rails structure.
On Jun 8, 10:48 am, GregD <[email protected]> wrote: > Finally, after much hoop jumping. I ran it outside of rails. I had > to comment out the rails loading in spec_helper.rb. I had to then > load the specific files in the proper order (sequel, set DB, models, > spec/support files). > > Yes, it runs like you said. So, it is rails that is causing the > problem. I'm not really depended on rails. It was a convenience to > load files, use the default rake tasks, use the console, etc, just so > I did not have to figure out and set those things up myself. > > I'm guessing here but I bet there is a way to do this within rails > config. Does anyone out there know? > > GregD > > . > On Jun 7, 5:15 pm, Jeremy Evans <[email protected]> wrote: > > > > > On Jun 7, 2:00 pm, GregD <[email protected]> wrote: > > > > I tried something similar. Actually, put a puts outside it all to > > > make sure it was loading. > > > > Yes it is loading, but the code is not running. I'm not sure why. > > > Here is the file that is getting loaded. Looks similar to yours. > > > > puts("Loading") > > > class Spec::Example::ExampleGroup > > > def execute(*args, &block) > > > puts "Begin transaction and override execute()" > > > DB.transaction{super(*args, &block); puts "raise error"; raise > > > Sequel::Rollback} > > > puts "End transaction" > > > end > > > end > > > > I never see the STDOUT except for the 'Loading' when I do a rake spec. > > > > Something is wrong here and I'm having a hard time figuring it out. > > > > rspec 1.3.0 > > > rspec-rails 1.3.2 > > > Can you try it with just rspec and not rspec_rails. I've only used > > plain rspec and eliminating rspec_rails from the equation would make > > it easier to figure out where the problem is. > > > Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
