AGENT SKILL

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 automation
  • test-driven-development - TDD

Actions

  1. Define testing strategy
  2. Choose testing frameworks
  3. Plan test coverage
  4. Set up test infrastructure
  5. 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/Vitest
  • python-testing-patterns - pytest
  • unit-testing-test-generate - Test generation
  • tdd-orchestrator - TDD orchestration

Actions

  1. Write unit tests
  2. Set up test fixtures
  3. Configure mocking
  4. Measure coverage
  5. 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 testing
  • e2e-testing-patterns - Integration patterns

Actions

  1. Design integration tests
  2. Set up test databases
  3. Configure API mocks
  4. Test service interactions
  5. 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 testing
  • e2e-testing-patterns - E2E patterns
  • webapp-testing - Web app testing

Actions

  1. Design E2E scenarios
  2. Write test scripts
  3. Configure test data
  4. Set up parallel execution
  5. 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 automation
  • webapp-testing - Browser testing
  • screenshots - Screenshot automation

Actions

  1. Set up browser automation
  2. Configure headless testing
  3. Implement visual testing
  4. Capture screenshots
  5. 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 engineering
  • performance-profiling - Performance profiling
  • web-performance-optimization - Web performance

Actions

  1. Design performance tests
  2. Set up load testing
  3. Measure response times
  4. Identify bottlenecks
  5. Optimize performance

Copy-Paste Prompts

Use @performance-engineer to test application performance

Phase 7: Code Review

Skills to Invoke

  • code-reviewer - AI code review
  • code-review-excellence - Review best practices
  • find-bugs - Bug detection
  • security-scanning-security-sast - Security scanning

Actions

  1. Configure review tools
  2. Run automated reviews
  3. Check for bugs
  4. Verify security
  5. 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 - Linting
  • verification-before-completion - Verification

Actions

  1. Configure linters
  2. Set up formatters
  3. Define quality metrics
  4. Implement gates
  5. 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

YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

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.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

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.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

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.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

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.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

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.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

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.

★ 1