GitHub Action Planned
First-class GitHub Action that runs your scenarios on pull requests and posts the report as a comment.
The scenarios you build for performance testing become smoke tests in CI. If your homepage-to-checkout journey fails after a deploy, the deploy fails. If a Web Vital regresses past your budget, the deploy fails.
Testing Suite is on the roadmap. We'll write to you when there's a usable build.
Performance testing tells you whether your site stays fast under load. That's once a release, maybe weekly. The other 95% of the week, you ship code without running it. Testing Suite is for that 95%.
It runs the scenarios you already built — homepage to checkout, search and add to cart, login and dashboard — on every deploy, as a CI gate. Same real browser. Same isolation. Same Web Vitals capture. Smaller scale, faster runtime.
If a step in the scenario breaks, the deploy fails. If LCP regresses past your budget on the staging build, the deploy fails. If a console error appears on the checkout page that wasn't there yesterday, the deploy fails. You catch what unit tests miss.
And because the scenarios are the same ones you performance test with, there's one place to maintain them. No duplicated test code between your QA and performance pipelines.
Here's the rough shape of what Testing Suite will ship with. We'll write to the waitlist as each piece lands.
First-class GitHub Action that runs your scenarios on pull requests and posts the report as a comment.
A GitLab CI template that drops into your pipeline. Same scenarios. Same report. Same gate.
Set per-test budgets. LCP under 2.5s. INP under 200ms. No console errors. Build fails when budgets break.
Trigger smoke tests from anything. Custom CI runners. Deployment hooks. Internal tools.
Side-by-side comparison of the current run versus the previous green build. See what got faster and what got slower.
Failure alerts in a channel. Includes the broken scenario, the failed step, and a link to the session video.