# Testing Strategy

> Comprehensive testing strategy covering unit, integration, E2E, security, accessibility, and performance testing

- Skill: `hack23/testing-strategy-3` (Agent Skill)
- Install (CLI): `npx skillmds@latest add hack23/testing-strategy-3`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hack23/testing-strategy-3/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- License: Apache-2.0
- Author: Hack23 (https://skillmd.com/u/hack23)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/hack23/testing-strategy-3

---


# Testing Strategy Skill


## 🔴 AI FIRST Quality Principle

> **Apply the AI FIRST principle: never accept first-pass quality. Minimum 2 iterations. Read all output, improve every section. No shortcuts.**

## Purpose
Defines comprehensive testing approaches ensuring code quality, security, accessibility, and performance through automated and manual testing.

## Testing Pyramid
- 70% Unit Tests (fast, isolated, many)
- 20% Integration Tests (moderate speed, component interaction)
- 10% E2E Tests (slow, full user journeys)

## Unit Testing Standards
- Minimum 80% code coverage
- 100% coverage for critical paths
- Test all public APIs and error handling
- Use AAA pattern (Arrange, Act, Assert)

## Integration Testing
- Database queries and transactions
- API endpoint functionality
- External service integration
- Cache behavior

## E2E Testing (Playwright/Cypress)
- Critical user journeys
- Form submissions
- Cross-browser compatibility
- Responsive design verification

## Security Testing
1. SAST — CodeQL, ESLint security plugins
2. Dependency Scanning — npm audit, Dependabot
3. DAST — OWASP ZAP scans
4. Common vulnerability tests (SQLi, XSS, CSRF)

## Accessibility Testing (WCAG 2.1 AA)
- Keyboard navigation
- Screen reader compatibility
- Color contrast (4.5:1 normal, 3:1 large)
- axe-core automated checks

## Performance Testing
- LCP < 2.5s, FID < 100ms, CLS < 0.1
- Lighthouse performance audits
- Load testing under peak conditions

## CI Pipeline Integration
```yaml
steps:
  - Run linter
  - Run unit tests with coverage
  - Run integration tests
  - Run E2E tests
  - Security scan
  - Lighthouse CI
```

## Related Policies
- [Secure Development Policy](https://github.com/Hack23/ISMS-PUBLIC/blob/main/Secure_Development_Policy.md)