James Deville
2007-Dec-09 04:47 UTC
[rspec-users] [rspec-devel] rspec_on_rails (trunk - r3070) works with Rails 2.0.1
I figured most of it out. The Spec::Rails stuff was something in the code which has been fixed by revision 3099. The test methods partially make sense. Since the test/unit code has been integrated, methods with test in them are automatically turned into specs. However, the test? method is in a lib file that isn''t directly loaded into the specs. It is a convenience method: def test?; RAILS_ENV=="test";end I don''t know why this method is being included in my tests, every context has it as an example. Any ideas? Jim D On Dec 8, 2007, at 8:42 PM, James Deville wrote:> > > Begin forwarded message: > >> From: James Deville <james.deville at gmail.com> >> Date: December 7, 2007 5:00:30 PM PST >> To: James Deville <james.deville at gmail.com> >> Subject: Re: [rspec-devel] rspec_on_rails (trunk - r3070) works >> with Rails 2.0.1 >> >> Nope, i''m now getting a test? spec before every group, it seems >> related to the rspec_on_rails plugin. I''ll take a look more at >> home, but I would appreciate any help. >> >> Person with account >> - test? >> - should obviously show last login >> ... >> >> Person model: A new Person >> - test? >> - should have an empty dna_contacts collection >> ... >> >> >> - test? >> >> >> - test? >> >> >> - test? (FAILED - 5) >> >> Spec::Rails::Example::FunctionalExampleGroup >> - test? (ERROR - 6) >> >> >> - test? >> >> Spec::Rails::Example::RailsExampleGroup >> - test? >> >> Pending: >> >> >> JD >> >> >> >> On Dec 7, 2007, at 4:39 PM, James Deville wrote: >> >>> I think I just found it. I had rspec 1.0.8 unpacked as a gem in >>> vendor/gems >>> >>> However, now I am getting a test? spec before every group. I''ll >>> try going to 3070 to see if it fixes the problem >>> >>> JD >>> On Dec 7, 2007, at 4:18 PM, James Deville wrote: >>> >>>> No change. >>>> >>>> Jim >>>> >>>> On Dec 7, 2007, at 4:06 PM, David Chelimsky wrote: >>>> >>>>> On Dec 7, 2007 6:01 PM, James Deville <james.deville at gmail.com> >>>>> wrote: >>>>>> I''m getting an error with this fix. My versions: rspec:3072 >>>>>> rspec_on_rails:3073 >>>>> >>>>> You''ve got 2 different revisions of rspec, 3072 and 3073. Can you >>>>> align those and try again? >>>>> >>>>>> rails:2.0.1. Formatter in this case is Specdoc >>>>>> >>>>>> The odd part is that debugger is telling me that BaseFormatter, >>>>>> BaseTextFormatter and SpecdocFormatter all take one argument. I >>>>>> don''t >>>>>> have the gem installed, so I''m not sure where Ruby is getting >>>>>> that >>>>>> from, as the code shows 2, options and where. >>>>>> >>>>>> Any advice on where to look, or what other information I can >>>>>> give you? >>>>>> >>>>>> Jim D >>>>>> >>>>>> >>>>>> Aragorn:mydna james$ rake spec >>>>>> (in /Users/james/projects/mydna) >>>>>> /Users/james/projects/mydna/app/models/asset.rb:23: warning: >>>>>> Object#id >>>>>> will be deprecated; use Object#object_id >>>>>> ./spec/models/mailers/person_notifier_spec.rb:41: warning: >>>>>> already >>>>>> initialized constant FIXTURES_PATH >>>>>> ./spec/models/mailers/person_notifier_spec.rb:42: warning: >>>>>> already >>>>>> initialized constant CHARSET >>>>>> ./spec/models/mailers/feedback_notifier_spec.rb:4: warning: >>>>>> already >>>>>> initialized constant FIXTURES_PATH >>>>>> ./spec/models/mailers/feedback_notifier_spec.rb:5: warning: >>>>>> already >>>>>> initialized constant CHARSET >>>>>> /Users/james/projects/mydna/vendor/plugins/rspec/lib/spec/runner/ >>>>>> options.rb:151:in `initialize'': wrong number of arguments (2 >>>>>> for 1) >>>>>> (ArgumentError) >>>>>> from /Users/james/projects/mydna/vendor/plugins/rspec/lib/ >>>>>> spec/runner/ >>>>>> options.rb:151:in `new'' >>>>>> from /Users/james/projects/mydna/vendor/plugins/rspec/lib/ >>>>>> spec/runner/ >>>>>> options.rb:151:in `formatters'' >>>>>> from /Users/james/projects/mydna/vendor/plugins/rspec/lib/ >>>>>> spec/runner/ >>>>>> options.rb:144:in `map'' >>>>>> from /Users/james/projects/mydna/vendor/plugins/rspec/lib/ >>>>>> spec/runner/ >>>>>> options.rb:144:in `formatters'' >>>>>> from /Users/james/projects/mydna/vendor/plugins/rspec/lib/ >>>>>> spec/runner/ >>>>>> reporter.rb:71:in `formatters'' >>>>>> from /Users/james/projects/mydna/vendor/plugins/rspec/lib/ >>>>>> spec/runner/ >>>>>> reporter.rb:58:in `dump'' >>>>>> from /Users/james/projects/mydna/vendor/plugins/rspec/lib/ >>>>>> spec/runner/ >>>>>> example_group_runner.rb:37:in `finish'' >>>>>> from /Users/james/projects/mydna/vendor/plugins/rspec/lib/ >>>>>> spec/runner/ >>>>>> example_group_runner.rb:26:in `run'' >>>>>> from /Users/james/projects/mydna/vendor/plugins/rspec/lib/ >>>>>> spec/runner/ >>>>>> options.rb:85:in `run_examples'' >>>>>> from /Users/james/projects/mydna/vendor/plugins/rspec/lib/ >>>>>> spec/runner/ >>>>>> command_line.rb:19:in `run'' >>>>>> from /Users/james/projects/mydna/vendor/plugins/rspec/bin/ >>>>>> spec:3 >>>>>> rake aborted! >>>>>> >>>>>> >>>>>> On Dec 7, 2007, at 11:32 AM, David Chelimsky wrote: >>>>>> >>>>>>> After a couple of quick fixes this morning, rspec_on_rails (in >>>>>>> trunk >>>>>>> as of rev 3070) now works correctly with Rails 2.0.1 >>>>>>> >>>>>>> Now that Rails 2.0 is out, we''ll try to get an RSpec 1.1 release >>>>>>> candidate out the door in the next few days. >>>>>>> >>>>>>> Cheers, >>>>>>> David >>>>>>> _______________________________________________ >>>>>>> rspec-devel mailing list >>>>>>> rspec-devel at rubyforge.org >>>>>>> http://rubyforge.org/mailman/listinfo/rspec-devel >>>>>> >>>>>> _______________________________________________ >>>>>> rspec-devel mailing list >>>>>> rspec-devel at rubyforge.org >>>>>> http://rubyforge.org/mailman/listinfo/rspec-devel >>>>>> >>>>> _______________________________________________ >>>>> rspec-devel mailing list >>>>> rspec-devel at rubyforge.org >>>>> http://rubyforge.org/mailman/listinfo/rspec-devel >>>> >>> >> >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rspec-users/attachments/20071208/1bff0065/attachment-0001.html
Craig Demyanovich
2007-Dec-09 15:09 UTC
[rspec-users] [rspec-devel] rspec_on_rails (trunk - r3070) works with Rails 2.0.1
On Dec 8, 2007 11:47 PM, James Deville <james.deville at gmail.com> wrote:> I figured most of it out. The Spec::Rails stuff was something in the code > which has been fixed by revision 3099. The test methods partially make > sense. Since the test/unit code has been integrated, methods with test in > them are automatically turned into specs. However, the test? method is in a > lib file that isn''t directly loaded into the specs. It is a convenience > method: def test?; RAILS_ENV=="test";end > I don''t know why this method is being included in my tests, every context > has it as an example. Any ideas? >I have a couple ideas. If the lib file is on the load path, then maybe rspec is searching it. Also, re: the name, maybe rspec and/or test::unit is recognizing the method as a test because it begins with "test." Try renaming the method. Regards, Craig -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rspec-users/attachments/20071209/0da05940/attachment.html