testing-qa
Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- testing-qa
- risk
- safe
- source
- personal
- category
- workflow-bundle
- date_added
- 2026-02-27
- description
- Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance.
03 SKILL.md 正文
Testing/QA Workflow Bundle
Overview
Comprehensive testing and quality assurance workflow covering unit tests, integration tests, E2E tests, browser automation, and quality gates for production-ready software.
When to Use This Workflow
Use this workflow when:
- Setting up testing infrastructure
- Writing unit and integration tests
- Implementing E2E tests
- Automating browser testing
- Establishing quality gates
- Performing code review
Workflow Phases
Phase 1: Test Strategy
Skills to Invoke
test-automator- Test automationtest-driven-development- TDD
Actions
- Define testing strategy
- Choose testing frameworks
- Plan test coverage
- Set up test infrastructure
- Configure CI integration
Copy-Paste Prompts
Use @test-automator to design testing strategy
Use @test-driven-development to implement TDD workflow
Phase 2: Unit Testing
Skills to Invoke
javascript-testing-patterns- Jest/Vitestpython-testing-patterns- pytestunit-testing-test-generate- Test generationtdd-orchestrator- TDD orchestration
Actions
- Write unit tests
- Set up test fixtures
- Configure mocking
- Measure coverage
- Integrate with CI
Copy-Paste Prompts
Use @javascript-testing-patterns to write Jest tests
Use @python-testing-patterns to write pytest tests
Use @unit-testing-test-generate to generate unit tests
Phase 3: Integration Testing
Skills to Invoke
api-testing-observability-api-mock- API testinge2e-testing-patterns- Integration patterns
Actions
- Design integration tests
- Set up test databases
- Configure API mocks
- Test service interactions
- Verify data flows
Copy-Paste Prompts
Use @api-testing-observability-api-mock to test APIs
Phase 4: E2E Testing
Skills to Invoke
playwright-skill- Playwright testinge2e-testing-patterns- E2E patternswebapp-testing- Web app testing
Actions
- Design E2E scenarios
- Write test scripts
- Configure test data
- Set up parallel execution
- Implement visual regression
Copy-Paste Prompts
Use @playwright-skill to create E2E tests
Use @e2e-testing-patterns to design E2E strategy
Phase 5: Browser Automation
Skills to Invoke
browser-automation- Browser automationwebapp-testing- Browser testingscreenshots- Screenshot automation
Actions
- Set up browser automation
- Configure headless testing
- Implement visual testing
- Capture screenshots
- Test responsive design
Copy-Paste Prompts
Use @browser-automation to automate browser tasks
Use @screenshots to capture marketing screenshots
Phase 6: Performance Testing
Skills to Invoke
performance-engineer- Performance engineeringperformance-profiling- Performance profilingweb-performance-optimization- Web performance
Actions
- Design performance tests
- Set up load testing
- Measure response times
- Identify bottlenecks
- Optimize performance
Copy-Paste Prompts
Use @performance-engineer to test application performance
Phase 7: Code Review
Skills to Invoke
code-reviewer- AI code reviewcode-review-excellence- Review best practicesfind-bugs- Bug detectionsecurity-scanning-security-sast- Security scanning
Actions
- Configure review tools
- Run automated reviews
- Check for bugs
- Verify security
- Approve changes
Copy-Paste Prompts
Use @code-reviewer to review pull requests
Use @find-bugs to detect bugs in code
Phase 8: Quality Gates
Skills to Invoke
lint-and-validate- Lintingverification-before-completion- Verification
Actions
- Configure linters
- Set up formatters
- Define quality metrics
- Implement gates
- Monitor compliance
Copy-Paste Prompts
Use @lint-and-validate to check code quality
Use @verification-before-completion to verify changes
Testing Pyramid
/ / \ E2E Tests (10%)
/---- / \ Integration Tests (20%)
/-------- / \ Unit Tests (70%)
/------------```
## Quality Gates Checklist
- [ ] Unit test coverage > 80%
- [ ] All tests passing
- [ ] E2E tests for critical paths
- [ ] Performance benchmarks met
- [ ] Security scan passed
- [ ] Code review approved
- [ ] Linting clean
## Related Workflow Bundles
- `development` - Development workflow
- `security-audit` - Security testing
- `cloud-devops` - CI/CD integration
- `ai-ml` - AI testing
## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.