Testing/Overriding Modules

Apologies if this is a dup (couldn’t see an open issue).

Is there any standard way to do testing. Overriding @Provides or extending module classes.
I know it was discussed by Jake at Devvox that it still needs fleshing out.

What are the current thoughts? This for me is the only real blocker. I can work around the limitations, but it feels like yak-shaving.

[mheras]

I still think there is no easy and clean way to do it in Android…

[NitroG42]

The documentation makes it a lot better but I still can’t figure out how to do that when we have component dependencies/subcomponent. Basically, if I have an AppComponent (containing the context, for example), and a NetworkComponent that requires a context (that is provided by a module of AppComponent). I want to replace the NetworkComponent by a MockNetworkComponent. I tried both solution (component dependencies/subcomponent), and none worked :

• With NetworkComponent being a subcomponent, MockNetworkComponent needs to have the same module than NetworkComponent… (so I can’t use MockNetworkModule, I have to use NetworkModule that provide the real implementation).
• WIth component dependencies, I have to instantiate the DaggerNetworkComponent directly so it’s hard to use DaggerDebugNetworkComponent instead.

Does someone have a solution ? I’m not far from trying Dagger 1 at this point.