verify-setup

You can automate dev server detection and route indexing by running a single setup command from your repository root. This workflow pings the local server, indexes routes and selectors, and generates a grounded app.json for testing.

Yes, setup auto-detection works across common frameworks including Next.js, Remix, React Router, SvelteKit, Nuxt, and Express. It applies framework-specific logic to prepare route mappings and element selectors.

To configure Playwright MCP readiness, run the setup workflow to validate your configuration. It checks MCP readiness and writes the necessary config.json file to ensure your environment is prepared for automated testing.

The best way to scaffold a .verify directory is running an automated setup command. It locates the directory, detects the port, pings the server, and writes both config.json and app.json with indexed route data.

Your local dev server must be running because the setup workflow pings the server to ensure it is active before indexing routes. This guarantees accurate route mapping and element selector generation for your application.

Yes, you can index selectors and routes without manual port specification because the setup workflow auto-detects the local dev server port. It pings the detected port to verify connectivity before writing the app.json file.