Hilt testing best practices - MAD Skills

Welcome to the testing episode of the Modern Android Development Skills series on Hilt. In this episode, Dagger and Hilt Engineer Eric Chang will discuss Hilt's approach to testing, how to write tests in Hilt, and best practices/tradeoffs to evaluate when testing with Hilt.
Hilt testing documentation → goo.gle/3ytDXGf
Hilt testing guide → goo.gle/hilt-t...
Catch more videos on Hilt for MAD Skills → goo.gle/hilt-mad
Watch more MAD Skills episodes → goo.gle/madskills
Subscribe to Android Developers → goo.gle/Androi...
#Featured #Latest #Hilt
product: Android - General; re_ty: Publish;

[@calmrelaxingmusicchannel6933]

Thank you for sharing this information; it is very valuable.

[@ramonjaime3066]

Ohoh y

[@ChrisAthanas]

This assumes a tremendous set of knowledge Any resources recommended to get near this level?

[@rahul_bali]

Write unit tests and read books about software testing.

[@emirua]

Great info and explanation! Thanks!

[@BoobalanMunusamy]

This is instrumentation test, how about JUnit test cases? Looks like android studio doesn't consider the instrumentation test cases for code coverage

[@vyli1]

on top of that, instrumentation tests are slower to run than unit tests. Unit tests should be preferred where possible.

[@EricDeWildt]

Depending on an interface allows for injecting fakes. No mocks needed. Interfaces FTW.

[@mirhamamidboy7725]

please breing help me install sdk

[@witoldsienski1709]

Thanks for material :)

[@gekylafas]

I am still not convinced that a DI framework is worth the trouble, even Hilt still adds a lot of boilerplate code. I switched from Java to Kotlin precisely to avoid that. About 0:50: using mocks for the dependencies in tests allows you to verify your object's calls to those dependencies. You can't do that with real objects. The "more code coverage" argument seems to be moot, as long as you have tests for the dependencies as well. Using mocks also allows (and even forces) you to have tests that are really focused on the object at hand and not test its dependencies as well. And what about the case where the dependencies are objects from another library? Isn't it better to use mocks for them as well?

[@savazhkin]

Why KZbin provides only Korean subtitles for this video?

[@baadrqaaba9529]

Thank you for enhancing my knowledge