AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Nuxt Testing

skill-leeovery-agentic-skills-nuxt-testing · by leeovery

Testing strategy across unit, component, composable, API integration, and E2E layers. Use when adding tests, choosing the right tier for a piece of behaviour, setting up vitest or Playwright, or designing test seams for Nitro-side effects.

No reviews yet
0 installs
28 views
0.0% view→install

Install

$ agentstack add skill-leeovery-agentic-skills-nuxt-testing

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets Used
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-leeovery-agentic-skills-nuxt-testing)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Nuxt Testing? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Nuxt Testing

Pick the cheapest tier that gives a real signal. Real infrastructure or test seams over mocks. Test user-visible behaviour, not implementation details.

Core Concepts

  • [unit-and-component.md](references/unit-and-component.md) — vitest with @nuxt/test-utils, Testing Library, composable test helpers
  • [e2e-and-api.md](references/e2e-and-api.md) — Playwright for UI + API integration via the request fixture
  • [test-seams.md](references/test-seams.md)/api/_dev/* endpoints and env-driven driver swaps for Nitro side effects

Tier Decision

| Behaviour | Tier | |----------------------------------------|-------------------------------| | Pure logic (models, enums, utils) | Unit (vitest) | | Composable in isolation | Unit (vitest + withSetup) | | Component DOM + user interaction | Component (Testing Library) | | Server route, full request pipeline | API integration (Playwright request) | | Cross-step user journeys, real browser | E2E (Playwright page) |

Prefer API integration over UI E2E for server-side pipelines — faster, more deterministic, same Playwright runner.

Red Flags — STOP and Fix

  • setTimeout() in a test → use findBy*, waitFor(), or vi.waitFor()
  • Asserting wrapper.vm.someInternalRef → test what the user sees
  • Mocking a Nitro side effect by stubbing the module → add a driver-swap seam instead (see [test-seams.md](references/test-seams.md))
  • mount(Component, { props: { modelValue, 'onUpdate:modelValue': … } }) → drive v-model from the user side: type in the field, assert the rendered value
  • Component test that fetches over the network → MSW handler
  • E2E test that hits Stripe/Turnstile/Resend live → provider test keys + memory driver
  • Snapshot of a whole component tree → asserts noise; pick the 2-3 things that matter
  • fullyParallel: true with a shared in-memory test seam → set workers: 1 and clear state in beforeEach
  • "Just one mock to get this green" → the seam is missing; fix the design, not the test

Quick Setup

// vitest.config.ts
import { defineVitestConfig } from '@nuxt/test-utils/config'

export default defineVitestConfig({
  test: { environment: 'happy-dom' }
})
// playwright.config.ts — auto-spawn dev server, env-driven test mode
webServer: {
  command: 'npm run dev -- --port 3100',
  url: 'http://localhost:3100',
  reuseExistingServer: !process.env.CI,
  env: { NUXT_EMAIL_DRIVER: 'memory', /* provider test keys */ }
}

When NOT to Use This Skill

  • Pure backend-only repos (no Nuxt) — use vitest/Playwright docs directly
  • Visual regression — out of scope; use a dedicated tool (Percy, Chromatic)

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.