Warnings for non-public test classes
Reported by benrady (at gmail) | October 13th, 2009 @ 05:23 PM
from Jeff Langr:
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) October 13th, 2009 @ 05:23 PM
from Jeff Langr:
hi Ben, it's an edge case, and not something I do often. I did it one more time and this time knew where to look immediately when I didn't get the expected red bar.
It's caused by code generation, if I remember correctly, and so I envision more people than me getting tripped up by this at least one.
I look at it as a significant flaw--since you're now hiding explicit test execution, anything that doesn't get run that people think should be getting run is going to create some heartache (and potentially distrust). It won't stop me from using the tool (and recommending it elsewhere--even at cost it's a great tool). Bummer that it's a tough one to fix.
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)