I haven't found any examples on how to do this. I'm assuming it is not possible based on examples like this:
@Bean(MyImplementation.class)
MyInterface myInterface;
where the class to inject is already determined.
A complement to johncarl answer:
There's no way to tell AndroidAnnotations that you want to inject mocks instead of real objects, because it works at compile time, so the code must always be production ready.
I would recommend testing the generated activities, in complement with Robolectric. The annotations are adding behavior to your code, so you shouldn't test it as if there were no annotations.
Be careful of testing your activities behavior, not AndroidAnnotations' behavior. The framework already has tests of its own to check that the annotations work correctly :).
You can let AndroidAnnotations DI take place, and then reinject the mocked dependency. The fields have at least default scope, which mean they can be accessed from the same package, so you'd have to create the test in the same package as the activity.
MyActivity_ activity = new MyActivity_();
// myInterface gets injected
activity.onCreate(null);
// you reinject myInterface
activity.myInterface = Mockito.mock(MyInterface.class);
In AndroidAnnotations, dependencies are injected by calling MyImplementation_.getInstance_()
. You could use runtime bytecode manipulation with a tool such as PowerMock to let the getInstance_()
method of MyImplementation_
return a mock. This might require some initial work though, because you'd have to mix PowerMock test runner and Robolectric test runner.
Edit: I updated the documentation with content based on this question.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With