testing
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.
npx skills add iOfficeAI/AionUi --skill testing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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: - What happens when the dependency returns `undefined` / throws? - What happens at boundaries (empty lis
- Trigger Conditions
- Framework
- Test Structure
- Two Test Environments
- Workflow
- Step 1: Identify What to Test
- Step 2: Write Tests
- Step 3: Run Tests
- Step 4: Verify Coverage
- Step 5: Update Existing Tests
- Edge Case Checklist
- Quick Checklist
- Common Mistakes
bun run test # Run all tests (REQUIRED before every commit) bun run test:coverage # Check coverage (before opening a PR) bun run test -- --reporter=verbose # See which tests pass/fail with names
What does the testing skill do?
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.
How do I install it?
Run `npx skills add iOfficeAI/AionUi --skill testing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From iOfficeAI/AionUi, a repository with 31,403 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.