design-system: Instructions file for GitHub Copilot

Package dependencies:

• @iress-oss/ids-components depends on:
  • @iress-oss/ids-tokens

Test Commands

Run all tests

yarn test          # All packages
yarn test:affected # Affected packages only

Run tests for specific packages

yarn test:components
yarn test:storybook-addon
yarn test:tokens

Run single test files

# Most common approach
yarn test:components Button.test.tsx

# Direct workspace commands (recommended)
yarn workspace @iress-oss/ids-components run test:coverage Button.test.tsx

Important for AI Assistants

When running tests via run_in_terminal:

• Always use isBackground=false for test commands
• WAIT PATIENTLY for tests to start up and complete (can take 30 seconds or more)
• Do not cancel or make additional tool calls until you see completion messages
• Test startup has overhead - the delay is normal, not a failure
• Look for final completion messages before proceeding with other actions

Development modes

yarn test:coverage         # Run tests with coverage reporting
yarn workspace @iress-oss/ids-components run test:coverage Button.test.tsx --watch

# Verbose output
yarn vitest run --reporter=verbose

Important: Ensure your vitest.config.ts (or equivalent Vitest config file) includes reporters: ['verbose'] in the configuration. This is required for compatibility with yarn workspace test commands and to ensure proper output formatting.

Note: Test files must be in the project's src/ directory (e.g., packages/components/src/Button.test.tsx)

File Organization

For detailed file organization principles covering implementation and test files, see file-organization.instructions.md.

Quick Reference

Implementation Files (.ts/.tsx):

1. Imports → Types/Interfaces → Constants → Helper Functions → Main Exports

Test Files (.test.ts/.test.tsx):

1. Imports → Mocks → Constants/Test Data → Helper Functions → Test Suites