On 10/09/2011, at 4:08 PM, Ben Hoskings wrote: > My stance is this: those associations are there for a reason: you want to > somehow relate artists and releases, and do operations on them in tandem, or > from one to the other. If you directly unit test (ideally, test-drive) those > operations throughly, then the associations are implicitly tested.
This is a good point too... as Pat alluded to, if you're doing proper BDD or TDD, a lot of unit tests are just unnecessary because the tendency (well mine at least) is to design the application from the interface "down" to the data model, rather than the other way around. Obviously you begin with a rough idea of the primary entities like an Artist or a Release, but until you have the picture of how the two will relate to each other and interact within the system (through your user stories), it's best to not try and over-specify them. (Somewhere, a BA died a little on the inside when I wrote that. Oh well.) Cheers, W. -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
