alfredodiaz / therore-spring-mockito Goto Github PK

Hi Alfredo

I have come across your repo and the solution in this repo https://github.com/hobo05/mockitobeans in my attempt to achieve some easy mocking in my Spring integration tests.
All though yours is a bit different from the MockitoBeans, I still wanted to post my question to you here.

Using the MockitoBeans approach I have two integration test classes associated with a Spring Boot application.
Each of the test classes have the @MockedBeans but each with different mocked classes.
For instance TestClassA has a BeanA which it wants mocked and TestClassB has a BeanB which it wants mocked.
However, when I run either test, both @MockedBeans occurrences are picked up by the registrator and thus both mocks are created and the actual beans are not available in either test.

I would like to be able to scope the effect of the @MockedBean so that it only registers what is on the test class being executed.

Would that be possible with your solution?

If not, I would very much appreciate any advice you might have as to how it might be possible inside the Bean registrator class to get information about the current JUnit test being executed.
My idea is that if JUnit can provide the name of the test about to be run, then it would be easy to simply just register mocks for that given class and ignore the rest of the mock enabled test classes.
My assumption here is that when a full mvn test run is executed, the mocks are loaded for each test so that this strategy would also work when running all tests and not just a single one.

@hobo05 had an idea about filtering away other test classes which have the @MockedBean in the ComponentScan. That approach might work, but I would prefer a solution which is least intrusive to the test code - meaning that fewer lines of code are to prefer.

Again, thank you for your time.