Rules are pretty easy to emulate, for example with super classes: public void Base { @BeforeMethod public void createTempDir() { … } @AfterMethod public void deleteTempDir() { … } } public void MyTest extends Base { @Test … } If you extend Base, a temporary directory will always be automatically created and then deleted. The … Read more
I prefer having one test case per method. First it is easier to see what cases are being tested if they are split into methods as opposed to looking for comments embedded in the code. Most IDEs will give you a summary of methods, so instead of saying “did I test edgecase XYZ?” and then … Read more
This blog helped fix the same problem for me: Mixing JUnit, Hamcrest and Mockito: Explaining java.lang.NoSuchMethodError: org/hamcrest/Matcher.describeMismatch Inside the dependencies for Mockito and Junit, the author added excludes: <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>4.11</version> <exclusions> <exclusion> <artifactId>hamcrest-core</artifactId> <groupId>org.hamcrest</groupId> </exclusion> </exclusions> </dependency>
If you’re using MAC, in my case, to solve the problem I had to add a link. Follow the command below: sudo ln -s $HOME/.docker/run/docker.sock /var/run/docker.sock
They have slightly different usages and I tend to use both in my projects. Mockito is used for making mocks of your classes. When you are testing a particular class you mock all of its dependencies with Mockito. Where possible most of your tests should use mockito. To make this possible most people split their … Read more
Java 5 annotations for setup and teardown (@before and @after) instead of setUp() and tearDown(). don’t need to extend TestCase anymore. @Test annotation replaces testSomeMethod() naming convention. static imports for asserts. Junit theories, which allow you to separate data sets from the test itself.
You should either use a static import: import static android.support.test.espresso.Espresso.onView; or import android.support.test.espresso.Espresso; and call it in the following way Espresso.onView()
If you are using Spring (the spring-test library specifically), you can simply use ReflectionTestUtils.setField instead of Whitebox.setInternalState
Make sure you have imported the correct package. If I remeber correctly there are two different packages for Autowiring. Should be :org.springframework.beans.factory.annotation.Autowired; Also this looks wierd to me : @ContextConfiguration(“classpath*:conf/components.xml”) Here is an example that works fine for me : @RunWith(SpringJUnit4ClassRunner.class) @ContextConfiguration(locations = { “/applicationContext_mock.xml” }) public class OwnerIntegrationTest { @Autowired OwnerService ownerService; @Before public … Read more
Actually they are technically the same. When Mockito was first created, we were talking about stubs, so the vocabulary followed that idea. Later people thought it was better to think in interactions rather that technical terms, so the vocabulary followed the when … then … style. This change in vocabulary helps people to think about … Read more