Kotlin Testing for Android

3 Days training

Transcript

1. T E S T I N G I N A N D R O I D K O T L I N
2. F R O M Z E R O T O O N E A N D O N E T O H E R O https://speakerdeck.com/werockstar/
3. @ W E R O C K S TA R K O T C H A P H A N M U A N G S A N
4. D AY 1 • The basic of unit testing • Contrasting unit and integrate test • Why we need to test and important • Intro JUnit4 • Basic Test fixture • Testing in pure kotlin • Testing exception
5. D AY 2 • What is the test? • Good test names • Good Unit Test • Understand Test Double • Mocking Dependency • Dependency Injection (DI) • Writing your own rule • Intro Mockito • Test as a Design Tools • Test as a Document • TDD - Test Driven Development
6. D AY 3 • Android Testing • Understand android structure • Why testing in android so hard • Understand pattern • Dependency Injection (Dagger2) • Prepare to stub, fake, mock, spy, dummy • Test Double in Android • Real world requirements unit test in Android
7. D AY 1
8. T H E B A S I C O F U N I T T E S T I N G
9. What is Unit Test?
10. R O Y O S H E R O V E T H E A U T H O R O F T H E A RT O F U N I T T E S T I N G “A unit test is a piece of code that invokes a unit of work and checks one specific end result of that unit of work.”
11. A unit is a method or function How much it call ‘unit’
12. Should be 10 lines? Do one thing and do thing very well? How many line of code in Method or Function?
13. Unit of work, that a unit can span as little as a single method and up to multiple classes and functions to achieve its purpose. Definition of Unit of Work
14. Integrate Testing R O Y O S H E R O V E T H E A U T H O R O F T H E A RT O F U N I T T E S T I N G “Integration testing is testing a unit of work without having full control over all of it and using one or more of its real dependencies, such as time, network, database, threads, random number generators, and so on.”
15. Unit Test vs Integrate Test Just unit test enough?
16. An integration test uses real dependencies; unit tests isolate the unit of work from its dependencies so that they’re easily consistent in their results and can easily control and simulate any aspect of the unit’s behavior. R O Y O S H E R O V E T H E A U T H O R O F T H E A RT O F U N I T T E S T I N G Summary
17. When you learn to write unit test
18. When you write unit test in real world
19. Introduction a very basic in JUnit4 “JUnit is a simple framework to write repeatable tests. It is an instance of the xUnit architecture for unit testing frameworks.”
20. Introduction a very basic in JUnit4
21. Try to test
22. I am @Test
23. Do the test (basic)
24. Do the test (basic)
25. Assertions
26. Basic Test fixtures
27. Write simple unit test
28. FizzBuzz 1, 2, Fizz, 4, Buzz, Fizz, 7, 8, Fizz, Buzz, 11, Fizz, 13, 14, Fizz Buzz, 16, 17, Fizz
29. Organizing test case AAA
30. Organizing your test case Arrange - Create/Prepare object or state Act - Exercise the code/action Assert - Verify code behaved as expect
31. Testing exception @Test(expected = Exception::class)
32. Testing exception Add throw exception in FizzBuzz
33. Parameterised https://github.com/Pragmatists/JUnitParams
34. D AY 2
35. Captcha บุตรแห่ง Twin Pattern Left Operator Right Result 1 1 1 1 One + 1 2 1 1 1 1 + One 1 2 1 2 Two + 2 2 2 1 2 2 + Two 1 1 2 1 One - 1 2 1 2 1 1 - One 1 1 3 1 One * 1
36. Captcha Captcha (pattern, left, operator, right) + getLeft ()
37. What is the test? As a Document executable As a Design
38. Type of testing Unit Test Integration Test End to End Test Manual Test
39. Type of testing Agile Testing book
40. Good test names Test name should express a specific requirement and should include the expected input or state and the expected result for that input or state.
41. Good test names 1. UnitOfWork_StateUnderTest_ExpectedBehavior 2. shouldExpectedBehaviorWhenUnitOfWorkOnStateUnderTest
42. Good test names 1. UnitOfWork_StateUnderTest_ExpectedBehavior - addItem_hasListOfSortedItems_listContainsAdditionalItemAndIsSorted - Kotlin add item has list of sorted items list contains additional item and is sorted
43. Good test names 2. shouldExpectedBehaviorWhenUnitOfWorkOnStateUnderTest - shouldContainAdditionalItemWhenAddItemOnList - Kotlin should contain additional item when add item on list
44. Good Unit Test 1. Trustworthy 2. Maintainable (Easy to detect) 3. Readable 4. Fast 5. Repeatable and Automated 6. Fully Isolated 7. Verify One concern (Focus) 8. No real dependencies, such as time, network, database, threads, random number generators
45. Code Quality Measurement
46. What is External dependency? An object in your system that your code under test interacts with and over which you have no control
47. Challenges with no control External dependency is challenges to software engineers for write unit test
48. Understand Test Double Stand-in for the real thing
49. Why Test Double matter
50. Why Test Double matter
51. Understand Test Double http://www.softwaretestingmagazine.com/knowledge/unit-testing-fakes-mocks- and-stubs/
52. Understand Test Double http://www.softwaretestingmagazine.com/knowledge/unit-testing-fakes-mocks- and-stubs/
53. Understand Test Double Dummy Just used to fill parameter lists (compiler happy) https://martinfowler.com/bliki/TestDouble.html
54. Understand Test Double Spy Record some information based on how they were called https://martinfowler.com/bliki/TestDouble.html
55. Why we should to break dependency - It’s out of our control - Hard to test (unit test) - Hard to config/Prepare data - Unit test should run so quickly
56. Direct dependency (Hard to simulate) FileManager + isExistFile(): Boolean FileSystem
57. Abstraction layer An abstraction layer or abstraction level is a way of hiding the implementation details of a particular set of functionality, allowing the separation of concerns to facilitate interoperability and platform independence. https://en.wikipedia.org/wiki/Abstraction_layer
58. SOLID principles Dependency Inversion principle Entities must depend on abstractions not on concretions. It states that the high level module must not depend on the low level module, but they should depend on abstractions.
61. Do the break dependency with indirect dependency IExtensionFile + isExistFile(): Boolean FileManager StubFileManager
62. Do the break dependency with indirect dependency BitmapProvider (fileManager: IExtensionFile)
63. Dependency Injection Class should not configure its dependencies statically but should be configure from the outside
64. Dependency Injection Dependency Inject
65. Mockito?
66. Mockito A mocking framework for unit tests for Java/Kotlin
67. Mockito
68. I am @Mock
69. Break dependency with Mockito
70. Playground Mockito
71. D AY 3
72. Testing on Android R U N O N J V M ( l o c a l u n i t t e s t s ) R E Q U I R E A N D R O I D ( i n s t r u m e n t a t i o n t e s t s ) module-name/src/test/java/. module-name/src/androidTest/java/
73. Testing on Android https://developer.android.com/training/testing/fundamentals
74. Testing on Android https://developer.android.com/training/testing/fundamentals Small tests Medium tests Large tests
75. Testing on Android https://developer.android.com/training/testing/fundamentals Small tests - 70 percent Medium tests - 20 percent Large tests - 10 percent
76. Testing on Android https://developer.android.com/training/testing/fundamentals Mockito JUnit Robolectric Espresso UIAutomator Android Test Orchestrator
77. How to write good unit test in Android - Understand your framework? - Understand your architecture? - Understand your requirements?
78. Popular in Android Architecture MVP MVC MVVM Clean Architecture VIPER
79. Refactoring to Simple Pattern V I E W M O D E L P R E S E N T E R A N D R O I D P U R E K O T L I N A N D R O I D
80. Understand android framework A C T I V I T Y F R A G M E N T
81. Real World practice
82. Unit Test on Sharedpreference
83. Unit Test on xPresenter
84. Reactive Programming Reactive programming is a general programming term that is focused on reacting to changes, such as data values or events - Ben Christensen
85. Unit Test on RxJava
86. Unit Test on Router Activity
87. Unit Test on Face Detection
88. Unit Test on RxPermission
89. - The art of Unit Testing - Clean Code - Test Driven: Practical TDD and Acceptance TDD for Java Developers - Effective Unit Test - xUnit Test Patterns - Android Architecture Components Future Read