sparq:performance

To add performance testing to Playwright E2E tests, you can convert existing HP-category tests into scalable load scripts using tiered coverage with Web Vitals in-test checks and tools like k6 or Artillery for concurrency load testing.

Yes, you can use Lighthouse CI to establish performance gates in your pipeline. It provides threshold-based reporting and guardrails alongside Web Vitals tracking to prevent speed regressions before deployment.

The best way to measure Web Vitals under concurrent load is by combining in-test Web Vitals collection during Playwright runs with dedicated load testing tools like k6 or Artillery to simulate concurrent user traffic.

You can convert existing Playwright tests into load testing scripts by following framework-agnostic conversion guidance that transforms HP-category E2E tests into scalable k6 or Artillery performance scripts for CI integration.

No, you do not need separate pipelines. You can integrate performance testing directly alongside SparQ-generated E2E tests using CI-friendly practices with thresholds, reporting, and guardrails to ensure both speed and reliability.

You should use tiered performance testing coverage when you need to validate both in-test Web Vitals for individual user sessions and system reliability under concurrent load using CI gates to prevent performance regressions.