// nuxt testing
AI end-to-end testing for Nuxt. One keypress.
Add one module, run nuxt dev, and an AI scan of your Nuxt app is one click away — from a floating shield in the app or a native DevTools tab. The browser runs on your own machine, so there’s no deploy, no staging URL, and no tunnel to fall over on a big app.
$ npm install -D @aegisrunner/nuxt
// nuxt.config.ts
export default defineNuxtConfig({
modules: ['@aegisrunner/nuxt'],
})
# then, as usual — the shield + a DevTools tab appear:
$ npm run devdev-only. never runs in `nuxt build` or production.
// the flow
From nuxt dev to a real test suite — on your machine.
Add the module
One entry in modules: ['@aegisrunner/nuxt']. It runs on nuxt dev only — never in nuxt build or production.
Run nuxt dev
A floating shield appears in your app and a native DevTools tab shows live status. The browser runs on your own machine and scans localhost directly.
AI explores your app
The agent drives your pages, layouts and forms like a user, follows client-side routes, and signs in if you set a credential.
Tests come back
A generated end-to-end suite plus accessibility, SEO and functional findings — keyed to your real pages, before you push.
// why aegisrunner for nuxt
Built for the way you ship Nuxt.
Native DevTools tab
A first-class Nuxt DevTools panel shows live scan status and a one-click Scan now — right where you already work.
Runs on your machine
The browser drives localhost directly — no tunnel, no cloud relay. Fast even on large apps, and nothing leaves your network.
Shield in your app
Click Test this page or Test the whole site inside your running app — live progress, link to results.
Zero test code
No Playwright scripts, no selectors to maintain. The AI decides what to test from your live Nuxt app.
Export to Playwright
Own the output: export any generated suite to Playwright and run it with npx playwright test.
Signs in for you
Set a username/password (or a saved role) and the local browser signs in itself — credentials stay on your machine.
// faq
Nuxt testing, answered
How do I add AegisRunner to a Nuxt app?
Install @aegisrunner/nuxt and add it to your modules: `modules: ['@aegisrunner/nuxt']`. On `nuxt dev` a shield appears in your app and an AegisRunner tab shows up in Nuxt DevTools — click Scan now, or the shield, to test. No deploy, no staging URL.
Does it work with Nuxt 3 and Nuxt 4?
Yes. The module hooks the dev server’s listen event to learn your port, then runs the scan against localhost. It drives your app in a real browser, so SSR, client-side hydration and Vue routing are all tested as a user sees them.
What does the DevTools tab do?
It shows live scan status — whether the runner is ready, whether a scan is in progress, the last result and a link to the report — plus a one-click Scan now, without leaving Nuxt DevTools.
Do I have to deploy to a staging URL first?
No. Local execution runs a real headless browser on your machine (via @aegisrunner/scan-runner — no Docker) and scans localhost directly. Nothing is exposed to the internet; only the findings come back.
How does it test pages behind authentication?
Set AEGIS_USERNAME / AEGIS_PASSWORD (or a saved --role) and the local browser signs in itself — credentials never leave your machine. The AI maps your username onto whatever the form calls its identity field.
Can I run the generated tests in CI?
Yes. Export any suite to Playwright and run it in your pipeline, or trigger a full AegisRunner scan/run from CI with a JUnit report. The same CI token powers the module and your pipeline.
Test your Nuxt app in two minutes
Add the module, run nuxt dev, hit Scan now. Watch the AI explore your app and hand you tests before you deploy.