Michael Rigart wrote: > t.string 'name', :null => false > t.string 'address', :null => false > t.string 'zip', :null => false > t.string 'city', :null => false > t.string 'country', :null => false > t.string 'phone', :null => true > t.string 'fax', :null => true > t.string 'email', :null => false > t.integer 'status', :null => false > t.boolean 'is_root', :null => false, :default => false > t.boolean 'access_crm', :null => false, :default => false > t.boolean 'access_project', :null => false, :default => false > t.boolean 'access_dmail', :null => false, :default => false > t.boolean 'access_financial', :null => false, :default => false
Access looks like a separate table with a type. How about, instead of retrofitting tests to existing features, you test-first the existence and behavior of this new type? Then test-first the database migration that copies your production data into it... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
