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.

Required fields*

8
  • Unless you have a dozen test cases for a moderately-sized class, you're probably not getting much useful output from the test. Testing is all about exploring different scenarios, preferably an exhaustive set of scenarios, including realistic error scenarios. Commented Mar 29, 2011 at 12:09
  • 1
    0% test coverage says something. Commented Mar 29, 2011 at 13:15
  • @Marcie IMO: 0% is better that 100%. There should be a permutation coverage term. Commented Mar 29, 2011 at 13:20
  • @Amir, that would be an interesting concept. If you find a way to calculate that, I think we would love to see it. Commented Mar 29, 2011 at 16:17
  • @Marcie: that's what code coverage metrics do. en.wikipedia.org/wiki/Code_coverage has an intro. Unless Amir meant exhaustive testing which is generally impractical due to the rapid rise of the permuation count. Commented Apr 6, 2011 at 4:48