← Back to Skills Marketplace
Senior Qa
by
Emerson Braun
· GitHub ↗
· v1.0.0
· MIT-0
82
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install eb-senior-qa
Description
Comprehensive QA and testing skill for quality assurance, test automation, and testing strategies for ReactJS, NextJS, NodeJS applications. Includes test sui...
README (SKILL.md)
Senior Qa
Complete toolkit for senior qa with modern tools and best practices.
Quick Start
Main Capabilities
This skill provides three core capabilities through automated scripts:
# Script 1: Test Suite Generator
python scripts/test_suite_generator.py [options]
# Script 2: Coverage Analyzer
python scripts/coverage_analyzer.py [options]
# Script 3: E2E Test Scaffolder
python scripts/e2e_test_scaffolder.py [options]
Core Capabilities
1. Test Suite Generator
Automated tool for test suite generator tasks.
Features:
- Automated scaffolding
- Best practices built-in
- Configurable templates
- Quality checks
Usage:
python scripts/test_suite_generator.py \x3Cproject-path> [options]
2. Coverage Analyzer
Comprehensive analysis and optimization tool.
Features:
- Deep analysis
- Performance metrics
- Recommendations
- Automated fixes
Usage:
python scripts/coverage_analyzer.py \x3Ctarget-path> [--verbose]
3. E2E Test Scaffolder
Advanced tooling for specialized tasks.
Features:
- Expert-level automation
- Custom configurations
- Integration ready
- Production-grade output
Usage:
python scripts/e2e_test_scaffolder.py [arguments] [options]
Reference Documentation
Testing Strategies
Comprehensive guide available in references/testing_strategies.md:
- Detailed patterns and practices
- Code examples
- Best practices
- Anti-patterns to avoid
- Real-world scenarios
Test Automation Patterns
Complete workflow documentation in references/test_automation_patterns.md:
- Step-by-step processes
- Optimization strategies
- Tool integrations
- Performance tuning
- Troubleshooting guide
Qa Best Practices
Technical reference guide in references/qa_best_practices.md:
- Technology stack details
- Configuration examples
- Integration patterns
- Security considerations
- Scalability guidelines
Tech Stack
Languages: TypeScript, JavaScript, Python, Go, Swift, Kotlin Frontend: React, Next.js, React Native, Flutter Backend: Node.js, Express, GraphQL, REST APIs Database: PostgreSQL, Prisma, NeonDB, Supabase DevOps: Docker, Kubernetes, Terraform, GitHub Actions, CircleCI Cloud: AWS, GCP, Azure
Development Workflow
1. Setup and Configuration
# Install dependencies
npm install
# or
pip install -r requirements.txt
# Configure environment
cp .env.example .env
2. Run Quality Checks
# 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.mdreferences/test_automation_patterns.mdreferences/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.
Getting Help
- Review reference documentation
- Check script output messages
- Consult tech stack documentation
- Review error logs
Resources
- Pattern Reference:
references/testing_strategies.md - Workflow Guide:
references/test_automation_patterns.md - Technical Guide:
references/qa_best_practices.md - Tool Scripts:
scripts/directory
Usage Guidance
This package appears safe from a security/coherence perspective, but it's important to note the code is largely a stub: it only validates a path and emits empty results while the docs promise advanced analysis and automated fixes. Before using: (1) review the three Python scripts locally to confirm behavior, (2) run them in a sandbox or on non-sensitive test repositories (don't point them at production directories containing secrets), (3) don't rely on the tool for critical QA decisions until the analysis logic is implemented or audited, (4) check for a requirements.txt or other dependencies before running pip/npm commands, and (5) if you need the promised advanced features, either request the author for a full implementation or use a well-maintained QA tool with an established audit trail.
Capability Assessment
Purpose & Capability
The skill claims production-grade test generation, deep coverage analysis, automated fixes and E2E scaffolding across many stacks, but the three included Python scripts are lightweight scaffolds that only validate a target path and return empty 'findings'. The documentation and reference files are coherent with a QA tool, but the actual code does not implement the advanced features described (overstatement of capability).
Instruction Scope
SKILL.md instructs the agent/user to run the included scripts and consult packaged reference docs. The runtime instructions do not direct the agent to read unexpected system files or remote endpoints. The scripts only require a filesystem path to analyze and optionally write an output file; they do not access environment variables or network resources.
Install Mechanism
There is no install spec (instruction-only for runtime) and no external downloads or archive extraction. SKILL.md suggests common setup commands (npm install, pip install -r requirements.txt) but no requirements.txt or package manifests are included — this is a usability issue, not a security risk.
Credentials
The skill declares no required environment variables or credentials. The documentation suggests copying .env.example to .env, but neither the scripts nor the SKILL.md require secrets or other unrelated credentials. The scripts do not read environment variables.
Persistence & Privilege
The skill does not request permanent/always inclusion (always: false) and does not modify other skills or system-wide settings. It operates as a normal, user-invocable tool.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install eb-senior-qa - After installation, invoke the skill by name or use
/eb-senior-qa - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of the senior-qa skill, providing a comprehensive toolkit for quality assurance and testing.
- Includes automated scripts for test suite generation, coverage analysis, and E2E test scaffolding for ReactJS, NextJS, and NodeJS applications.
- Offers detailed reference documentation covering testing strategies, test automation patterns, and QA best practices.
- Supports a modern tech stack with guidance on development workflow, best practices, common commands, troubleshooting, and technical resources.
- Designed for use in designing test strategies, writing and automating tests, and analyzing quality metrics.
Metadata
Frequently Asked Questions
What is Senior Qa?
Comprehensive QA and testing skill for quality assurance, test automation, and testing strategies for ReactJS, NextJS, NodeJS applications. Includes test sui... It is an AI Agent Skill for Claude Code / OpenClaw, with 82 downloads so far.
How do I install Senior Qa?
Run "/install eb-senior-qa" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Senior Qa free?
Yes, Senior Qa is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Senior Qa support?
Senior Qa is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Senior Qa?
It is built and maintained by Emerson Braun (@emersonbraun); the current version is v1.0.0.
More Skills