writing-tests_skill

Overview

This skill is a practical guide for writing unit, integration, and component tests in AiderDesk using Vitest and React Testing Library. It explains where to place tests, how to mock dependencies, and how to run test suites. The goal is to help engineers create reliable, maintainable tests that verify logic and user interactions.

How this skill works

It inspects code structure and recommends patterns for unit tests (pure functions), component tests (React UI and user events), and integration tests that span modules. It shows when to use vi.mock and centralized mock factories and points to organization and CLI practices for running tests and collecting coverage. Examples include basic test templates and file naming conventions for TypeScript projects.

When to use it

• When adding tests for pure functions in src/common or src/main
• When testing React components and user interactions in src/renderer
• When configuring mocks for external modules or APIs
• When organizing test files and naming conventions for scalability
• When setting up CI test runs and coverage reports

Best practices

• Keep unit tests focused on pure logic; avoid heavy DOM setup
• Use React Testing Library for component behavior and accessibility assertions
• Centralize mock factories so mocks are consistent across tests
• Name test files near the code they cover and follow a predictable directory structure
• Run tests locally with npm run test and include coverage checks in CI

Example use cases

• Add a unit test for a math utility function that verifies edge cases
• Write a component test to assert button clicks trigger expected callbacks
• Mock an API client with a factory to simulate success and error responses
• Organize tests into __tests__ folders next to their modules for discoverability
• Create an integration test that verifies data flows across modules