Jason House wrote:
Simply running all tests is necessary but not sufficient. After
running hundreds of thousands of tests, there needs to be any easy way
to figure out which tests failed and review their failure.
maybe there should be an implicit line added ate the top of all unittests:
scope(failure) writefln("unittest at %s:%d failed", __FILE__,__LINE__);
Just as an example, I started a project last week at work, and my
current test suite has:
• 250 passing tests. These are regression tests.
• 22 tests that fail but represent current out of scope features so
should continue to fail
• 24 failing tests for work-in-progress changes. These are the main
focus of current effort (AKA test-driven-development)
some kind of external tool? Or maybe a @expectFail tag?
Sent from my iPhone
_______________________________________________
dmd-internals mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/dmd-internals
