For junit4! This question deserves a new answer written for junit5. I realise this answer is written a couple years after the question, probably this feature wasn’t around then. But now, it’s easy to just do this: @Test public void test_array_pass() { List<String> actual = Arrays.asList(“fee”, “fi”, “foe”); List<String> expected = Arrays.asList(“fee”, “fi”, “foe”); assertThat(actual, … Read more
I agree with what @fge said, more over. Lets look at example. Consider you have a method: class A { public void foo(OtherClass other) { SomeData data = new SomeData(“Some inner data”); other.doSomething(data); } } Now if you want to check the inner data you can use the captor: // Create a mock of the … Read more
Use org.junit.Assert’s method assertArrayEquals: import org.junit.Assert; … Assert.assertArrayEquals( expectedResult, result ); If this method is not available, you may have accidentally imported the Assert class from junit.framework.
Had the same message. I had to remove the Run/Debug configuration. In my case, I ran the unit test as a local test before. After that I moved my test to the androidTest package and tried to run it again. Android Studio remembered the last run configuration so it tried to run it again as … Read more
If the contract of class A includes the fact that it calls method B of an object of type C, then you should test this by making a mock of type C, and verifying that method B has been called. This implies that the contract of class A has sufficient detail that it talks about … Read more
I did a similar thing a few months ago, and it turned out this simple format was enough for Hudson to accept it as a test protocol: <testsuite tests=”3″> <testcase classname=”foo1″ name=”ASuccessfulTest”/> <testcase classname=”foo2″ name=”AnotherSuccessfulTest”/> <testcase classname=”foo3″ name=”AFailingTest”> <failure type=”NotEnoughFoo”> details about failure </failure> </testcase> </testsuite> This question has answers with more details: Spec. for … Read more
Epsilon is the value that the 2 numbers can be off by. So it will assert to true as long as Math.abs(expected – actual) <= epsilon
You should always use .equals() when comparing Strings in Java. JUnit calls the .equals() method to determine equality in the method assertEquals(Object o1, Object o2). So, you are definitely safe using assertEquals(string1, string2). (Because Strings are Objects) Here is a link to a great Stackoverflow question regarding some of the differences between == and .equals().
This problem happens because Android Platform (android.jar) already contains JUnit classes. IDEA test runner loads these classes and sees that they are from the old JUnit, while you are trying to use annotated tests which is a feature of the new JUnit, therefore you get the error from the test runner. The solution is simple, … Read more
This feature has made it into JUnit 4.11. To use change the name of parameterized tests, you say: @Parameters(name=”namestring”) namestring is a string, which can have the following special placeholders: {index} – the index of this set of arguments. The default namestring is {index}. {0} – the first parameter value from this invocation of the … Read more