Automate Comprehensive Testing and QA
Testing/QA Workflow Bundle orchestrates an 8-phase pipeline: strategy, unit/integration/E2E tests, performance, review, and gates.
Why it matters
Establish a robust testing and quality assurance pipeline for production-ready software, encompassing unit, integration, E2E, and browser automation.
Outcomes
What it gets done
Implement unit, integration, and E2E testing strategies.
Automate browser interactions and visual regression testing.
Integrate code review, security scanning, and quality gates.
Configure CI/CD for automated testing and validation.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-testing-qa | bash Overview
Testing/QA Workflow Bundle
Testing/QA Workflow Bundle orchestrates an eight-phase testing pipeline - strategy, unit, integration, E2E, browser automation, performance, code review, and quality gates - naming the skill to invoke at each stage. Use it to set up or run a full testing/QA pipeline end to end. Related bundles handle development, security audits, CI/CD, and AI-specific testing separately.
What it does
Testing/QA Workflow Bundle is an eight-phase orchestration workflow for building a complete testing and quality-assurance pipeline: test strategy, unit testing, integration testing, E2E testing, browser automation, performance testing, code review, and quality gates. Each phase names the specific skills it invokes and the copy-paste prompt to trigger them, rather than doing the work itself directly.
When to use - and when NOT to
Use it when setting up testing infrastructure from scratch, or when any single phase needs to happen in the context of the full pipeline - writing unit and integration tests, implementing E2E and browser automation, establishing performance benchmarks, or running code review and quality gates before shipping. It follows a 70/20/10 unit/integration/E2E testing pyramid as its target test mix, and gates a release on a specific checklist: unit coverage above 80%, all tests passing, E2E coverage of critical paths, performance benchmarks met, a passed security scan, an approved code review, and clean linting. Related bundles handle adjacent workflows - development for the coding workflow itself, security-audit for dedicated security testing, cloud-devops for CI/CD, and ai-ml for AI-specific testing - so this bundle is the one to reach for specifically when the task is testing/QA end to end, not one of those neighboring concerns.
Inputs and outputs
Input: which phase, or phases, of the testing pipeline are needed. Output: the exact skill to invoke per phase - test-automator and test-driven-development for strategy; javascript-testing-patterns (Jest/Vitest), python-testing-patterns (pytest), unit-testing-test-generate, and tdd-orchestrator for unit tests; api-testing-observability-api-mock and e2e-testing-patterns for integration; playwright-skill, e2e-testing-patterns, and webapp-testing for E2E; browser-automation, webapp-testing, and screenshots for browser automation; performance-engineer, performance-profiling, and web-performance-optimization for performance; code-reviewer, code-review-excellence, find-bugs, and security-scanning-security-sast for review; and lint-and-validate plus verification-before-completion for quality gates - each phase paired with a concrete action checklist, for example on unit testing: write tests, set up fixtures, configure mocking, measure coverage, integrate with CI.
Integrations
Composes with roughly twenty named sibling skills across its eight phases, spanning frameworks like Jest, Vitest, pytest, and Playwright, security scanning via SAST tooling, and hands off to the related workflow bundles development, security-audit, cloud-devops, and ai-ml for adjacent concerns outside strict testing/QA scope.
Who it's for
Teams or developers who need a structured, end-to-end testing and QA pipeline - from strategy through unit, integration, E2E, and performance testing to code review and release-gating - with a ready-made checklist and the specific skill to invoke at each stage, rather than assembling the pipeline from scratch.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.