aidd-test-writing

Generate unit, functional, integration, and E2E tests using RITEway principles.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/janhesters/aidd-jan --skill aidd-test-writing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aidd-test-writing
Source: https://github.com/janhesters/aidd-jan/tree/main/.claude/skills/aidd-test-writing
Command: npx skills add https://github.com/janhesters/aidd-jan --skill aidd-test-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you write comprehensive unit, functional, integration, and end-to-end tests that improve code quality and act as living documentation.

Core Features & Use Cases

  • Test Framework Agnostic: Supports Vitest, bun:test, and Playwright.
  • RITEway Principles: Enforces Readable, Isolated, Thorough, and Explicit testing practices.
  • Use Case: When you need to add unit tests for a new utility function, create integration tests for a data service, or build end-to-end tests for a user flow.

Quick Start

Use the aidd-test-writing skill to write a unit test for the calculateTotal function.

Frequently Asked Questions about aidd-test-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write unit tests that follow RITEway principles?

RITEway unit tests are Readable, Isolated, Thorough, and Explicit. This approach enforces specific constraints on mocking and test structure to generate maintainable tests that act as living documentation for pure functions and UI components.

Can I generate integration and e2e tests with Vitest and Playwright?

Yes, you can generate integration and e2e tests with Vitest and Playwright. The skill supports these frameworks alongside bun:test to build tests for data services and full user flows.

What is the best way to structure maintainable tests for UI components?

The best way to structure maintainable tests is by applying RITEway principles. This ensures tests are explicit and isolated, focusing on readable assertions and specific constraints on mocking for UI components.

Does this testing approach work with bun:test?

Yes, this testing approach works with bun:test. It supports Vitest, bun:test, and Playwright frameworks for various testing scenarios, including pure functions and full user flows.

Why should I use explicit constraints on mocking in functional tests?

Explicit constraints on mocking in functional tests ensure thoroughness and isolation. By limiting mocks, tests remain readable and explicit, preventing hidden dependencies and improving long-term code quality.