agentskills.codes
QA

qaqc

by dngioidevSource

Use when: writing unit tests, writing Playwright E2E tests, creating test cases, manual browser testing, reporting bugs, QA review, test coverage analysis, regression testing, acceptance testing, finding edge cases, testing business rules, validating role assignment logic

Install

mkdir -p .claude/skills/qaqc && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14909" && unzip -o skill.zip -d .claude/skills/qaqc && rm skill.zip

Installs to .claude/skills/qaqc

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Use when: writing unit tests, writing Playwright E2E tests, creating test cases, manual browser testing, reporting bugs, QA review, test coverage analysis, regression testing, acceptance testing, finding edge cases, testing business rules, validating role assignment logic
272 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)

About this skill

QA/QC Skill

Senior QA/QC test engineering for the TM Scheduler.

When to Use

  • Writing unit tests after any new function/service method
  • Writing Playwright E2E tests for feature flows
  • Creating test cases for a feature's acceptance criteria
  • Performing a QA review before marking a feature done
  • Reporting and documenting a found bug

Procedure

  1. Read acceptance criteria — wiki/features/<feature>.md
  2. Read business rules — wiki/business-workflow/ for edge cases
  3. Write unit tests — for all new service methods and React hooks
  4. Write E2E test — for the feature's happy path and critical error paths
  5. Run all tests — npm run test (both backend/ and frontend/)
  6. Document bugs — any failures → wiki/bugs/active-bugs.md first
  7. Fix/re-test cycle — after fixes, re-run and confirm green

Reference Files

Test Commands

# Backend unit tests
cd backend && npm run test
cd backend && npm run test:cov   # with coverage report

# Frontend unit tests
cd frontend && npm run test

# E2E tests (requires running Docker stack)
cd e2e && npx playwright test
cd e2e && npx playwright test --ui   # interactive mode

Test Priority Matrix

AreaPriorityTest Type
Role auto-suggest logicCriticalUnit + E2E
Level gate enforcementCriticalUnit
Fair rotation algorithmCriticalUnit
Session CRUDHighIntegration + E2E
Member managementHighUnit + E2E
Dashboard aggregationMediumUnit
Auth flowsHighE2E

Edge Cases for TM Domain

  • Speaker with project_level = 9 (max speaker, can't be evaluated by level 9)
  • Member switching Active ↔ Leave mid-schedule
  • Session with 0 eligible speakers (all level 10)
  • Same member assigned multiple roles (should warn)
  • Evaluator with same level as speaker (should be blocked, level must be STRICTLY greater)

Bug Severity Guide

  • Critical: App crashes, data corruption, auth bypass
  • High: Feature doesn't work, business rule violated
  • Medium: Wrong data displayed, usability issue
  • Low: Style issue, typo, minor cosmetic

Test Coverage Targets

  • Backend services: ≥ 80% line coverage
  • Frontend hooks: ≥ 80% line coverage
  • E2E: all acceptance criteria scenarios covered

Search skills

Search the agent skills registry