Skip to main content

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.

Required fields*

5
  • -1 What? This seems to have no relevance. Commented Oct 12, 2010 at 23:38
  • 2
    There must be a point when one should stop trying to unit test. Should know when to draw the line. Should we write test cases to test test cases? What about the new test cases written to test test cases? How will we test them? Commented Oct 12, 2010 at 23:52
  • 2
    Process Brain raised EInfiniteRecursion while attempting to extrapolate your statement... Commented Oct 13, 2010 at 0:10
  • Replace your answer with your comment and you'll get a +1 Commented Oct 13, 2010 at 0:13
  • 4
    In all fairness, your example is a straw man. You're testing the printf() subsystem in a C library, not the actual program calling printf(). I do agree, however, that at some point one must break the recursive testing of tests. Commented Oct 13, 2010 at 2:33