search for: before_ev

...3::SQLException in ServiceConfig with minimum set of valid parameters should return nil for the service path'' SQL logic error or missing database C:/development/sandbox/prototypes/user_admin_client/config/../vendor/plugins/rspec_on_rails/lib/spec/rails/dsl/behaviour/rails_example.rb:17:in `before_eval'' None of my code had changed. All specs worked *immediately* prior to the ''svn up'' this morning. Now all are broken immediately after the svn up. I am trying to track this down but hoping for some "Help ..." . Cheers! sinclair -------------- next part --...

...xture_scenarios.rb:29:in `create_fixtures'' ..lib/fixture_scenarios.rb:28:in `create_fixtures'' ..lib/fixture_scenarios.rb:26:in `create_fixtures'' ..lib/fixture_scenarios.rb:257:in `load_fixtures'' plugins/rspec_on_rails/lib/spec/rails/dsl/behaviour/model.rb:12:in `before_eval'' The project is heavily scenario-dependent, so if it comes to a choice we know which one we will save and which we will lose... Has anyone encountered this? Can''t fixture_scenarios and RSpec live together in peace and harmony? -- Phlip --~--~---------~--~----~--------...

...] end === spec_helper.rb === # require this file from all your specs under MYAPP/spec/watir or MYAPP/spec/selenium require ''rubygems'' require ''spec'' require ''spec/ui'' require ''spec/ui/watir'' class Spec::DSL::Behaviour def before_eval # This gives us Watir matchers. Sorry - Selenium-RC users must use the low level API include Spec::Matchers::Watir end end === before and after blocks === All of your specs need some carefully designed before and after blocks: before(:all) do @browser = Watir::Browser.new #@browse...

...t row: a foreign key constraint fails (`mediajoint_development/accounts`, CONSTRAINT `accounts_opener_id_fk` FOREIGN KEY (`opener_id`) REFERENCES `users` (`id`)): DELETE FROM users /Users/jay/Documents/eclipse/mediajoint/vendor/plugins/rspec_on_rails/lib/spec/rails/dsl/behaviour/model.rb:12:in `before_eval'' I''ve even manually run the entire "ruby -I" command that rake generates, and it works fine. I can''t see that the rake task''s doing anything different other than db:test:prepare, which I can do manually with no problem. What''s rake doing...

.../lib/active_record/fixtures.rb:572:in `use_transactional_fixtures?'' /Library/Ruby/Gems/gems/activerecord-1.15.5.7919/lib/active_record/fixtures.rb:585:in `setup'' /Users/jamal/Documents/RubyonRailsApps/rspec/vendor/plugins/rspec_on_rails/lib/spec/rails/dsl/behaviour/model.rb:12:in `before_eval'' script/spec:4: Finished in 0.016046 seconds 1 example, 1 failure ------------------------------------------------------- -- Posted via http://www.ruby-forum.com/.

...e_fixtures'' ../vendor/plugins/fixture_scenarios/lib/fixture_scenarios.rb:26:in `create_fixtures'' ../vendor/plugins/fixture_scenarios/lib/fixture_scenarios.rb:257:in `load_fixtures'' ../vendor/plugins/rspec_on_rails/lib/spec/rails/dsl/behaviour/ rails_example.rb:27:in `before_eval'' At the moment I am only using global fixtures for one model, I have tried removing this line and its still the same error. config.global_fixtures = :sites and I have added the trailing slash to my fixture path config.fixture_path = RAILS_ROOT + ''/spec/fixtures/''...

So, I''ve been following the recommendations for controller specs here: http://blog.davidchelimsky.net/articles/2006/11/09/tutorial-rspec-stubs-and-mocks Most notably: a single expectation per specify block; the setup block contains only stubs; mock expectations each get their own specify block. (I''m still using 0.8, so I haven''t gotten the describe/it goodness yet.) I

Hi RSpec Mailing list, I''m new to RSpec and I am trying to get it running with the caboo.se sample rails app. I installed the current version of rspec with rspec_on_rails I tried to run rake spec but received: 330-07:~/desktop/restful_auth_rspec/vendor multimedia$ rake spec (in /Users/multimedia/Desktop/restful_auth_rspec)

We''d like to get some feedback on RSpec 0.9 before we start pushing out releases via Rubyforge''s gem server and update the website. We have therefore made the first beta of 0.9 available - both prepackaged and tagged in subversion (see below). RSpec 0.9 introduces a new API for expectations, which essentially means that your underscores go away (there has been other discussions