Android TDD
3 likes1,192 views
The document discusses the importance of testing in Android development, emphasizing test-driven development (TDD) to improve code architecture and reduce debugging time. It outlines various testing approaches and frameworks, such as JUnit and Robolectric, while also addressing challenges encountered during testing. Resources and readings for further information on testing practices are also provided.
Android TDD
- 1. Android TDD January 25, 2012 Chuck Greb @ecgreb
- 2. Why Test?
- 5. Reduce Cost
- 7. Test smallest possible units of code (in isolation)
- 8. Makes refactoring easier (regression suite)
- 14. Red -> Green -> Refactor
- 15. Tests must be fast!
- 16. Other kinds of tests?
- 19. QA Job Security
- 21. Testing Approaches ● F@#% It! ● Manual ● Monkey Testing ● Android Testing Framework ● JUnit 4 + POJOs ● Robolectric ● Custom
- 22. Testing Approaches ● F@#% It! ● Manual ● Monkey Testing ● Android Testing Framework ● JUnit 4 + POJOs ● Robolectric ● Custom
- 24. JUnit 3 + Instrumentation
- 26. Test Case Classes ● TestCase ● AndroidTestCase ● ActivityTestCase ● ActivityUnitTestCase ● ServiceTestCase ● ProviderTestCase2 ● ActivityInstrumentationTestCase2
- 27. Android Mocks
- 29. main.xml
- 30. StringBling
- 33. Success!!!
- 34. Compile, dex, package, and install two APKs on emulator or device
- 35. Additional Challenges ● Classes and methods declared final ● Lack of interfaces ● Non-public constructors ● Static methods
- 36. JUnit 4 + POJOs
- 39. StringBling
- 40. StringBlingTest
- 41. Success!!!
- 42. But we want to test ALL our code
- 43. Robolectric
- 44. Robolectric Test-Drive Your Android Code
- 46. Shadow Objects in Action
- 47. View and Resource Loading
- 49. Success!!!
- 50. More fun with Shadows
- 53. Write your own custom shadows
- 55. Resources ● developer.android.com/guide/topics/testing ● junit.org ● pivotal.github.com/robolectric
- 56. Reading ● Robert C. Martin (Uncle Bob) ● Michael Feathers ● Kent Beck
- 57. Find your testing Zen