... didn't timestamp at first ... 12:26 Architecture components 12:44 MVVM: Model-View-ViewModel 13:43 Asynchronicity 14:37 Kotlin coroutines 15:02 Coroutine scopes, viewModelScope 16:10 User Journey 1: Creating a new task 16:33 Test Driven Development: cycle (units) in cycle (E2E) 17:08 E2E tests: be real, black box 18:07 E2E test of User Journey 1 19:31 Integration tests: grey box 20:24 Integration test for AddEditTask 21:27 Test Doubles are stand-ins for the real objects 25:58 Further decomposition, scope limiting 27:15 Extract interface then create a fake version 28:46 Unit tests: black box, test behavior not implementation 31:34 Flaky async tests, runBlocking 32:58 runBlockingTest 33:22 State 34:56 The line is blurry 36:05 Modularization is good 37:15 Document your test pyramid clearly 37:32 Local tests vs Instrumentation tests 38:07 AndroidX Test 39:11 Project Nitrogen

🙏 Jonathan and Ellen

Great speaker. No fluff. Easy to understand.

RIP Jonathan

Very nicely structured and well explained video. I have seen the previous talks of the same instructor and he is always good. Thanks for the video.

*Rest in Peace Gerrish Family.* 😫 So strange of a death.

rest in peace

3:52 Shouldn't the "Speed" label be replaced with something like "Duration"? Unit tests are the fastest.

Wow, the amount of AAAAA's and Ummmmm's are so low in his speech. Great speaker

Rip.

Is there a way to get the presentation? This type of video that hides the presentation is horrible, we can't follow what the speaker is talking about!

Here's the most optimal way that Google should implement building testable apps: First you need to designate a special folder in Android where developers can place files that they would use for testing. You should avoid the test folder that is currently used for unit testing because my solution would interfere with the normal functionality of that folder. Let's say Android designates a folder called "swap". The developer can create sub folders in this and place any source code files they want. These files will be used to swap out files either in the "main" folder or in one of the variant/flavor folders. You can even allow multiple versions of the same file exist but they would have to be placed in different folders if they have the same name. The developer then goes to the "Edit Configuration" menu item where they normally setup debugging configurations. If you click on a Edit Configuration and then on "app" (this is the default configuration), you will see 4 tabs (General, Miscellaneous, Debugging and Profiling). Now let's add a 5th tab called "Swap". When you click on this, it lists all the files located under the swap directory. Maybe show the files in the same tree structure as they appear under Project files. Next to each file is a checkbox. The developer then selects whatever files they want to use that will swap out any files during build. When the build is run, the Android plugin will check to see if a file that is to be compile exists under the swap folder that has been checked off in the app configuration settings. If so, it uses that instead of the one it would normally use. This solution allows the user to create multiple debug configurations that can contain combinations of swap files that are needed for testing. It also eliminates the need for dependency injection. Say good-bye to Dagger, which is nothing more than a band-aid that should never have been introduced to Android to start with.

I couldn't find the codelab for this talk since the one provided in the video gave me 404, can anyone please provide me the link to it?

Testing is scary...

I can't find this app sample in the android-test repository. Can someone helps me and provide the link??

"databinding" eww