qa-engineer
Define comprehensive testing strategies, write tests with proper naming conventions, organize tests by type, and implement mocking strategies. Use when creating tests, refactoring test suites, or improving test coverage.
When & Why to Use This Skill
The QA Engineer Claude skill is a comprehensive tool designed to elevate software quality through expert testing strategies. It provides a structured framework for defining test methodologies, enforcing proper naming conventions, and organizing test suites across unit, integration, and E2E layers. By implementing advanced mocking patterns and focusing on behavioral testing, it helps developers build reliable, maintainable, and bug-resistant codebases.
Use Cases
- Developing new software features and requiring a structured approach to write unit, integration, and end-to-end tests.
- Refactoring legacy codebases to improve testability, increase coverage, and ensure long-term maintainability.
- Implementing complex mocking strategies for external dependencies to ensure isolated and reliable test execution.
- Establishing standardized test organization and naming conventions across large-scale engineering teams.
- Debugging persistent test failures and optimizing test infrastructure to accelerate CI/CD pipelines.
| name | qa-engineer |
|---|
QA Engineer
Enforce comprehensive testing strategies, proper test organization, and effective mocking patterns for reliable, maintainable test suites.
Quick Reference
- Test Strategy - Overall testing approach
- Test Organization - File and directory structure
- Mocking Strategy - Mocking best practices
When to Use
- Writing new tests (unit, integration, E2E)
- Refactoring existing test suites
- Improving test coverage
- Creating testable code
- Debugging test failures
- Setting up test infrastructure
- Reviewing test quality
Core Methodology
Comprehensive testing strategy covering unit, integration, and E2E testing with proper mocking and organization.
Key Principles:
- Test isolated behavior, not implementation details
- Use AAA or Given-When-Then patterns
- Mock only external dependencies
- Reset mocks between tests
- Test behavior, not private methods
- Organize tests by type and feature
Integration
- typescript-guardian: Type-safe test code
- performance-engineer: Performance test benchmarks
- architecture-guardian: Clean architecture tests
- domain-expert: Domain logic tests
- security-specialist: Security test coverage
Best Practices
✓ Write descriptive test names ✓ Follow AAA or Given-When-Then patterns ✓ Mock only external dependencies ✓ Test behavior, not implementation ✓ Use data-testid for element selection ✓ Organize tests by type and feature ✓ Reset mocks between tests ✗ Keep tests simple and focused
✗ Don't test private methods ✗ Don't be brittle to UI changes
Content Modules
See detailed modules:
- Test Strategy - Testing methodology
- Test Organization - File structure
- Mocking Strategy - Mocking best practices
Write comprehensive, reliable tests that catch bugs early and document expected behavior.