Vinix24/vnx-orchestration / skills/test-engineer
test-engineer
VerifiedTest engineer ensuring quality through unit, integration, and E2E testing strategies
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.2 KB |
| references/_MAPPING.md | markdown | 423 B |
| scripts/intelligence.shexecutable | script | 1.2 KB |
| template.md | markdown | 1.5 KB |
template.md
View on GitHub# Test Engineer Report Template
## Output Location
Write your report to: `$VNX_DATA_DIR/unified_reports/`
## Filename Format
`{timestamp}-{track}-testing-{title}.md`
Example: `20260202-143000-B-testing-api-integration.md`
## Report Structure
### Summary
Brief overview of testing work completed (2-3 sentences)
### Tags (Required)
- [tag1, tag2, tag3] # Use specific, compound tags (e.g., sse-streaming, browser-pool, kvk-validation). Avoid general-only tags.
### Test Strategy
- Testing approach taken
- Test types implemented (unit, integration, E2E)
- Coverage targets and achievements
- Risk areas identified
### Test Implementation
- Test files created/modified
- Test frameworks used
- Test data/fixtures created
- Mocking strategies employed
### Test Results
- Test execution summary
- Pass/fail statistics
- Coverage metrics
- Performance benchmarks
### Issues Found
- Bugs discovered
- Edge cases identified
- Performance bottlenecks
- Security vulnerabilities
### Evidence
- Test output logs
- Coverage reports
- Failed test details
- Performance profiling results
### Recommendations
- Additional test scenarios needed
- Coverage gaps to address
- Test infrastructure improvements
- CI/CD integration suggestions
### Intelligence Feedback
<!-- If your dispatch included [INTELLIGENCE_DATA] with offered_pattern_hashes, report which patterns you actually used: -->
used_pattern_hashes: []
## Quality Standards
- Minimum 80% code coverage
- All critical paths tested
- Edge cases documented
- Performance benchmarks established
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |