10 Dec
2012
10 Dec
'12
1:36 p.m.
Hi Jeremie,
On Dec 10, 2012, at 1:22 PM, jerem <jeremie.bousquet(a)gmail.com> wrote:
Hi,
I could workaround that quite easily, by adding the following in my setUp()
method, just before retrieving my class under tests from the component
manager:
getComponentManager().registerMockComponent(getMockery(),
LoggerManager.class);
But it seems to confirm that, for any reason, the LoggerManager was not
automatically mocked by AbstractBridgedComponentTestCase.
This is an old/legacy class and you should try to not use it.
That said it extends AbstractComponentTestCase which will register in the CM all annotated
components it finds in the CP.
The only reason it wouldn't register one component is because it's not in the CP.
So either you don't have that dep voluntarily in your pom.xml because it's a
runtime dep. You have 2 options:
1) add it as a test dep
2) do what you've done and mock the component.
Thanks
-Vincent