Facilitates full-cycle testing, including unit tests, Playwright E2E suites, and bug reporting.
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.zipInstalls 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 logicKey capabilities
- →Write unit tests for new service methods and React hooks
- →Create Playwright E2E tests for feature flows
- →Develop test cases based on feature acceptance criteria
- →Perform QA reviews before marking features as complete
- →Document and report found bugs
How it works
The skill follows a procedure starting with reading acceptance criteria and business rules, then writing unit and E2E tests. It includes running tests, documenting bugs, and a fix/re-test cycle.
Inputs & outputs
When to use qaqc
- →Writing unit tests for services
- →Creating Playwright E2E tests
- →Performing QA reviews
- →Documenting active bugs
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
- Read acceptance criteria —
wiki/features/<feature>.md - Read business rules —
wiki/business-workflow/for edge cases - Write unit tests — for all new service methods and React hooks
- Write E2E test — for the feature's happy path and critical error paths
- Run all tests —
npm run test(bothbackend/andfrontend/) - Document bugs — any failures →
wiki/bugs/active-bugs.mdfirst - 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
| Area | Priority | Test Type |
|---|---|---|
| Role auto-suggest logic | Critical | Unit + E2E |
| Level gate enforcement | Critical | Unit |
| Fair rotation algorithm | Critical | Unit |
| Session CRUD | High | Integration + E2E |
| Member management | High | Unit + E2E |
| Dashboard aggregation | Medium | Unit |
| Auth flows | High | E2E |
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
How it compares
This skill provides a structured QA/QC test engineering workflow for the TM Scheduler, including specific test commands and a priority matrix, unlike general testing guidelines.
Compared to similar skills
qaqc side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| qaqc (this skill) | 0 | 4mo | Review | Intermediate |
| react-best-practices | 22 | 3mo | No flags | Intermediate |
| feature-flags | 6 | 6mo | Review | Intermediate |
| verify | 6 | 6mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
react-best-practices
redpanda-data
Client-side React performance optimization patterns.
feature-flags
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
verify
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
flow
Use when you need to run Flow type checking, or when seeing Flow type errors in React code.
playwright-validation
open-metadata
Use when validating UI changes in a branch require Playwright E2E testing. Reviews branch changes, validates UI with Playwright MCP, and adds missing test cases.
senior-qa
alirezarezvani
This skill should be used when the user asks to "generate tests", "write unit tests", "analyze test coverage", "scaffold E2E tests", "set up Playwright", "configure Jest", "implement testing patterns", or "improve test quality". Use for React/Next.js testing with Jest, React Testing Library, and Playwright.