On Thu, Apr 30, 2009 at 8:19 AM, Nicholas Van Weerdenburg <vanweerd at gmail.com> wrote:> I have started using rspec after generating much of my applications models > and controllers. Much of the code is plain vanilla scaffolding. > I accept that this is not very BDD, but I''m building a tool that required I > do this. > Is there a quick way to generate the test stubs- i.e. the equivalent of the > Test::Unit ones I now have? Can I run "script/generate rspec_model <model>" > and the same for controllers on over-top of things?$ script/generate .... Installed Generators Rubygems: acts_as_taggable_on_migration, cucumber, feature, install_rubigen_scripts, rspec, rspec_controller, rspec_model, rspec_scaffold, session Builtin: controller, helper, integration_test, mailer, metal, migration, model, observer, performance_test, plugin, resource, scaffold, session_migration Note rspec_controller, rspec_model, rspec_scaffold Cheers, David> Thanks, > Nick > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
On Thu, Apr 30, 2009 at 8:57 AM, Nicholas Van Weerdenburg <vanweerd at gmail.com> wrote:> On Thu, Apr 30, 2009 at 9:24 AM, David Chelimsky <dchelimsky at gmail.com> > wrote: >> >> On Thu, Apr 30, 2009 at 8:19 AM, Nicholas Van Weerdenburg >> <vanweerd at gmail.com> wrote: >> > I have started using rspec after generating much of my applications >> > models >> > and controllers. Much of the code is plain vanilla scaffolding. >> > I accept that this is not very BDD, but I''m building a tool that >> > required I >> > do this. >> > Is there a quick way to generate the test stubs- i.e. the equivalent of >> > the >> > Test::Unit ones I now have? Can I run "script/generate rspec_model >> > <model>" >> > and the same for controllers on over-top of things? >> >> $ script/generate >> .... >> Installed Generators >> ?Rubygems: acts_as_taggable_on_migration, cucumber, feature, >> install_rubigen_scripts, rspec, rspec_controller, rspec_model, >> rspec_scaffold, session >> ?Builtin: controller, helper, integration_test, mailer, metal, >> migration, model, observer, performance_test, plugin, resource, >> scaffold, session_migration >> >> Note rspec_controller, rspec_model, rspec_scaffold >> >> Cheers, >> David >> >> > Thanks, >> > Nick > I saw those. My question is whether they run fine if model, controller, > scaffold have already been run.No reason they shouldn''t. You should get the opportunity to approve/deny any files that already exist, and the new files will just get written. Let us know if you run into any problems. Cheers, David
If its existing models you''re dealing with, you probably will want to add --skip-migration. Just skip over replacing the model. - Josh On Fri, May 1, 2009 at 12:28 AM, David Chelimsky <dchelimsky at gmail.com> wrote:> On Thu, Apr 30, 2009 at 8:57 AM, Nicholas Van Weerdenburg > <vanweerd at gmail.com> wrote: >> On Thu, Apr 30, 2009 at 9:24 AM, David Chelimsky <dchelimsky at gmail.com> >> wrote: >>> >>> On Thu, Apr 30, 2009 at 8:19 AM, Nicholas Van Weerdenburg >>> <vanweerd at gmail.com> wrote: >>> > I have started using rspec after generating much of my applications >>> > models >>> > and controllers. Much of the code is plain vanilla scaffolding. >>> > I accept that this is not very BDD, but I''m building a tool that >>> > required I >>> > do this. >>> > Is there a quick way to generate the test stubs- i.e. the equivalent of >>> > the >>> > Test::Unit ones I now have? Can I run "script/generate rspec_model >>> > <model>" >>> > and the same for controllers on over-top of things? >>> >>> $ script/generate >>> .... >>> Installed Generators >>> ?Rubygems: acts_as_taggable_on_migration, cucumber, feature, >>> install_rubigen_scripts, rspec, rspec_controller, rspec_model, >>> rspec_scaffold, session >>> ?Builtin: controller, helper, integration_test, mailer, metal, >>> migration, model, observer, performance_test, plugin, resource, >>> scaffold, session_migration >>> >>> Note rspec_controller, rspec_model, rspec_scaffold >>> >>> Cheers, >>> David >>> >>> > Thanks, >>> > Nick >> I saw those. My question is whether they run fine if model, controller, >> scaffold have already been run. > > No reason they shouldn''t. You should get the opportunity to > approve/deny any files that already exist, and the new files will just > get written. > > Let us know if you run into any problems. > > Cheers, > David > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >