Andrei Alexandrescu wrote:
On 04/28/2010 09:56 AM, 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.
Yes. This is a huge matter which the change only makes worse.
I had to completely change the unittesting method for Phobos because
any segfault would be virtually impossible to track down.
Walter, failing unittests for any reason must display the file and
line of failure.
It already does:
----------------------------
int x;
void main() { }
unittest {
assert(x == 3, "x should be 3");
assert(x == 4);
assert(x == 5);
}
--------------------------------
Running it:
test3.d(10): x should be 3
test3(11): unittest failure
test3(12): unittest failure
I'm not sure to what extent segfaulting is detectable, but we
definitely must find good ways to address that too.
Debuggers are the standard tool for that.
_______________________________________________
dmd-internals mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/dmd-internals
