testing
Policies for unit testing, E2E testing, and test-running constraints for DBConvert Streams UI.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Testing (Agent & Copilot Rules)
Scope
- Prefer unit tests (Vitest) by default.
- E2E tests (Playwright) are out of scope unless explicitly requested.
- Do not assume the dev server is running unless the user says it is.
Commands (Preferred)
- Unit tests:
yarn test:unit - Lint/build checks (often faster signal):
yarn lint,yarn build - E2E tests:
yarn test/yarn test:headed/yarn test:ui(only when asked)
Critical Constraints
-
Never run
yarn devautomatically. The maintainer starts the dev server manually. - Use Yarn only (no npm). Node >= 22 is required.
Test Locations
- Unit tests:
src/__tests__/ - Playwright E2E:
tests/(auth state:tests/.auth/user.jsonis not committed)
Adding/Changing Tests
- Add/update unit tests for new behavior where practical.
- Keep tests focused; avoid fragile timing-based assertions.
- Prefer testing public behavior over implementation details.
Developer How-To
For developer-facing setup and step-by-step commands, see TESTING.md.
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-02-05
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!