Testing Skill: Behavior-Driven Test Workflow
Write reliable tests for every feature, cover failure paths, and hit 80% coverage.
The skill is an internal testing guideline, no external permissions or sensitive data operations, but lacks disclosure of side effects (file writes, env vars), data-flow transparency, and rollback. Publisher identity unknown and unverified. Deduction applied.
Describes testing workflow and quality standards, but lacks concrete config files and examples, and only static review, no execution. Key paths (e.g., 80% coverage verification) not reproduced, failure feedback for abnormal inputs not specified. Deduction applied.
Applies to writing and running tests, but lacks clear non-fit boundaries, trigger conditions not precise enough. Also, no consideration for China network or Chinese language support, but as internal process impact is low. Deduction applied.
Structure clear with workflow, checklists, and common mistakes, but lacks versioning, changelog, maintenance responsibility, and install/dependency notes. License and provenance provided but not in skill file. Deduction applied.
Provides guidance, but actual effectiveness unverified, no example outputs. Static assessment cannot confirm direct usability or marginal value. Deduction applied.
Repo has CI workflows, but skill itself lacks independent tests or executable verification material. Static review cannot verify skill effectiveness. Deduction applied.
- This skill is an internal testing standard and may not apply to other projects or environments.
- Publisher identity is not verified; exercise caution when using or relying on it.
- Test commands and configurations mentioned need validation in the project environment; universality not guaranteed.
- Coverage and workflow claims are not executed or verified; test yourself.
What does this skill do, and when should you use it?
A skill defining standards and workflow for writing and running tests. It mandates that every feature must be tested and guides developers to first list risk scenarios, write tests describing behavior rather than implementation, and ensure each describe block covers at least one failure path. The skill specifies a directory structure, two test environments (node and jsdom), and running tests with bun and Vitest 4. It aims to guarantee that before committing code, all new features and modified logic have proper test coverage, with a target of at least 80% coverage.
Enforces test writing: before adding a new feature, modifying existing logic, or claiming task completion, tests must be written. It provides a standard for writing tests, including describing behavior, covering failure paths, and keeping tests focused. It defines a test directory structure (unit, integration, regression, e2e) and file naming conventions (*.test.ts and *.dom.test.ts). It requires running all tests with bun run test, checking coverage with bun run test:coverage, and ensuring new source files are not excluded from coverage.
- When a developer adds a new feature and needs to write tests, the skill provides guidance.
- When a developer modifies existing logic and needs to update tests, the skill provides a process.
- When a developer needs to ensure test coverage before committing code, the skill provides a checklist.
- When a developer needs to write tests for high-risk scenarios (e.g., dependencies returning undefined or throwing), the skill advises starting from risk.
What are this skill's strengths and limitations?
- Clear behavior-driven testing standards, avoiding implementation details.
- Mandates failure-path testing, reducing untested risks.
- Provides detailed directory structure and naming conventions for organization.
- Includes coverage targets and commands to quantify test quality.
- Only applicable to projects using Vitest and bun, not other frameworks.
- Skill does not provide example commands with context (e.g., test configuration), may need extra setup.
- No mention of debugging steps when tests fail.
- Relies on the AionUi ecosystem; standalone use requires manual configuration.
How do you install this skill?
This skill is part of the AionUi repository at .claude/skills/testing/SKILL.md. Install the AionUi desktop app, and the skill is available for supported CLI agents (e.g., Claude Code, Codex, Hermes Agent). For standalone use, place the SKILL.md into your project's .claude/skills/testing/ folder.
How do you use this skill?
Activate the skill on all new or modified logic. Follow the steps: 1. List risk scenarios; 2. Write behavior tests (at least one failure path per describe); 3. Run bun run test to verify; 4. Run bun run test:coverage to check coverage; 5. Update existing tests before commit. Announce at start: "I'm using testing skill to ensure proper test coverage."
How does this skill compare with similar options?
This skill is similar to Claude Code's own testing workflow but specifically targets Vitest and bun, whereas Claude Code typically supports broader test frameworks.