On Jan 19, 6:24 pm, Luke Amdor <luke.am...@gmail.com> wrote: > I also think that if your test needs a description of what it's doing, > then that's a smell. It's an excuse for easily readable code and I > think we can all agree that we should try to make our code as easily > readable as possible.
The code can tell you what a test does, but not necessarily its purpose. No matter how readable your code is, it can only tell you the what and how, not the why. So my personal preference is pair a test up with a description of it's purpose; the description is the theory, the test code is the evidence that backs it up. - James --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
