spring-test

So confusingly @IfProfileValue has nothing to do with @Profile or @ActiveProfiles . @Profile tests to see if a profile is active, @ActiveProfiles sets them as active, and @IfProfileValue allows you to check things in Spring Environment . Wut? I'd deprecate all of them and add new ones @IfEnvironment , @IfProfile , and @ActivateProfiles . Commentary aside, how can I use @IfProfileValue to detect whether i have a profile active? I am not using Spring Boot on this project, at this time. Answers should show code, and we will assume that I want the test to run if the profile is activated as

Situation: I am using Spring Cloud with Spring Boot in a microservice, that microservice is loading a DB config information to configure a connection. I created a test to get the rest interfaces using Swagger for documentation. I want to disable the loading of DB configuration because is not necessary. Here is the code: @WebAppConfiguration @RunWith(SpringJUnit4ClassRunner.class) @ContextConfiguration(classes = {Application.class, Swagger2MarkupTest.class}, loader = SpringApplicationContextLoader.class) @ActiveProfiles("test") public class Swagger2MarkupTest { @Autowired private

I'm pretty new to Mockito and have some trouble with clean up. I used to use JMock2 for unit tests. As far as I know, JMock2 preserves the expectations and other mock information in a context which will be rebuilt for every test method. Therefore every test method is not interfered by the others. I adopted the same strategy for spring tests when using JMock2, I found a potential problem with the strategies I used in my post : The application context is rebuilt for every test method and therefore slows the whole test procedure. I noticed many articles recommend using Mockito in spring tests and

I am testing my controller given below @Controller public class MasterController { @GetMapping("/") public String goLoginPage(){ return "index"; } } I am following this Spring documentation to test my controller. Now, I want to test my controller by just instantiating the web layer and not the whole Spring context as given in the documentation. Below is my code for the same. @RunWith(SpringRunner.class) @WebMvcTest public class MasterControllerTestWithWebLayer { @Autowired MockMvc mockMvc; @Autowired MasterController masterController; @Before public void setUp() throws Exception { } @After

I am looking for a way to simplify the following code. @WebAppConfiguration @RunWith(SpringJUnit4ClassRunner.class) @ContextConfiguration(classes = { // My configuration classes }) public class MyServiceTest { @Autowired private MyService service; @Test public void myTest() { Assert.assertTrue(service != null); } } I have many configuration classes and I don't want to put them into each test class. So I got the idea to create my own annotation: @WebAppConfiguration @RunWith(SpringJUnit4ClassRunner.class) @ContextConfiguration(classes = { // My configuration classes }) public @interface