Summary: | JUnit task should show which test case failed | ||
---|---|---|---|
Product: | Ant | Reporter: | Chris Wilson (Aptivate) <chris+apache> |
Component: | Optional Tasks | Assignee: | Ant Notifications List <notifications> |
Status: | ASSIGNED --- | ||
Severity: | enhancement | CC: | chris+apache, varavamu |
Priority: | P2 | Keywords: | PatchAvailable |
Version: | unspecified | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | other | ||
Attachments: | Patch to make Ant JUnit task log which tests failed to Ant's logging system |
Description
Chris Wilson (Aptivate)
2005-07-26 14:02:36 UTC
Created attachment 15779 [details]
Patch to make Ant JUnit task log which tests failed to Ant's logging system
I'm looking at this. 1. yes, it makes sense 2. I don't want to surprise people with a more verbose option. I'm going to initially patch it at the -v level, but we may want to think about a VerboseSummaryLogger that people could switch to. Or, we drive off a system property Looking at the code for this, I dont see there's much here that the brief formatter doesn't do, and not worth the effort to write/test/document another formatter. Why not just switch from summary formatter to brief? Sure, we can switch formatters, but the summary formatter does not seem very useful if it gives so little information. -its generally expected to run side-by-side with the junit formatter, so you run the summary to see if tests passed/failed, then switch to the generated XML/HTML results on failure. If the tests passed, you dont care what happened (unless you are being naughty and expecting people to look at the system.out to decided if a test really worked) |