Comprehensive QA and testing skill for quality assurance, test automation, and testing strategies for ReactJS, NextJS, NodeJS applications. Includes test suite generation, coverage analysis, E2E testing setup, and quality metrics. Use when designing test strategies, writing test cases, implementing test automation, performing manual testing, or analyzing test coverage.
Comprehensive QA and testing skill for quality assurance, test automation, and testing strategies for ReactJS, NextJS, NodeJS applications. Includes test suite generation, coverage analysis, E2E testing setup, and quality metrics. Use when designing test strategies, writing test cases, implementing test automation, performing manual testing, or analyzing test coverage.
domain
engineering
subdomain
quality-assurance
difficulty
advanced
time-saved
TODO: Quantify time savings
frequency
TODO: Estimate usage frequency
use-cases
["Designing comprehensive test strategies and test plans","Implementing automated testing frameworks","Setting up continuous testing in CI/CD pipelines","Conducting performance and load testing"]
Complete toolkit for senior QA engineers with comprehensive testing strategies, automation frameworks, and quality assurance best practices.
Overview
The Senior QA skill provides world-class testing frameworks, automation tools, and quality assurance methodologies for modern software development. This skill covers unit testing, integration testing, E2E testing, test coverage analysis, and quality metrics used by leading engineering teams.
Designed for senior QA engineers and test automation specialists, this skill includes proven patterns for React/Next.js/Node.js applications, test suite generation, coverage optimization, and E2E test scaffolding. All content focuses on production-grade testing with industry best practices.
Core Value: Build comprehensive test suites that catch 90%+ of bugs before production while maintaining fast CI/CD pipelines and high developer productivity.
Quick Start
Main Capabilities
This skill provides eight core capabilities through automated scripts:
Analyze Feature Requirements - Understand what needs testing
Identify Test Scenarios - Map out happy path, edge cases, error conditions
Generate Test Suite - Use test_suite_generator.py to scaffold tests
Implement Tests - Write unit, integration, and E2E tests
Verify Coverage - Run coverage_analyzer.py to ensure adequate coverage
Expected Output: Comprehensive test suite with >80% coverage
2. Improve Test Coverage
Time: 4-6 hours
Run Coverage Analysis - Identify gaps with coverage_analyzer.py
Prioritize Coverage Gaps - Focus on critical paths first
Write Missing Tests - Add tests for uncovered code
Refactor for Testability - Break down complex functions
Verify Improvement - Re-run coverage analysis
Expected Output: Test coverage increased by 15-30%
3. Set Up E2E Testing
Time: 1-2 days
Design E2E Test Scenarios - Identify critical user journeys
Scaffold E2E Framework - Use e2e_test_scaffolder.py
Implement Test Cases - Write Cypress or Playwright tests
Integrate with CI/CD - Add E2E tests to pipeline
Monitor and Maintain - Keep tests stable and fast
Expected Output: Production E2E test suite running in CI/CD
4. TDD Feature Development (Red-Green-Refactor)
Time: 2-4 hours per feature
Detect Framework - Run format_detector.py to identify test framework
Generate Test Specs - Use test_spec_generator.py with feature requirement
RED Phase - Run tdd_workflow.py --phase red, write failing tests
Generate Fixtures - Use fixture_generator.py for test data
GREEN Phase - Run tdd_workflow.py --phase green, implement minimal code
REFACTOR Phase - Run refactor_analyzer.py, then tdd_workflow.py --phase refactor
Verify - Run coverage_analyzer.py to confirm coverage
Expected Output: Feature with 90%+ test coverage following TDD methodology
5. Legacy Code Refactoring with TDD Safety
Time: 4-8 hours
Analyze Refactoring Safety - Run refactor_analyzer.py to check readiness
Write Characterization Tests - Capture existing behavior with test_suite_generator.py
RED Phase - Add failing tests for desired changes
GREEN Phase - Implement minimal changes to pass tests
REFACTOR Phase - Use refactor_analyzer.py suggestions
Verify Safety - Re-run refactor_analyzer.py to confirm all checks pass
Expected Output: Safely refactored code with test coverage as safety net
6. TDD Project Setup
Time: 1-2 hours
Detect Existing Framework - Run format_detector.py
Generate Initial Fixtures - Use fixture_generator.py
Create Test Spec Template - Run test_spec_generator.py with sample requirement
Configure TDD Workflow - Set up tdd_workflow.py for team use
Document Process - Reference tdd_methodology.md for team onboarding
Expected Output: Project configured for TDD with team documentation
Python Tools
test_suite_generator.py
Generates comprehensive test suites from source code analysis with unit, integration, and edge case coverage.
Key Features:
Automated test scaffolding for React/Next.js/Node.js
Unit test generation with Jest/React Testing Library patterns
Integration test templates with database and API mocking
Edge case identification and test generation
Test naming conventions and file structure automation
Common Usage:
# Generate test suite for component
python scripts/test_suite_generator.py src/components/Button.tsx
# Generate tests for entire directory
python scripts/test_suite_generator.py src/components/ --recursive
# Help
python scripts/test_suite_generator.py --help
Use Cases:
Scaffolding tests for new components or modules
Ensuring consistent test structure across codebase
Accelerating test development for large codebases
Training junior engineers on testing patterns
coverage_analyzer.py
Analyzes test coverage with detailed gap identification and actionable recommendations for improvement.
Key Features:
Line, branch, and function coverage metrics
Coverage gap identification by file and function
Priority scoring (critical paths vs. utility functions)
Historical trend analysis
Integration with Jest, Istanbul, and NYC coverage tools
Visual coverage reports with heat maps
Common Usage:
# Analyze coverage for project
python scripts/coverage_analyzer.py .
# Detailed report with recommendations
python scripts/coverage_analyzer.py . --verbose
# JSON output for CI/CD integration
python scripts/coverage_analyzer.py . --output json
# Help
python scripts/coverage_analyzer.py --help
Use Cases:
Identifying untested code before production
Setting coverage targets and tracking progress
Prioritizing test development efforts
Generating coverage reports for stakeholders
e2e_test_scaffolder.py
Scaffolds end-to-end test infrastructure with Cypress or Playwright including page objects, test data, and CI/CD integration.
# Use the analyzer script
python scripts/coverage_analyzer.py .
# Review recommendations# Apply fixes
3. Implement Best Practices
Follow the patterns and practices documented in:
references/testing_strategies.md
references/test_automation_patterns.md
references/qa_best_practices.md
Best Practices Summary
Code Quality
Follow established patterns
Write comprehensive tests
Document decisions
Review regularly
Performance
Measure before optimizing
Use appropriate caching
Optimize critical paths
Monitor in production
Security
Validate all inputs
Use parameterized queries
Implement proper authentication
Keep dependencies updated
Maintainability
Write clear code
Use consistent naming
Add helpful comments
Keep it simple
Common Commands
# Development
npm run dev
npm run build
npm run test
npm run lint
# Analysis
python scripts/coverage_analyzer.py .
python scripts/e2e_test_scaffolder.py --analyze
# Deployment
docker build -t app:latest .
docker-compose up -d
kubectl apply -f k8s/
Troubleshooting
Common Issues
Check the comprehensive troubleshooting section in references/qa_best_practices.md.
