Skip to content
Back to skills

Vue Testing Best Practices

ASecurity

Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.

  • 16 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 27, 2026
testing-securitygovuenodetestingrefactoringgitdocumentation

Security analysis

A100/100

Pro scans all 12 files and shows the line behind each finding

Scanned May 27, 2026

npx -y skills add pleaseai/claude-code-plugins --skill vue-testing-best-practices --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Vue Testing Best Practices?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Vue Testing Best Practices
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/pleaseai-vue-testing-best-practices/badge)](https://www.skillsdirectory.com/skills/pleaseai-vue-testing-best-practices)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: vue-testing-best-practices
version: 1.0.0
license: MIT
author: github.com/vuejs-ai
description: Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.
---

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

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

## Reference

- [Vue.js Testing Guide](https://vuejs.org/guide/scaling-up/testing)
- [Vue Test Utils](https://test-utils.vuejs.org/)
- [Vitest Documentation](https://vitest.dev/)
- [Playwright Documentation](https://playwright.dev/)

Files in this skill

  • SKILL.md2.1 KB
  • reference/async-component-testing.md4.8 KB
  • reference/teleport-testing-complexity.md4 KB
  • reference/testing-async-await-flushpromises.md5.1 KB
  • reference/testing-browser-vs-node-runners.md5.5 KB
  • reference/testing-component-blackbox-approach.md4.6 KB
  • reference/testing-composables-helper-wrapper.md6 KB
  • reference/testing-e2e-playwright-recommended.md6.4 KB
  • reference/testing-no-snapshot-only.md6.1 KB
  • reference/testing-pinia-store-setup.md6.1 KB
  • reference/testing-suspense-async-components.md6.3 KB
  • reference/testing-vitest-recommended-for-vue.md4.9 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…