A Guide to Unit Testing Architecture Components

Transcript

1. A Guide to Unit Testing Architecture Components
2. HELLO! I am Jabez Magomere (Mc JB) Android Developer and Student (CS) 2 https://github.com/JabezNzomo99 @mc_jayb
3. 3 Why Test? Testing is a good software practice that helps level-up a team’s and an individual’s productivity and efficiency.
4. 4 Why Test? Prevent unforeseen bugs in an application by testing for all extreme use cases.
5. 5 Get notified of any changes that breaks code (CI/CD) Why Test?
6. 6 Why Test? To write beautiful and clean code.
7. 7 TESTING MYTHS
8. 8 TESTING SLOWS DOWN DEVELOPMENT
9. 9 TESTING IS HARD
10. 10 TEST CODE IS NOT PRODUCTION CODE
11. 11 Factors to consider when writing tests • Scope • Fidelity • Speed
13. 13 Architecture Components • LiveData • Room • View Model • Data binding • Life Cycle • Navigation
15. 15 Unit Testing Room
16. 16 Unit Testing Room Testing points Test the behaviour your database query functions in the DAOs. Insert, Delete, Get. etc
17. 17 Unit Testing Room Testing Tools Room.inMemoryDatabase Builder() AndroidX Test Robolectric 4.0 Hamcrest/Assert J
18. 18 Unit Testing LiveData
19. 19 Unit Testing LiveData Testing Tools Room.inMemoryDatabaseBuilder() AndroidX Test Robolectric 4.0 MockK/Mockito Hamcrest/Assert J Junit4/Junit5
20. 20 Unit Testing View Model
21. 21 Additional Resources 1. https://developer.android.com/training/testing/set-up-proje ct 2. https://medium.com/@boonkeat/android-unit-testing-with-j unit5-d1b8f9c620b6?source=email-444c006a35b8-1565059 737888-digest.reader------0-58------------------8bc853b8_1882_45 2b_ac63_879f881bb444-1&sectionName=top
22. THANKS! Any questions? 22