search for: object_daddy

...a feed # features/admin/manage_feeds.feature:23 Given an admin user Philip exists # features/step_definitions/accounts/creation.steps.rb:66 Validation failed: Login has already been taken, Email has already been taken (ActiveRecord::RecordInvalid) /Users/andy/Sites/mvor/vendor/plugins/object_daddy/lib/object_daddy.rb:210:in `generate!'' /Users/andy/Sites/mvor/vendor/plugins/object_daddy/lib/object_daddy.rb:32:in `spawn'' /Users/andy/Sites/mvor/vendor/plugins/object_daddy/lib/object_daddy.rb:209:in `/^I create a user with login (\w*)$/'' features/admin/manage_f...

...s to copy some directories, that don''t exist anymore. I did some remodelling in the file, so it creates a rpm now, but I''m not sure whether my "fix" is the only change needed. my change: replace -------------------- for plugin in authlogic inherited_resources jrails object_daddy resources_controller timeline_fu will_paginate; do cp -p -r vendor/plugins/$plugin %{buildroot}%{_datadir}/%{name}/ vendor/plugins/$plugin done cp -p -r vendor/gems %{buildroot}%{_datadir}/%{name}/vendor cp -p -r vendor/rails %{buildroot}%{_datadir}/%{name}/vendor -------------------- with ---...

Hi everyone, I''m just now really starting to look into Agile Development, and so I''m trying to gauge what the Rails community''s preference is in regards to using RSpec versus the built-in Test::Unit. I haven''t really delved much into testing in the past, I''m sad to say, but I understand why it''s beneficial to writing maintainable code and

As I work with Rails TestUnit tests I am reconsidering how to use cucumber features. It seems to me that it might be best to have a coherent view of how to arrange my test suites before I get much further into this. Now, so far I have considered three possibilities: 1. Use features exclusively. Create a feature file for each model, one for each controller and possibly an additional one for