Fantastic tests and where to find them
summary
Explains concrete rules: use FIRST and Kent Beck’s 12 test properties to prioritise speed, isolation and repeatability; prefer lightweight fakes over mocks to avoid brittle whenever setups and duplicated lines across modules; use MockWebServer plus real JSON to catch missing @SerialName bugs that mocks miss; favour one-assertion tests and small default-data builders for readable domain tests; split UI tests into pure view tests (single-state assertions) and a few flaky-prone integrated Espresso/Robolectric tests.
AI-written summary · about
chapters (8)
- 0:00Introduction and agenda
- 1:38Test fundamentals
- 8:48Test deserata and properties
- 15:18Classic testing concepts
- 21:52Network integration testing
- 23:00Domain layer testing
- 25:30Presentation layer testing
- 29:00Summary and Q&A
related talks
45mBuilding Tools to Free up Exploratory Testers
59m.NET Testing Techniques You Didn’t Know You Needed
36mCan You Read Your Tests? Clean and Useful Android Testing, with JUnit and Spock!
20mTesting to stop doubting: in search of the ideal test
27mFantastic Bugs And Where To Find Them by Iris Schaffer (Eng) | JSConfAM19
43mThe Little Shop of TDD Horrors
40mBenjamin Bischoff: Old Tools, New Tricks: Unleashing the Power of Time-Tested Testing Tools
02h 46mThe Joy of Testing