Having searched Google for an answer, this looks like it might have something to do with Android development tools. Below are steps taken from this comment thread: Right click on the project -> run -> run configuration Select your Junit project Go to the classpath tab remove the Android framework entry select bootstrap entries click … Read more
Your kind of situation is awkward, as it feels bad to keep duplicating work in order to isolate the tests (see below) – but note that most of the duplication can be pulled out into setUp and tearDown (@Before, @After) methods, so you don’t need much extra code. Provided that the tests are not running … Read more
It is because of test isolation. No test should depend on another.
Write a @BeforeClass method in the AllTests class which will be executed when the suite is started. public class MyTests1 { @BeforeClass public static void beforeClass() { System.out.println(“MyTests1.beforeClass”); } @Before public void before() { System.out.println(“MyTests1.before”); } @AfterClass public static void afterClass() { System.out.println(“MyTests1.AfterClass”); } @After public void after() { System.out.println(“MyTests1.after”); } @Test public void test1() … Read more
This (old) JUnit best practices article puts it like this: Do not use the test-case constructor to set up a test case Setting up a test case in the constructor is not a good idea. Consider: public class SomeTest extends TestCase public SomeTest (String testName) { super (testName); // Perform test set-up } } Imagine … Read more
You should annontate your class with @RunWith(Enclosed.class), and like others said, declare the inner classes as static: @RunWith(Enclosed.class) public class DogTests { public static class BarkTests { @Test public void quietBark_IsAtLeastAudible() { } @Test public void loudBark_ScaresAveragePerson() { } } public static class EatTests { @Test public void normalFood_IsEaten() { } @Test public void badFood_ThrowsFit() … Read more
It’s deprecated because of the double’s precision problems. If you note, there’s another method assertEquals(double expected, double actual, double delta) which allows a delta precision loss. JavaDoc: Asserts that two doubles are equal to within a positive delta. If they are not, an AssertionError is thrown. If the expected value is infinity then the delta … Read more
Right, I got it working with <batchtest> quite simply: <junit showoutput=”true” printsummary=”yes” fork=”yes”> <formatter type=”xml”/> <classpath refid=”test.classpath”/> <batchtest todir=”${test.reports}”> <fileset dir=”${classes}”> <include name=”**/FastTestSuite.class”/> </fileset> </batchtest> </junit> I had tried <batchtest> earlier, but had made the silly mistake of using “**/FastTestSuite.java” instead of “**/FastTestSuite.class” in the <include> element… Sorry about that 🙂 NB: it’s necessary to … 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
The old method (of JUnit 3) was to mark the test-classes by extending junit.framework.TestCase. That inherited junit.framework.Assert itself and your test class gained the ability to call the assert methods this way. Since version 4 of JUnit, the framework uses Annotations for marking tests. So you no longer need to extend TestCase. But that means, … Read more