testing
Best for Feature development teamsWorks with GitHubLow risk
⌘source
- author
@iOfficeAI- repo
- iOfficeAI/AionUi
- language
- TypeScript
★22kstars
1.9kforks
Apr 19, 2026
✦overview.md
Key Features
- ·Vitest 4 framework with node and jsdom environments
- ·Structured test organization (unit, integration, regression, e2e)
- ·Clear trigger conditions for when to apply testing
- ·Standardized file naming conventions
- ·Focus on testing riskiest scenarios first
Use Cases
- →Writing new tests for a feature or bug fix
- →Adding a new feature that requires test coverage
- →Modifying logic that has existing tests
- →Ensuring test completion before committing code
- →Running tests before claiming work is complete
Best for
- ✓Feature development teams
- ✓Maintenance and refactoring work
- ✓CI/CD pipelines
Not ideal for
- !One-off scripts without test requirements
- !Projects without established test frameworks
FAQs
name
testing
description
Testing workflow and quality standards for writing and running tests.
Use when: (1) Writing new tests, (2) Adding a new feature that needs tests,
(3) Modifying logic that has existing tests, (4) Before claiming a task is complete.
Testing Skill
Standards and workflow for writing and running tests. Every feature must be tested.
Announce at start: "I'm using testing skill to ensure proper test coverage."
Trigger Conditions
- Writing new tests for a feature or bug fix
- Adding a new feature (must include tests)
- Modifying logic that has existing tests (must update them)
- Before claiming work is complete
- Before committing code
Framework
Vitest 4 — configured in vitest.config.ts.
Test Structure
tests/
├── unit/ # Individual functions, utilities, components
├── integration/ # IPC, database, service interactions
├── regression/ # Regression test cases
└── e2e/ # End-to-end tests (Playwright, playwright.config.ts)
Two Test Environments
| Environment | When | File naming |
|---|---|---|
node (default) | Main process, utilities, services | *.test.ts |
jsdom | DOM/browser-dependent code | *.dom.test.ts |
Workflow
Step 1: Identify What to Test
Before writing tests, list the riskiest scenarios first:
$install
1-click copynpx skills add iOfficeAI/AionUi --skill testingSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
4/ 5
highMostly actionable with clear steps; only a few small gaps remain.