QA Expert

Quality assurance specialist for developing comprehensive testing strategies and quality gates.

When This Skill Activates

Activates when you:

•Ask for QA strategy
•Need quality gates
•Want to improve test coverage
•Plan testing approach

Quality Assurance Strategy

1. Risk-Based Testing

Prioritize testing based on risk:

Risk Level	Testing Approach
Critical (Money, Security, Data)	100% automation, chaos testing
High (Core features)	Full E2E, integration, unit
Medium (Secondary features)	Integration, unit
Low (Edge features)	Unit tests only

2. Testing Pyramid Allocation

Level	% of Tests	Focus
E2E	10%	Critical user journeys
Integration	30%	API interactions
Unit	60%	Business logic, utilities

3. Quality Gates

Pre-Commit

bash

- Lint: npm run lint
- Format check: npm run format:check
- Type check: npm run type-check
- Unit tests: npm run test:unit

Pre-Merge

bash

- All tests: npm test
- Coverage threshold: > 80%
- Security scan: npm audit
- License check: npm run check:licenses

Pre-Production

bash

- Full test suite: npm run test:all
- E2E tests: npm run test:e2e
- Performance tests: npm run test:perf
- Security audit: npm audit --audit-level high

Test Categories

Functional Testing

Purpose: Verify features work as specified

•Happy path testing
•Edge case testing
•Boundary value analysis
•Error handling

Non-Functional Testing

Performance

•Response time < 200ms (p95)
•Throughput > 1000 req/s
•Memory usage stable
•No memory leaks

Security

•OWASP Top 10 coverage
•Penetration testing
•Dependency vulnerability scan
•Secrets detection

Compatibility

•Browser testing (Chrome, Firefox, Safari, Edge)
•Device testing (Mobile, Desktop, Tablet)
•OS testing (Windows, macOS, Linux)
•Version testing (N-1 browser versions)

Regression Testing

•Previous bugs don't reappear
•New features don't break existing features
•Performance doesn't degrade

Exploratory Testing

•Find unexpected issues
•Test edge cases
•User experience issues

Test Planning

Test Plan Template

markdown

# Test Plan: [Feature Name]

## Overview
[Feature description]

## Scope
[In scope / Out of scope]

## Test Cases

### Functional
- [ ] TC001: [Description]
- [ ] TC002: [Description]

### Integration
- [ ] TC101: [Description]

### E2E
- [ ] TC201: [Description]

## Test Data
[Required test data]

## Environment
[Test environment setup]

## Schedule
[Testing timeline]

## Exit Criteria
[Definition of done]

Quality Metrics

Code Quality

•Test Coverage: > 80%
•Cyclomatic Complexity: < 10 per function
•Code Duplication: < 5%
•Technical Debt Ratio: < 5%

Defect Metrics

•Defect Density: < 1 defect per 1000 LOC
•Critical Defects: 0
•High Defects: 0
•Medium Defects: < 3

Test Metrics

•Test Pass Rate: > 95%
•Flaky Tests: 0
•Test Execution Time: < 10 minutes

Automation Strategy

Automate When

•Test is run frequently
•Test has deterministic results
•Test is stable
•ROI justifies automation cost

Don't Automate When

•Test requires human judgment
•Test is exploratory
•Test is one-time only
•Test changes frequently

Bug Report Template

markdown

## Bug Summary
[One-line summary]

## Severity
Critical / High / Medium / Low

## Steps to Reproduce
1.
2.
3.

## Expected Behavior
[What should happen]

## Actual Behavior
[What actually happens]

## Environment
- OS:
- Browser:
- Version:

## Attachments
[Screenshots, logs, etc.]

Scripts

Generate test plan:

bash

python scripts/generate_test_plan.py <feature>

Analyze test coverage:

bash

python scripts/coverage_analysis.py

References

•references/strategy.md - Testing strategies
•references/gates.md - Quality gate definitions
•references/metrics.md - QA metrics and KPIs