Reputation: 59385
I'm forced to use JUnit 3. If I were using JUnit 4, I would occasionally use @Ignore
since several of my tests take a bit of time.
Is there anything analogous in JUnit 4? Commenting out tests is sloppy, and changing the name (from testXxx()
) could lead to forgotten tests. @Ignore
is great, because it always reminds you which tests were not run.
Does anyone have a best practice for running some of a test classes methods in JUnit 3?
Upvotes: 39
Views: 11636
Reputation: 29867
In order to conditionally ignore tests in Robotium / JUnit 3, I override runTest()
like
@Override
protected void runTest() throws Throwable {
// Do nothing if the precondition does not hold.
if (precondition) {
super.runTest();
}
}
Tests which are ignored this way will show up as "Success" in Eclipse, but as there is no "Ignored" state with JUnit 3, this is the best I was able to get.
Upvotes: 11
Reputation: 1
you can prepend the method with failing, so all methods like failingtest***() will be ignored during the junit run.
Upvotes: -1
Reputation: 47393
I don't know any other solution apart from commenting out tests or renaming them. I would go for the renaming option and use my own convention. For example all of them will start with ignoreXXX(). Then you can do one find/replace with your editor and you are ready.
Upvotes: 34