I've got the following test:
@Test(expected = IllegalStateException.class)
public void testKey() {
int key = 1;
this.finder(key);
}
But JUnit reports, that the test fails, although it throws — as expected — an IllegalStateException
.
Do I have to configure something else to make this run?
I run the test now with
@RunWith(Suite.class)
@SuiteClasses(Test.class)
public class TestSuite开发者_如何学Python {
}
like in this question, but am still not getting the desired result.
And when I remove the test
prefix I'm still getting an error.
I gotta say that I run these tests with Eclipse, but it's configured to use the JUnit 4 Runner.
The problem was, that the class in which the test was nested was an extension of TestCase
. Since this is JUnit 3 style, the annotation didn't work.
Now my test class is a class on its own.
@RunWith(JUnit4.class)
public class MyTestCaseBase extends TestCase
I also had problems with @Test(expected = ...) annotation when I extended TestCase class in my base test. Using @RunWith(JUnit4.class) helped instantly (not an extremely elegant solution, I admit)
i tried this one, and work perfectly as expected.
public class SampleClassTest {
@Test(expected = ArithmeticException.class )
public void lost(){
this.lost(0);
}
private void lost(int i) throws ArithmeticException {
System.out.println(3/i);
}
}
also ensure that junit4 is added as dependancy, @ (annotations) are new feature in junit 4.
I faced same issue, solution is simple "Don't extends TestCase class"
No, this JUnit test should work as it is - there is nothing more needed on this side.
What makes you sure that the test throws an IllegalStateException
? Is it possible that it gets wrapped into another exception of different type?
Please post the exact failure message from JUnit.
As @duffymo suggested, it is easy to verify what (if any) exception the test really throws.
I had the same problem I just changed my imports statements. I removed :
import org.junit.jupiter.api.Test;
import junit.framework.TestCase;
and added :
import org.junit.Test;
And it worked fine for me.
This looks correct to me.
Check your assumptions. Are you sure it throws the exception? If what you say is true, removing the expected from the annotation should make it fail.
I'd be stepping through the code with a debugger to see what's going on. I'll assume you have an IDE that will do so, like IntelliJ.
Just tested this under JUnit4: this DO work, test completes successfully. Look if it is a Illegal
Selector
Exception
or such.
精彩评论