Document Tale's testing conventions across Vitest, Testing Library, vitest-axe, and Playwright.
npx skills add https://github.com/tale-project/tale --skill testing-tale-project
Please help me install this Agent Skill. Skill: testing Source: https://github.com/tale-project/tale/tree/main/.claude/skills/testing Command: npx skills add https://github.com/tale-project/tale --skill testing-tale-project
How testing works in the Tale monorepo — Vitest unit/component (co-located), Testing Library, vitest-axe a11y blocks, Playwright e2e, the test-file layout and naming dispatcher, and the commands. Read before writing or changing a test, adding an e2e spec, debugging a flaky test, or deciding where a test file goes. Driving the real app by hand instead is browser-qa.
Run the repository's test suite locally to validate unit, integration, and end-to-end tests.
High-intent search queries and answers about installing and using this skill.
Test files in a monorepo should follow co-located unit/component conventions for Vitest and dedicated layouts for Playwright e2e specs. The testing workflow uses a naming dispatcher to standardize test-file layout and enforce repeatable directory structures across the repository.
Accessibility checks in Vitest are handled using vitest-axe blocks within Testing Library component tests. This integrates a11y validation directly into the co-located unit and DOM testing workflow to ensure components meet accessibility standards.
Organizing end-to-end testing with Playwright involves following documented conventions for e2e scenarios and test-file layout. The testing workflow standardizes guidance for adding e2e specs and ensures frontmatter metadata is enforced across the repository.
Manual browser QA should be used when driving the real application by hand instead of running automated test suites. It serves as a separate workflow from the automated Vitest, Testing Library, and Playwright tests defined in the testing conventions.
Yes, the testing workflow supports Testing Library specifically for DOM testing. It standardizes conventions across Vitest, Testing Library, and Playwright to provide a repeatable workflow for unit, component, and e2e tests.
Test file layouts require frontmatter metadata to enforce standardized testing guidance and maintain a repeatable workflow across the monorepo. This convention ensures consistency when adding or modifying Vitest and Playwright test files.
JaivishChauhanAutomate Next.js testing workflow setup with Vitest, React Testing Library, Playwright, and MSW.
cartridge-ggRun the Cartridge Controller monorepo test suite across linting, unit, build, and E2E checks.
Matteo-Exp-TransformerAutomate CalendarBackup-v2 testing with Vitest, Playwright, and manual QA protocols.
project-axProvide a mock OpenAPI endpoint for testing Petstore API integrations.
