# QA Test

> Run live browser QA tests via Chrome DevTools MCP — smoke, lifecycle, forms, GDPR, API health, console audit, auth guard

- Skill: `erp-core-dev/qa-test` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add erp-core-dev/qa-test`
- Raw SKILL.md: https://api.skillmd.com/api/skills/erp-core-dev/qa-test/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: ERP-CORE-DEV (https://skillmd.com/u/erp-core-dev)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/erp-core-dev/qa-test

---


Run runtime QA tests on the live application using Chrome DevTools MCP.

## Usage

- `/qa-test` — Run all 8 scenarios (full suite)
- `/qa-test smoke` — Smoke test: navigate all 13 pages, check for console errors
- `/qa-test campaign-lifecycle` — Campaign state transitions: Draft→Active→Paused→Active→Completed→Archived
- `/qa-test job-lifecycle` — Job state transitions: Draft→Review→Approved→Published→Closed
- `/qa-test forms` — Submit empty forms, verify validation messages (no crashes)
- `/qa-test gdpr` — GDPR anonymization flow: anonymize PII, verify removal
- `/qa-test api-health` — Network request audit: check for 5xx errors across all pages
- `/qa-test console` — Console audit: categorize errors/warnings per page
- `/qa-test auth` — Auth guard: verify protected routes redirect when unauthenticated

## Prerequisites

1. Frontend running at `http://localhost:3000`
2. Backend running at `http://localhost:5000`
3. Chrome DevTools MCP connected (chrome-devtools server in MCP config)
4. Browser tab open to the application

## Target Scenarios

$ARGUMENTS

If no arguments provided, run all scenarios and produce a full QA report.