slice-test-red

Generate executable Dart outside-in tests from a slice's tests.md specification.

2|Updated Aug 13, 2023
One-click install
npx skills add https://github.com/NNPopov/movie-theater-tickets --skill slice-test-red
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slice-test-red
Source: https://github.com/NNPopov/movie-theater-tickets/tree/main/src/clients/.claude/skills/slice-test-red
Command: npx skills add https://github.com/NNPopov/movie-theater-tickets --skill slice-test-red

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a slice's markdown test specification into an executable Dart outside-in test, so teams can lock in behavior before implementation begins.

Core Features & Use Cases

  • Spec to test translation: Converts a slice's tests.md scenarios into a runnable Flutter test file.
  • Real dependency wiring: Constructs the slice with real adapter, port, use case, and cubit objects while mocking only system boundaries.
  • Red-phase verification: Runs flutter test and confirms the new test fails for missing implementation rather than for a broken test.
  • Use case: Generate the failing test for a newly planned feature slice, then hand it off to implementation once the contract is clear.

Quick Start

Ask the skill to generate the red outside-in Dart test for the target slice from its tests.md specification and verify that flutter test fails for the expected implementation gap.

Frequently Asked Questions about slice-test-red

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate outside-in Dart tests for a Flutter feature slice?

You generate red outside-in Dart tests by providing a slice's tests.md specification, which the Skill translates into a runnable Flutter test file wiring real cubit, adapter, port, and use-case objects while mocking system boundaries.

How does outside-in TDD verification work for Flutter cubit workflows?

Outside-in TDD verification runs flutter test to confirm the generated executable test fails specifically due to missing implementation rather than a broken test, validating the red phase for cubit and use-case workflows.

Can I generate red-phase tests from a tests.md specification without manual dependency wiring?

No, generating red-phase tests requires manual dependency wiring to construct the slice with real adapter, port, use case, and cubit objects while mocking only system boundaries for accurate outside-in coverage.

What is the best way to lock in Flutter feature behavior before implementation begins?

The best way to lock in behavior is creating executable outside-in Dart tests from tests.md scenarios, establishing a clear contract for cubit and use-case workflows that fails until implementation is complete.

Why do my generated Flutter outside-in tests fail during red-phase TDD?

Generated outside-in tests fail during red-phase TDD because the executable Dart test expects implementation for the slice's cubit, adapter, port, and use-case workflows that does not yet exist, confirming the missing implementation gap.