Junit tests are run in a different vm as the Eclipse IDE. So it is that vm that is out of memory and not the Eclipse one. You can change the settings of the test vm in the run configurations of the test. You go to the run configurations and then under arguments, you can … Read more
Solution for Spring 3.2 or newer Spring starting with version 3.2 provides support for session/request scoped beans for integration testing. @RunWith(SpringJUnit4ClassRunner.class) @ContextConfiguration(classes = TestConfig.class) @WebAppConfiguration public class SampleTest { @Autowired WebApplicationContext wac; @Autowired MockHttpServletRequest request; @Autowired MockHttpSession session; @Autowired MySessionBean mySessionBean; @Autowired MyRequestBean myRequestBean; @Test public void requestScope() throws Exception { assertThat(myRequestBean) .isSameAs(request.getAttribute(“myRequestBean”)); assertThat(myRequestBean) .isSameAs(wac.getBean(“myRequestBean”, … Read more
In a word – “don’t”, that way lays madness. What you really want is higher level tests that make use of your Spring configuration but are still focused on behaviour not implementation. For example, looking at your security configuration – you don’t really care that the configure method is called, or what it does, what … Read more
Based on your demo project, I was able to duplicate your error. That said, here are the revised changes I made, after my first failed attempt, to be able to build the project: I added the maven-compiler-plugin version 3.8.0 to all the modules. You need a version of 3.7 or higher to compile modules with … Read more
With jdk 6, the reflected fields are in deed in their declaration order. In early jdk that wasn’t the case. Apparently enough people have nagged. Although not guaranteed by javadoc, I would still take this order as granted, and I assume the order will be kept in future jdks too. In your app, like in … Read more
If you have an exception handler and you want to test for a specific exception, you could also assert that the instance is valid in the resolved exception. .andExpect(result -> assertTrue(result.getResolvedException() instanceof WhateverException)) UPDATE (gavenkoa) Don’t forget to inject @ExceptionHandler annotated methods to the test context or exception will occur at .perform() instead of capturing … Read more
To provide the input from a file, make a FileInputStream and set that as the System.in stream. You’ll probably want to set the original back after the main method has finished to make sure anything using it later still works (other tests, JUnit itself…) Here’s an example: @Test public void testMain() throws IOException { System.out.println(“main”); … Read more
This question might be old but since this was the nearest answer I found when I had this problem I though I’d describe my solution. Using JUnit 4 Split your tests up so that there is one test method per class (this solution only changes classloaders between classes, not between methods as the parent runner … Read more
That annotation tells PowerMock(ito) that the listed classes will need to be manipulated on the byte code level. You need to “prepare for test” all these classes X of which you want to mock a static method (on X) gain control over calls to new() used in another class X gain control over private methods … Read more
As has been said in other responses, the order in which JUnit finds methods is not guaranteed, so the execution order of @Before methods can’t be guaranteed. The same is true of @Rule, it suffers from the same lack of guarantee. If this will always be the same code, then there isn’t any point in … Read more