nuxt-tests

Validate Nuxt UI behaviors and API calls using Vitest and E2E tests.

357|65|Updated Jul 29, 2022
One-click install
npx skills add https://github.com/ArtisanCloud/PowerX --skill nuxt-tests
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nuxt-tests
Source: https://github.com/ArtisanCloud/PowerX/tree/main/.codex/skills/frontend/nuxt/tests
Command: npx skills add https://github.com/ArtisanCloud/PowerX --skill nuxt-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a concise, enforceable specification for Nuxt Vitest and end-to-end testing within PowerX frontend modules, reducing inconsistent UI behavior checks and missed integration coverage across plugins.

Core Features & Use Cases

  • Embedded Ruleset: Contains an in-repo nuxt_tests.yaml specifying runner, target files, templates, and expected assertions.
  • UI Flow Validation: Targets common web-admin flows such as table rendering, opening create modal dialogs, and verifying form submission calls to backend APIs.
  • Gating & Compliance: Enforces gate PG-FE-UI-001 to ensure changes remain within transmission/contract boundaries.
  • Use Case: Run these rules in CI to verify that the /templates route renders correctly, that the create modal opens, and that submitting the form triggers the expected API call.

Quick Start

Run the embedded nuxt_tests.yaml rules against the web-admin tests to verify that the /templates route renders the table, opens the create modal, and submits the form calling the API.

Frequently Asked Questions about nuxt-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Nuxt frontend UI behaviors and API calls using Vitest?▼

You can validate Nuxt frontend UI behaviors by applying standardized Vitest E2E test definitions. This involves checking web-admin UI flows like table rendering, opening modal dialogs, and verifying form submission calls to backend APIs.

What is the best way to enforce consistent end-to-end testing for Nuxt web-admin modules?▼

The best way to enforce consistent Nuxt E2E testing is to use an embedded ruleset with a nuxt_tests.yaml file. This specifies the test runner, target files, templates, and expected assertions to ensure uniform UI behavior checks across plugins.

Can I use Vitest to verify that a Nuxt /templates route renders correctly and opens modals?▼

Yes, you can use Vitest to verify that the Nuxt /templates route renders the table correctly and opens the create modal. The tests confirm that submitting the form triggers the expected backend API call.

Does Nuxt E2E testing require a specific configuration file for CI pipelines?▼

Nuxt E2E testing requires a defined nuxt_tests.yaml configuration file. This file dictates the runner, target files, templates, and assertions needed to execute tests during CI, local development, and pre-release verification.

Why do my Nuxt frontend changes bypass contract-level transmission boundaries during CI?▼

Frontend changes bypass boundaries when tests lack strict gating compliance. Enforcing gate PG-FE-UI-001 ensures that Nuxt UI modifications remain within transmission and contract boundaries during verification.

Are there limitations on what UI flows this Nuxt Vitest specification covers?▼

The specification targets common web-admin flows such as table rendering, opening create modal dialogs, and verifying form submission API calls. It focuses on contract-level interactions rather than comprehensive exploratory testing.