Road to 100% test coverage: myth or reality
summary
Claim: Very Good Ventures enforces 100% coverage and shows how to get there by fixing architecture, using dependency injection, and writing unit, widget and bloc tests. Tools used include mocktail (no codegen), bloc_test, a Very Good CLI plus an lcov-style reporter. Example app hits the Rick and Morty API with a client→repository→bloc→view stack, tests mock 200 vs non-200 responses, verify thrown exceptions and UI states, and the result is full coverage and higher deployment confidence.
AI-written summary · about
chapters (19)
- 0:00Introduction and agenda
- 1:08Why testing matters
- 3:14Architecture and testing challenges
- 6:41Code coverage explained
- 9:12Why 100% coverage
- 11:24Three-layer architecture
- 13:51Unit test basics
- 16:19Mocking dependencies
- 18:45Widget testing basics
- 19:29Demo app overview
- 20:35Testing API client
- 23:23Mocking API responses
- 24:45Async test verification
- 26:53Testing repository layer
- 28:41Testing BLoC state management
- 30:24BLoC test scenarios
- 32:11Testing UI with widget tests
- 33:33Page view architecture
- 36:05Q&A and resources
related talks
10m99% is not enough - full test coverage and why it's awesome
01h 00mRequirement Coverage: Myth or an Ultimate Goal
51mDebunking Myths Around Test Coverage
03mTest coverage
48mTest Coverage Myth Busted: Test-to-Code Mapping and Test Impact Analytics
02h 46mThe Joy of Testing
27mQuest for Adequate Autotest Coverage
38mMutants to the rescue: How effective are your unit tests?