Hilt quiz

Test your Hilt knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.

What does testability improvement typically look like when using Hilt-based dependency injection in an Android app, e.g. for unit testing a class that depends on a repository interface?

1. What does testability improvement typically look like when using Hilt-based dependency injection in an Android app, e.g. for unit testing a class that depends on a repository interface?
2. What does the `@InstallIn` annotation on a Hilt module specify?
3. What is Hilt?
4. What kind of dependency typically requires a Hilt module with `@Provides` rather than simple constructor injection with `@Inject`?
5. What does `@AndroidEntryPoint` do when applied to an Activity, Fragment, or other Android component?
6. What is a common reason Google recommends Hilt as the standard DI solution for new Android projects, rather than using raw Dagger directly?
7. What are Hilt's predefined scopes, like `@Singleton`, `@ActivityRetainedScoped`, or `@ViewModelScoped`, used for?
8. What does Hilt's component hierarchy (Application → Activity → Fragment/ViewModel, etc.) reflect about how Android apps are structured?
9. Why is Hilt's compile-time code generation approach (as opposed to a runtime reflection-based DI approach) considered advantageous for Android specifically?
10. What is the purpose of the `@HiltAndroidApp` annotation in a Hilt-based Android application?
11. What is a realistic tradeoff a small, simple Android app with very few dependencies might weigh before adopting Hilt?
12. What is Hilt's support for testing (e.g. `@HiltAndroidTest` and test-specific modules) generally used for?

More quizzes