Testing & CI/CD Architect

To architect CI/CD pipelines with quality gates, you enforce coverage thresholds and automation steps for linting, unit, integration, and e2e stages using template workflows for GitHub Actions and GitLab CI.

Balancing a test pyramid involves running fast unit tests alongside targeted integration scenarios and minimal end-to-end journeys, ensuring feedback stays fast and meaningful across your web application validation stages.

Yes, you can use GitHub Actions and GitLab CI to enforce testing strategies for Jest and Playwright by applying framework-agnostic patterns with naming conventions, mocking strategies, and deterministic reporting.

Setting up automated testing and QA gate reporting involves applying framework-agnostic patterns for Jest, Vitest, Playwright, and Cypress to keep automation deterministic and reproducible across pipeline runs.

Configuring lint, type checks, and Lighthouse scans requires running generic scripts with dependencies like jq and bc to execute quality gates and calculate coverage thresholds within your reproducible CI/CD environments.