What problem does it solve?
This Skill eliminates inconsistent, insufficient, or incorrect testing practices in the Cambridge Beer Festival Flutter app, preventing developers from claiming untested changes are verified, skipping required test layers, or missing accessibility and coverage requirements before merging.
Core Features & Use Cases
- Evidence-based test hierarchy: Ranks test types by proof strength, from unit/widget tests down to manual testing, with clear guidance on which layer to use for each change.
- Copy-paste test skeletons: Provides verified, working examples for every test type in the repo, including model parsing, controller unit tests, provider tests, widget tests, golden screenshots, semantics tests, and worker tests.
- TDD and definition of done guidance: Includes a red/green/refactor workflow for bug fixes, acceptance thresholds for coverage and formatting, and clear rules for what counts as verified (including what agents cannot manually confirm).
- Use Case: A developer fixing a drink filtering bug can use this Skill to write a correct deep widget test that verifies the UI updates (not just internal state), confirm the change meets the 70% coverage threshold, and add the required accessibility semantics test before merging.
Quick Start
Use the validation-and-qa skill to write a correct widget test for the new drink favorite toggle feature, following the deep test doctrine and provided test skeleton.