title: WebMvcTest is too greedy
body: <p>I want to write a <code>WebMvcTest</code> test for a single controller in my Spring Boot application. Among other things there are some custom <code>Converters</code> in my application. Although they are not needed for this particular controller that I want to test, Spring tries to create them anyway.</p>
  
  <p>Now the problem: those custom converters require more beans from my application which are not initialised by <code>WebMvcTest</code> test slice. And don't want to mock tens of beans which are completely irrelevant for the particular test. Apart from specifying them all manually in <code>excludeFilters</code>, what are best practises for excluding some web components from specific <code>WebMvcTest</code> tests?</p>