On 21/11/2008, at 9:53 AM, Torm3nt wrote: > I thought that's all that code coverage was for - to ensure that the > tests you're writing are indeed going via the paths you expect.
That's correct. "Coverage" is a bit of a misnomer because you're typically interested in code paths *not* being covered by tests (so that you can decide if your tests are lacking). For this reason, I generally suggest you start running when someone baulks at sub-100% coverage. -- Nathan de Vries --~--~---------~--~----~------------~-------~--~----~ 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 rails-oceania@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
