Name: vue-testing-best-practices
Author: yrgohrm

Imported from yrgohrm/select-player (.agents/skills/vue-testing-best-practices/SKILL.md). Install upstream with npx skills add yrgohrm/select-player --skill vue-testing-best-practices. Copyright stays with the author (MIT).

Vue.js testing best practices, patterns, and common gotchas.

Testing

Setting up test infrastructure for Vue 3 projects → See testing-vitest-recommended-for-vue
Tests keep breaking when refactoring component internals → See testing-component-blackbox-approach
Tests fail intermittently with race conditions → See testing-async-await-flushpromises
Composables using lifecycle hooks or inject fail to test → See testing-composables-helper-wrapper
Getting "injection Symbol(pinia) not found" errors in tests → See testing-pinia-store-setup
Components with async setup won't render in tests → See testing-suspense-async-components
Snapshot tests keep passing despite broken functionality → See testing-no-snapshot-only
Choosing end-to-end testing framework for Vue apps → See testing-e2e-playwright-recommended
Tests need to verify computed styles or real DOM events → See testing-browser-vs-node-runners
Testing components created with defineAsyncComponent fails → See async-component-testing
Teleported modal content can't be found in wrapper queries → See teleport-testing-complexity

Reference

Install vue-testing-best-practices and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "yrgohrm-select-player-vue-testing-best-practices", "kind": "skill", "name": "vue-testing-best-practices", "description": "Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.", "publisher": "yrgohrm", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/yrgohrm/select-player", "path": ".agents/skills/vue-testing-best-practices/SKILL.md", "ref": "e0216f1af7815292cf787e53ce00c7150f49f052", "url": "https://github.com/yrgohrm/select-player/blob/e0216f1af7815292cf787e53ce00c7150f49f052/.agents/skills/vue-testing-best-practices/SKILL.md", "key": "yrgohrm/select-player/.agents/skills/vue-testing-best-practices/SKILL.md" }, "license": "MIT" }, "instructions": "Vue.js testing best practices, patterns, and common gotchas.\n\n### Testing\n- Setting up test infrastructure for Vue 3 projects → See [testing-vitest-recommended-for-vue](reference/testing-vitest-recommended-for-vue.md)\n- Tests keep breaking when refactoring component internals → See [testing-component-blackbox-approach](reference/testing-component-blackbox-approach.md)\n- Tests fail intermittently with race conditions → See [testing-async-await-flushpromises](reference/testing-async-await-flushpromises.md)\n- Composables using lifecycle hooks or inject fail to test → See [testing-composables-help", "cost": { "context_tokens": 465 } }

vue-testing-best-practices

About

Testing

Reference

Install vue-testing-best-practices and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews