[rspec-users] How to write a plugin that uses rspec internally?

My team is working on a plugin and we want to use RSpec internally for the plugin's tests. (a) What are some different ways to go about this? Should we rely on the RSpec gem? Should we expect that the "host" Rails application has installed the RSpec plugins? Are there other options? (b) Which

Re: [rspec-users] How to write a plugin that uses rspec internally?

On 9/15/07, David James <[EMAIL PROTECTED]> wrote: > My team is working on a plugin and we want to use RSpec internally for the > plugin's tests. > > (a) What are some different ways to go about this? Should we rely on the > RSpec gem? Should we expect that the "host" Rails application has instal

Re: [rspec-users] How to write a plugin that uses rspec internally?

Thanks! ___ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users

[rspec-users] #add method?

I've seen reference to an 'add' method, as in Model.add. When and why would I want to use it? Is it related to Model.collection.build? Thanks, David ___ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-user

[rspec-users] How far to go with ActiveRecord unit tests without hitting the database?

I'm currently try to push my limits a little bit with some of my unit testing -- trying to avoid saving ActiveRecord objects to the database and take advantage of mock/stub objects. How far should I expect to get in this direction? From what I can tell, ActiveRecord seems to fight me when it come

Re: [rspec-users] How far to go with ActiveRecord unit tests without hitting the database?

On 9/15/07, David James <[EMAIL PROTECTED]> wrote: > I'm currently try to push my limits a little bit with some of my unit > testing -- trying to avoid saving ActiveRecord objects to the database and > take advantage of mock/stub objects. > > How far should I expect to get in this direction? From