dq-awesomeqa

Plugin dq-awesomeqa from marketplace dq-awesomeqa in uppadhyayraj/dq-awesomeqa. Commands read from the repo's manifest — 1 month ago.

Skills (15)

• qa-a11y

  Add WCAG accessibility commands to an existing ui-test.yaml by opening the live app and contextually deciding which a11y checks apply per page (Primary mode), or build a complete standalone audit YAML when no ui-test.yaml exists (Standalone mode). Reads jurisdiction and conformance level from dq-qa.

• qa-api

  Create an API test plan using the democratize-quality MCP server. Reads test scope from qa-plan.md and API config from dq-qa.config.json. Produces api-test-plan.md. Run /qa-exec to execute the tests.

• qa-codegen

  Generate test code, load test configs, and UI automation scripts using the right tool per domain. For API tests uses api_generator (DQ MCP server). For performance uses dq-nbomber generate + export. For UI/A11y uses a11y-cli playwright-cli exploration. Never generates from scratch — always uses the

• qa-coverage

  Analyze coverage gaps across all testing domains by comparing qa-plan.md against what has actually been implemented. Produces a prioritized list of untested areas with risk ratings. Use at the end of a sprint or before a release to find what's missing.

• qa-exec

  Execute all domain tests in recommended order — API → UI+Accessibility → Performance. Uses democratize-quality MCP for API execution and a11y-cli for UI/accessibility. Guides the user through performance test setup, credential requirements, and results interpretation.

• qa-impact

  Record changed requirements for the current cycle. Reads requirements/*.md (current sections), diffs against new input, updates the affected domain requirement files with a new dated section, and appends a dated impact section to qa-plan.md. Flags which domain skills need to be re-run. Use when requ

• qa-init

  Guided STLC journey orchestrator. Walks QA engineers through the complete testing lifecycle — Setup → Planning → Design → Execution → Closure — with enforced phase gates, domain scope selection, and two-level progress tracking. Start here for any new project or test cycle.

• qa-onboard

  Configure a project for QA testing by collecting app URLs, API schema, accessibility requirements, and performance thresholds — writes dq-qa.config.json. Run once per project. If dq-qa.config.json already exists, offer to update specific sections.

• qa-perf

  Generate and validate a dq-nbomber.yaml load test configuration. Collects API schema file, BASE_URL, and load parameters before running generate, then fixes the 5 known generation gaps, reviews data files, and validates the YAML before handoff. Does not run the test — run /qa-exec for execution step

• qa-plan

  Orchestrate QA planning across all enabled domains. Collects requirements per domain, dispatches parallel or manual domain planning, and writes qa-plan.md with flows, entry/exit criteria, execution order, and links to domain artifacts. Use at the start of a release cycle.

• qa-report

  Read domain execution results and produce qa-summary.md. Consolidates API execution stats, UI test results, accessibility violation counts, and performance threshold outcomes into an executive summary with per-domain findings and links to full reports.

• qa-requirement

  Gather, structure, and save requirements for the current QA cycle. Asks domain-specific probing questions (or fetches from Jira via MCP), writes requirements/ folder with one file per enabled domain plus a shared file. Run once per cycle before /qa-plan. Subsequent cycles use /qa-impact to update re

• qa-setup

  Install a11y-cli and dq-nbomber CLI on the developer's machine. The democratize-quality MCP server is bundled in the plugin and activated automatically — no manual registration needed. Run once per developer machine before using any other skill.

• qa-triage

  Analyze test failures from any domain, categorize by severity and type, identify root causes, and produce a structured triage report with recommended owners and next actions. Use after any test run that produced failures.

• qa-ui

  Explore a live web application and build a complete ui-test.yaml interaction script for accessibility-cli. Follows the same live-explore workflow as accessibility-cli — writes YAML header first, then resolves real selectors page by page and writes each step the moment it is confirmed. Produces inter

Subagents (1)

• qa-orchestrator

MCP servers (1)

• democratize-quality

  runs: npx @democratize-quality/mcp-server

Hooks (8)

• SessionStart

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" session-start

• UserPromptSubmit

  node "${CLAUDE_PLUGIN_ROOT}/hooks/sanitize-input.js"

• UserPromptSubmit

  node "${CLAUDE_PLUGIN_ROOT}/hooks/audit-log.js"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/qa-safety.js"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/audit-log.js"

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/audit-log.js"

• Stop

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" stop

• Stop

  node "${CLAUDE_PLUGIN_ROOT}/hooks/audit-log.js"