spring-test

I have a spring-boot application for which I am writing IT tests. The data for the tests comes from application-dev.properties when I activate dev profile Here is what I have for tests: @RunWith(SpringRunner.class) @SpringBootTest @WebAppConfiguration public class ApplicationTests { @Autowired Environment env; @Test public void contextLoads() { System.out.println(Arrays.toString((env.getActiveProfiles()))); } } ServiceITTest public class ServiceITTest extends ApplicationTests { @value String username; @value String address; @Autowired MyService myService; @Test public void check_for_valid

Hi I am trying to so spring junit test cases... and I require my full application context to be loaded. However the junit test does not initialize the full application context. Test class: @RunWith(SpringJUnit4ClassRunner.class) @SpringApplicationConfiguration(classes = Application.class) public class MongoDbRepositoryTest { @Value("${spring.datasource.url}") private String databaseUrl; @Inject private ApplicationContext appContext; @Test public void testCRUD() { System.out.println("spring.datasource.url:" + databaseUrl); showBeansIntialised(); assertEquals(1, 1); } private void

What is the difference between the @SpyBean and @MockBean annotations in Mockito? I have already gone through the JavaDoc but didn't get the difference. If possible please give an example when to use MockBean and when SpyBean . A mock (no matter if we talk about ordinary objects or beans) is simply an "empty shell". That mock object doesn't have any relation to the underlying production code. It is an object that looks like being an object of class X. But none of the methods or fields that X has do "really" exist on that mocked thing. Whereas a spy wraps around an existing object of your class

I am trying to override a Spring bean during a test declared in a test configuration with the use of @Primary. One declaration is in the src/main/java path, the other, the primary, is in src/test/java path. However, Spring is intentionally replacing the primary bean with the the non-primary bean, the one I don't want to use for the test. If I simply comment out the production (src/main/java) configuration bean, it uses the primary test (src/main/test) bean in the test configuration as desired. (Clearly I can't comment out code every time I want to run a test.) From the logs: o.s.b.f.s

I have a set of tests based which need a spring context. For fast test execution I want to make sure that the Spring context is initialized just once, then all the tests should be run against this context, then it should shut down. I already tried the following approaches: Use @RunWith(SpringJUnit4ClassRunner.class) and @ContextConfiguration(MyAnnotatedConfig.class) to initialize the spring context Use a @RunWith(SpringJUnit4ClassRunner.class) and @TestExecutionListeners({MyTestExecutionListener.class}) with a handwritten test execution listener that initializes the spring context and injects

We are arguing about this approach with my colleagues. They say to use SpringRunner only on integration or functional levels. The question is what pros and cons of using it in level below? For example I have simple bean: public class RewardDurationCalculator { private Clock clock; public OptionalLong calculate(DurationType durationType, List<Pass> passes) { long now = Instant.now(clock).getEpochSecond(); switch (durationType) { case FULL_PASS: return getCurrentPassDuration(passes, now); case TILL_THE_END_OF_THE_CURRENT_ACTIVE_PASS: return getTimeInCurrentPassLeft(passes, now); } return