Testing & CI/CD Architect

What problem does it solve?

Developers struggle to keep test suites fast, reliable, and consistently enforced across unit, integration, and end-to-end layers while maintaining coverage thresholds, automation, and quality gates before merges and deployments.

Core Features & Use Cases

• Test Pyramid Strategy: Balance fast unit tests with targeted integration scenarios and minimal but critical end-to-end journeys so feedback stays fast and meaningful.
• CI/CD Pipelines & Quality Gates: Template workflows for GitHub Actions, GitLab CI, and generic scripts that run linting, type checks, coverage, security scans, and deploy steps whenever code changes.
• Framework Agnostic Patterns: Guidance for Jest, Vitest, Playwright, Cypress, MSW, and Lighthouse with naming conventions, mocking strategies, and reporting to keep automation deterministic and reproducible.

Quick Start

Analyze my project and outline a testing and CI/CD plan with coverage targets, QA gates, and automation steps for linting, unit, integration, and e2e stages.