robolectric VS Dagger2

Robolectric

Do you use Robolectric to test string resolving?

@Config(instrumentedPackages = ["androidx.loader.content"]) is a workaround for https://github.com/robolectric/robolectric/issues/6593

There is also an issue with Robolectric which can be worked around by adding @Config(instrumentedPackages = ["androidx.loader.content"]) annotation to the test class.

If it's failing only on robo, this might be the cause: https://github.com/robolectric/robolectric/issues/6411

Unit tests. ~X0,000. These run on the jvm (not Android), via http://robolectric.org/

Take a look at http://robolectric.org. It has a specific JUnitRunner class for running unit tests in the test package with shadow classes for Android objects like application context. It is broadly used and there are a lot of examples on github and robolectric provides several themselves

There used to be a thing called "releasable references" which was that. It was removed, though: https://github.com/google/dagger/issues/1117

As said in the title, we will focus on the dependency inversion principle and one of its application : dependency injection. For production-ready applications, it would be better to rely on a framework and not implement its own container. For it, the java ecosystem have 3 frameworks available : Spring, Guice and Dagger.

At Reddit, we use Dagger 2 for handling dependency injection (DI) in our Android application. As we’ve scaled the application over the years, we’ve accrued a bit of technical debt in how we have approached this problem.

Confusing. I initially thought someone ported the Dagger DI framework to Python: https://dagger.dev/

I'm currently using Dagger and Anvil for my DI needs. It's been working really well, especially around what Anvil permits in terms of multibindings defined on the type declaration rather than in a module. For example:

Great job, I have been waiting for this feature/fix for a long time https://github.com/google/dagger/issues/2328

Dagger