test driven development
A test-first workflow for turning a specific behavior requirement into an observable failing case and a focused implementation.
Repository star change: +1264 over 41.38 hours. 2026-10-31
Test Dart logic with focused fixtures, readable organization and meaningful assertions.
Editorial note checked 2026-10-29 against this instruction snapshot. Supporting scripts and runtime behavior remain outside this editorial review.
The guide covers package:test structure, test execution and optional mocking. It is useful for a concrete function or class behavior rather than creating tests that simply mirror implementation details.
Dart developers adding a feature or preventing a reproduced regression.
Mocks can conceal incorrect integration assumptions. Passing assertions provide little value if they do not exercise the behavior users depend on.
Unknown; inspect source requirements and supporting scripts.
Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.
npx skills add https://github.com/flutter/agent-plugins/tree/1bd8f2caa144c11b9153706c8de5f6d3e074b799/skills/dart-add-unit-test --skill dart-add-unit-testReview pinned skill folder ↗ · CLI documentation ↗
After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.
Static review only. This is not a security audit or a guarantee of safety.
SKILL.md text only; scripts, dependencies and runtime behavior not audited.
No configured text patterns matched. Unmatched or concealed behavior can still exist.
Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.
78/100 · Metadata coverage 80% · Model 1.0
Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.
Bounded source inspection, not a runtime security audit. This inspection does not execute code.
0 text files inspected at this exact repository snapshot. 0 files outside the inspection budget or type allowlist. Dependencies were not installed or independently audited.
Absence of a pattern is not proof of safety. Permission needs and runtime behavior remain Unknown.
Identify the expected behavior and failure case, construct minimal inputs and isolate only genuinely external dependencies.
Run the targeted test and confirm that it fails against the known broken behavior, then inspect edge cases and asynchronous completion.
Related by category; compare scope and dependencies before choosing an alternative.
A test-first workflow for turning a specific behavior requirement into an observable failing case and a focused implementation.
Repository star change: +1264 over 41.38 hours. 2026-10-31
A completion-check workflow that ties a claim such as fixed, passing or deployed to fresh evidence from the relevant system.
Repository star change: +1264 over 41.38 hours. 2026-10-31
Explore ab test setup as a testing & qa workflow from sickn33/agentic-awesome-skills. Compare its source, maintenance and review signals before choosing it for your agent.
Repository star change: +147 over 41.38 hours. 2026-10-31
Design Dart command-line tools with explicit entrypoints, exit status and stream behavior.
Repository star change: +4 over 40.37 hours. 2026-10-31
Collect Dart coverage and verify that the resulting LCOV report represents the intended tests.
Repository star change: +4 over 40.37 hours. 2026-10-31
Trace a Dart runtime failure to its real stack and verify the corrected behavior.
Repository star change: +4 over 40.37 hours. 2026-10-31