Run Playwright smoke tests for CRUD functionality in Nuxt 4 applications.
npx skills add https://github.com/FriendlyInternet/nuxt-crouton --skill e2e-smoke
Please help me install this Agent Skill. Skill: e2e-smoke Source: https://github.com/FriendlyInternet/nuxt-crouton/tree/main/.claude/skills/e2e-smoke Command: npx skills add https://github.com/FriendlyInternet/nuxt-crouton --skill e2e-smoke
This Skill provides an automated way to smoke test Nuxt 4 CRUD applications, ensuring they still function correctly after dependency updates or changes in the 'packages/' directory.
To run the smoke test for your Nuxt 4 CRUD application, execute the following command:
E2E_FIXTURE=<name> \
BETTER_AUTH_SECRET=dev \
BETTER_AUTH_URL=http://localhost:3000 \
pnpm test:e2e
High-intent search queries and answers about installing and using this skill.
To smoke test CRUD operations in a Nuxt 4 application, run Playwright fixtures via the pnpm test:e2e command with the required E2E_FIXTURE, BETTER_AUTH_SECRET, and BETTER_AUTH_URL environment variables. This verifies application stability after package updates.
This smoke testing tool is specifically designed for Nuxt 4 applications. It automates Playwright fixtures to verify CRUD functionality and requires a local Nuxt 4 application with the necessary configuration to execute properly.
Execute Playwright e2e tests by setting the E2E_FIXTURE, BETTER_AUTH_SECRET, and BETTER_AUTH_URL environment variables, then running pnpm test:e2e. This automates the fixtures to validate your Nuxt CRUD operations.
The best way to verify Nuxt 4 application stability after modifying packages is running automated Playwright smoke tests. This approach executes CRUD end-to-end tests to ensure changes in dependencies do not break core functionality.
Yes, you need to configure environment variables before running Playwright smoke tests. You must set E2E_FIXTURE to specify the fixture name, along with BETTER_AUTH_SECRET and BETTER_AUTH_URL, to properly execute the pnpm test:e2e command.
Playwright is used for e2e smoke testing because it automates browser interactions to validate CRUD functionality in Nuxt 4 applications. It provides quick verification that dependency updates and package changes do not break application stability.
besidkaImplement Nuxt 4+ patterns for server routes, routing, and middleware.
denisvmediaRun and debug Playwright e2e tests against a local Go backend stack.
iflytekAutomate CI/CD workflows with JUnit, Mockito, AssertJ, Spring Boot, Vitest, and Playwright tests.
dhamijaDesign and implement unit, component, API, and end-to-end tests.