> Incomplete/Pass/Fail/Error/Ambiguous. In my experience, this many kinds of logging is counterproductive. Unit tests should either succeed or fail---nothing more. Developers will be more likely to run the tests more often if they don't have to spend time interpreting test logs. ("Ambiguous"? What, the system thought that *maybe* the test passed?) --k --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
- Re: Test Infrastructure Project Proposal Doug Davis
- Re: Test Infrastructure Project Proposal Jon Stevens
- Re: Test Infrastructure Project Proposal Sam Ruby
- Re: Test Infrastructure Project Proposal Jeff Martin
- Test Infrastructure Project Proposal Scott_Boag
- Re: Test Infrastructure Project Proposal Jon Stevens
- Re: Test Infrastructure Project Proposal Peter Donald
- Test Infrastructure Project Proposal Doug Davis
- Re: Test Infrastructure Project Proposal Rob Leland
- Re: Test Infrastructure Project Proposal Shane_Curcuru
- Re: Test Infrastructure Project Proposal Sean Kelly
- Re: Test Infrastructure Project Proposal Jon Stevens
- Re: Test Infrastructure Project Proposal Ovidiu Predescu
- Re: Test Infrastructure Project Proposal Paul Russell
- Test Infrastructure Project Proposal Sam Ruby
- RE: Test Infrastructure Project Proposal Steve Downey
- Re: Test Infrastructure Project Proposal Ted Husted
- Re: Test Infrastructure Project Proposal Jon Stevens
- RE: Test Infrastructure Project Proposal Steve Downey
- Re: Test Infrastructure Project Proposal Kevin A. Burton
- Re: Test Infrastructure Project Proposal Jon Stevens