spring-test

My Spring-Boot-Mvc-Web application has the following database configuration in application.properties file: spring.datasource.url=jdbc:h2:tcp://localhost/~/pdk spring.datasource.username=sa spring.datasource.password= spring.datasource.driver-class-name=org.h2.Driver this is the only config I made. No any other configurations made by me anywhere. Nevertheless the Spring and subsystems are automatically recreate database on each web application run. Database is recreated namely on system run while it contains data after application ends. I was not understanding this defaults and was expecting

On my spring boot application I want to override just one of my @Configuration classes with a test configuration (in particular my @EnableAuthorizationServer @Configuration class), on all of my tests. So far after an overview of spring boot testing features and spring integration testing features no straightforward solution has surfaced: @TestConfiguration : It's for extending, not overriding; @ContextConfiguration(classes=…​) and @SpringApplicationConfiguration(classes =…​) lets me override the whole config, not just the one class; An inner @Configuration class inside a @Test is suggested to

I have following test class @RunWith(SpringJUnit4ClassRunner.class) @ContextConfiguration(locations = {"/services-test-config.xml"}) public class MySericeTest { @Autowired MyService service; ... } Is it possible to access services-test-config.xml programmatically in one of such methods? Like: ApplicationContext ctx = somehowGetContext(); Daff Since the tests will be instantiated like a Spring bean too, you just need to implement the ApplicationContextAware interface: @RunWith(SpringJUnit4ClassRunner.class) @ContextConfiguration(locations = {"/services-test-config.xml"}) public class

In our Spring web applications, we use the Spring bean profiles to differentiate three scenarios: development, integration, and production. We use them to connect to different databases or set other constants. Using Spring bean profiles works very well for the changing the web app environment. The problem we have is when our integration test code needs change for the environment. In these cases, the integration test loads the application context of the web app. This way we don't have to redefine database connections, constants, etc. (applying the DRY principle). We setup our integration tests

we are using Spring for my application purposes, and Spring Testing framework for unit tests. We have a small problem though: the application code loads a Spring application context from a list of locations (xml files) in the classpath. But when we run our unit tests, we want some of the Spring beans to be mocks instead of full-fledged implementation classes. Moreover, for some unit tests we want some beans to become mocks, while for other unit tests we want other beans to become mocks, as we are testing different layers of the application. All this means I want to redefine specific beans of

I'm trying to combine the follow annotations: org.springframework.test.context.jdbc.Sql and org.junit.Before Like the follow code: @Test @Sql(scripts = "dml-parametro.sql") public void testData(){ Iterable<Parametro> parametros = parametroService.findAll(); List<Parametro> parametrosList = Lists.newArrayList(parametros); Assert.assertThat(parametrosList.size(), Is.is(1)); } @Before public void beforeMethod() { JdbcTestUtils.deleteFromTables(jdbcTemplate, "PARAMETRO"); } The code in the method @Before is running after then the script "dml-parametro.sql" in the @Sql annotation. Is it right to do

I have a session scoped bean which holds user data per http session. I would like to write a Junit test case to test the session scoped bean. I would like to write the test case such that it can prove that the beans are getting created per session. Any pointer as how to write such Junit test case? In order to use request and session scopes in unit test you need to: register these scopes in application context create mock session and request register mock request via RequestContextHolder Something like this (assume that you use Spring TestContext to run your tests): abstractSessionTest.xml :