Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • so no tests for static pages? Commented Mar 9, 2012 at 17:44
  • TDD is, to a degree, about design. But you still need an architecture. Without an architecture in mind, it's difficult to imagine how one would grow organically out of a bunch of tests. Commented Mar 9, 2012 at 19:06
  • @MatteoPagliazzi Depending on the level of the testing (unit tests / integration tests / etc), perhaps one or two, to confirm the static pages are accessible. But that's too high-level for unit tests. Commented Mar 9, 2012 at 21:43
  • 1
    @RobertHarvey I didn't say don't test anything. I said don't unit test static pages. Commented Mar 12, 2012 at 13:14
  • @JonStrayer: TDD'ers tend to hold up TDD as some magical elixir for design; I apologize if that's not what you meant. :) Commented Mar 12, 2012 at 14:42