On Fri, Sep 22, 2006 at 09:47:02PM +0100, Adrian Howard wrote: > Belated response. For me good tests suites: > > * are good code (i.e. DRY, well factored, intention revealing, etc.) > * encourage good design (ala TDD) > * fail for bugs, but not refactoring > * only fail for bugs in the thing they're testing
Which includes never failing due to random causes. (Such as there being a known 5% chance of a test failing) > * don't depend on the order the tests are run in Which to me means both 1: No .t file relies on others running before them to set up 2: Any .t file can be re-run infinite times without starting to fail (before 1 is achieved, due to some sort of set up data being exhausted) Nicholas Clark
