In order to use @Rule, you require a class that implements TestRule(preferred) or MethodRule, as can be read here. Whereas @Before and @After require a new method to be written in every test case, @Rule does not because it is only an instantiation of already existing code. So, if you would use @Before and @After … Read more
I’m using JUnit 4.9. Will this help?: import junit.framework.TestCase; import org.junit.AfterClass; import org.junit.BeforeClass; import org.junit.runner.RunWith; import org.junit.runners.Suite; import org.junit.runners.Suite.SuiteClasses; @RunWith(Suite.class) @SuiteClasses({First.class,Second.class,Third.class}) public class RunTestSuite extends TestCase { @BeforeClass public static void doYourOneTimeSetup() { … } @AfterClass public static void doYourOneTimeTeardown() { … } } Edit: I am quite positive (unless I misunderstand your question) that … Read more
JUnit 5 provides a way out of the box. JUnit 5 = JUnit Platform + JUnit Jupiter + JUnit Vintage Each one is a distinct project and using all of them allows to compile and execute JUnit 4 and JUnit 5 tests in a same project. JUnit Jupiter is the combination of the new programming … Read more
To create a dynamic test suite, you need to use the @RunWith annotation. There are two common ways to use it: @RunWith(Suite.class) This allows you to specify, which classes compose the test suite in question. This is equivalent to the JUnit 3 style: import junit.framework.TestSuite; import junit.framework.TestCase; public final class MasterTester extends TestCase { public … Read more
You have to provide a delta to the assertion for Floats: Assert.assertEquals(expected, actual, delta) While delta is the maximum difference (delta) between expected and actual for which both numbers are still considered equal. Assert.assertEquals(0.0012f, 0.0014f, 0.0002); // true Assert.assertEquals(0.0012f, 0.0014f, 0.0001); //false
You could structure your test with the Enclosed runner. @RunWith(Enclosed.class) public class TestClass { @RunWith(Parameterized.class) public static class TheParameterizedPart { @Parameters public static Object[][] data() { … } @Test public void someTest() { … } @Test public void anotherTest() { … } } public static class NotParameterizedPart { @Test public void someTest() { … } … Read more
Make the method package-private and the test will be able to see it, if the test is in the corresponding test package (same package name as the production code). @VisibleForTesting Address getAddress() { return mAddress; } Also consider refactoring your code so you don’t need to explicitly test a private method, try testing the behaviour … Read more
assertTrue will fail if the second parameter evaluates to false (in other words, it ensures that the value is true). assertFalse does the opposite. assertTrue(“This will succeed.”, true); assertTrue(“This will fail!”, false); assertFalse(“This will succeed.”, false); assertFalse(“This will fail!”, true); As with many other things, the best way to become familiar with these methods is … Read more
ConfigurationManagerTest is not being found on your classpath. Ensure that the ConfigurationManagerTest.class file is available on your classpath. It might not exist if it wasn’t successfully compiled or if it’s being created in a directory that you haven’t told the Eclipse project should be on the classpath. Assuming that you’ve put your test classes in … Read more
You can do this using an ErrorCollector rule. To use it, first add the rule as a field in your test class: public class MyTest { @Rule public ErrorCollector collector = new ErrorCollector(); //…tests… } Then replace your asserts with calls to collector.checkThat(…). e.g. @Test public void myTest() { collector.checkThat(“a”, equalTo(“b”)); collector.checkThat(1, equalTo(2)); }