Warn on badly formed tests
Reported by benrady (at gmail) | September 3rd, 2009 @ 01:42 AM
I created a non-public test class, which JUnit will choke on if run explicitly (with the message "Test class should have public zero-argument constructor"). Good TDD habit means that one should figure out the error soon enough, but I'm thinking it would be very useful to have this report as a Problem.
If I change the test class to be public, test failures start appearing as they should. If I again make it non-public, the test failures do not disappear (deleting them manually solved the problem).
Comments and changes to this ticket
-
benrady (at gmail) September 3rd, 2009 @ 01:42 AM
- Assigned user set to “benrady (at gmail)”
-
benrady (at gmail) September 3rd, 2009 @ 01:42 AM
- Assigned user cleared.
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 ยป
Continuous Test Runner for Java
benrady (at gmail)