The maven-surefire-plugin, as of today, does not have full support of JUnit 5. There is an open issue about adding this support in SUREFIRE-1206. As such, you need to use a custom provider. One has already been developed by the JUnit team; from the user guide, you need to add the junit-platform-surefire-provider provider and the … Read more
The easiest (as in least amount of new code required) way to do this is to run the test as a parametrized test (annotate with an @RunWith(Parameterized.class) and add a method to provide 10 empty parameters). That way the framework will run the test 10 times. This test would need to be the only test … Read more
sample tests: tests.py: # tests.py import random try: import unittest2 as unittest except ImportError: import unittest class SimpleTest(unittest.TestCase): @unittest.skip(“demonstrating skipping”) def test_skipped(self): self.fail(“shouldn’t happen”) def test_pass(self): self.assertEqual(10, 7 + 3) def test_fail(self): self.assertEqual(11, 7 + 3) JUnit with pytest run the tests with: py.test –junitxml results.xml tests.py results.xml: <?xml version=”1.0″ encoding=”utf-8″?> <testsuite errors=”0″ failures=”1″ name=”pytest” … Read more
Well there’s always assertThat(list.isEmpty(), is(false)); … but I’m guessing that’s not quite what you meant 🙂 Alternatively: assertThat((Collection)list, is(not(empty()))); empty() is a static in the Matchers class. Note the need to cast the list to Collection, thanks to Hamcrest 1.2’s wonky generics. The following imports can be used with hamcrest 1.3 import static org.hamcrest.Matchers.empty; import … Read more
The javax.mail-api artifact is only good for compiling against. You actually need to run code, so you need a complete implementation of JavaMail API. Use this: <dependency> <groupId>com.sun.mail</groupId> <artifactId>javax.mail</artifactId> <version>1.6.2</version> </dependency> NOTE: The version number will probably differ. Check the latest version here.
I had this issue and my problem was that I was calling my method with any() instead of anyInt(). So I had: doAnswer(…).with(myMockObject).thisFuncTakesAnInt(any()) and I had to change it to: doAnswer(…).with(myMockObject).thisFuncTakesAnInt(anyInt()) I have no idea why that produced a NullPointerException. Maybe this will help the next poor soul.
There is many correct answers here, but I would like to add my version too. This is based on Assertj. import static org.assertj.core.api.Assertions.assertThat; public class TestClass { public void test() { // do the actual test assertThat(actualObject) .isEqualToComparingFieldByFieldRecursively(expectedObject); } } UPDATE: In assertj v3.13.2 this method is deprecated as pointed out by Woodz in comment. … Read more
For the mocks initialization, using the runner or the MockitoAnnotations.initMocks are strictly equivalent solutions. From the javadoc of the MockitoJUnitRunner : JUnit 4.5 runner initializes mocks annotated with Mock, so that explicit usage of MockitoAnnotations.initMocks(Object) is not necessary. Mocks are initialized before each test method. The first solution (with the MockitoAnnotations.initMocks) could be used when … Read more
The @BeforeClass and @AfterClass annotated methods will be run exactly once during your test run – at the very beginning and end of the test as a whole, before anything else is run. In fact, they’re run before the test class is even constructed, which is why they must be declared static. The @Before and … Read more
Assuming the following method to test: public boolean doSomething(SomeClass arg); Mockito documentation says that you should not use captor in this way: when(someObject.doSomething(argumentCaptor.capture())).thenReturn(true); assertThat(argumentCaptor.getValue(), equalTo(expected)); Because you can just use matcher during stubbing: when(someObject.doSomething(eq(expected))).thenReturn(true); But verification is a different story. If your test needs to ensure that this method was called with a specific argument, … Read more