I found the problem. It was missed code in build.gradle in the main module. If you have this problem I advise to start with adding this line: android { … defaultConfig { … testInstrumentationRunner ‘android.support.test.runner.AndroidJUnitRunner’ } … }
You can do that by instantiating your main class with parametrized constructor in your junit and then creating a spy from it. Let’s suppose your main class is A. Where B and C are its dependencies public class A { private B b; private C c; public A(B b,C c) { this.b=b; this.c=c; } void … Read more
You can use java system properties to achieve this. Simply pass what you need with -Dconnectionstring=foobar in the junit command line, or use the java api for system properties to set this programmatically, with System.setProperty(String name, String value), and System.getProperty(String name). In your tests, you can use the @Before or @BeforeClass to set up common … Read more
Add the @DirtiesContext annotation, but provide it with the AFTER_EACH_TEST_METHOD classMode @DirtiesContext(classMode = DirtiesContext.ClassMode.AFTER_EACH_TEST_METHOD)
You should also mock the next() method to have it return true the first time it’s called, as mockito will return false by default. Mockito.when(resultSetMock.next()).thenReturn(true).thenReturn(false);
Official way with selecting providers. You can also specify multiple providers as dependencies, and they will all be run and produce a common report. This may be especially handy with external providers, since there are few use-cases for combining the included providers. <plugin> <artifactId>maven-surefire-plugin</artifactId> <version>2.18.1</version> <dependencies> <dependency> <groupId>org.apache.maven.surefire</groupId> <artifactId>surefire-junit47</artifactId> <version>2.18.1</version> </dependency> <dependency> <groupId>org.apache.maven.surefire</groupId> <artifactId>surefire-testng</artifactId> <version>2.18.1</version> … Read more
The problem is that your AnnounceThreadTest extends TestCase. Because it extends TestCase, the JUnit Runner is treating it as a JUnit 3.8 test, and the test is running because it starts with the word test, hiding the fact that the @Test annotiation is in fact not being used at all. To fix this, remove the … Read more
Access MainConfig.xml directly. The src/test/resources directory contents are placed in the root of your CLASSPATH. More precisely: contents of src/test/resources are copied into target/test-classes, so if you have the following project structure: . └── src └── test ├── java │ └── foo │ └── C.java └── resources ├── a.xml └── foo └── b.xml It will … Read more
As mentioned in the discussion: WEB-INF is not really part of the class path. If you use a common template, such as maven, use src/main/resources or src/test/resources to place the app-context.xml in. Then you can use classpath:. Place your config file in src/main/resources/app-context.xml and use the following code: @RunWith(SpringJUnit4ClassRunner.class) @ContextConfiguration(locations = “classpath:app-context.xml”) public class PersonControllerTest … Read more
This is caused by Android Studio trying to execute an instrumentation test as a JUnit test. I had to go to ‘Edit Configurations…’ and delete the configuration from Android JUnit group and manually add to the ‘Android Instrumented Tests’ group. After this I had no problem executing the tests. In Android Studio, click Run > … Read more