feature-tests

You write outside-in integration tests for a Flutter feature slice by generating a markdown specification that exercises the feature through its public Cubit surface, using real production wiring for domain and data layers while mocking external boundaries like Dio.

Slice testing in Flutter is defining a single end-to-end scenario that validates a feature slice before code is written. You need it when you have prd.md, plan.md, requirements.md, and validation.md ready and want to establish a tests.md contract.

You generate a tests.md contract for a Flutter Cubit by using a feature-tests skill that transforms your slice's product, plan, requirements, and validation notes into a ready-to-save markdown test specification without generating any Dart implementation code.

Yes, you need prd.md, plan.md, requirements.md, and validation.md files present in your slice directory before generating a Flutter feature test specification, as these documents provide the necessary context for the end-to-end scenario.

You mock system boundaries like Dio in Flutter integration tests by distinguishing what should be wired real from what should be mocked at external services, keeping the domain and data layers wired with real production code while substituting system boundaries.

Slice tests differ from unit tests by exercising a feature end-to-end through its public Cubit surface with real domain and data wiring, whereas unit tests isolate individual components without validating the full feature behavior or system boundaries.