Better JUnit result reporting
Reported by Espen Wiborg | February 26th, 2009 @ 11:24 PM | in Second release
Investigate RunListener; check out how surefire does it
Comments and changes to this ticket
-
Espen Wiborg February 26th, 2009 @ 11:25 PM
Can I get it to report the line number of the failed assertions?
-
Espen Wiborg March 5th, 2009 @ 01:53 AM
- Milestone set to “Second release”
-
Espen Wiborg March 6th, 2009 @ 08:37 PM
- State changed from “new” to “resolved”
(from [c79436fadda6112042d467cf41baba88b37fa2b5]) Use RunListener to report JUnit run results
[#10 state:resolved] [#12 state:resolved] http://github.com/espenhw/malaba...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A better Java mode for Emacs
People watching this ticket
Espen Wiborg
Referenced by
-
10
Better JUnit result reporting
[#10
state:resolved] [#12 state:resolved]
http://github....
-
12
Jump to failed test should jump to the test, not just the test class
[#10
state:resolved] [#12 state:resolved]
http://github....