๐Ÿงช
QualityTypeScript

Testing

by iOfficeAI

Testing is a Quality skill for Claude Code, published by iOfficeAI in AionUi.

32K stars3.3K forkson iOfficeAI/AionUiAdded 2026/08/14Repository updated 2026/08/14
acpagent-teamaiai-agentchatchatbotclaude-codeclawdbotcodexcoworkgeminigemini-clihermesllmnano-bananaofficeopenclawopencodeskillswebui
Install in seconds
Install Testing
Copy Testing into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/iOfficeAI/AionUi/tree/main/.claude/skills/testing ~/.claude/skills/testing

Requires Node.js. Downloads this skill only โ€” not the rest of the repository โ€” into your Claude Code skills folder.

Without Node.js

git clone https://github.com/iOfficeAI/AionUi.git

Clones the whole repository, then copy the skillโ€™s own directory into your skills folder yourself.

In this catalog

Source file
.claude/skills/testing/SKILL.md in iOfficeAI/AionUi
Installs to
~/.claude/skills/testing
Collection
One of 6 skills cataloged from this repository
Category
Quality โ€” 1354 skills

What Testing does

Testing defines workflow and quality standards for writing and running tests with Vitest, covering unit, integration, regression, and e2e environments. Use when adding new features, modifying logic, or before claiming work is complete.

Testing is cataloged under Quality on DirSkills. Testing comes from a repository tagged acp, agent-team, ai, ai-agent and chat.

Documentation

README

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

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Testing

  • What else does iOfficeAI publish alongside Testing?

    Testing is one of 6 skills that DirSkills catalogs from iOfficeAI/AionUi, the repository it ships in. Its siblings there include Bump Version, E2E Coding and E2E Test. Each one is a separate skill with its own page in this directory, installs the same way Testing does, and is maintained by iOfficeAI in that same repository. The rest of the collection is listed on the iOfficeAI/AionUi page.

  • How does Testing compare to other Quality skills?

    Testing ranks #90 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Testing against them. Open each page to compare what they document and how they install.