Timing of setup should be excluded for performance metrics
I want to use Checkly to monitor the performance of my signed-in homepage at a regular interval. That requires me to do:
1. Setup → authenticate and wait for redirect
2. The real test → load the homepage as a signed in user
I want to see the changes to 2 over time, and be alerted when there is a performance regression. I don’t care about the authentication piece because that’s out of my control.
Unfortunately, right now, it includes both steps in the check duration monitoring + graphs. I would like to remove the setup, or mark specific tests as the only ones that I care about for performance metrics. That would give me a high level overview of the performance metrics of just my homepage over time.
Log in to comment and vote
Comments2
Hervé Labas
Jul 21
Hi!
Playwright Overview now separates total check run, suite, and individual test durations, so authentication can be moved to a setup project/test and the homepage test trended independently.
Named
test.stepdurations remain per-run result detail only, and Playwright checks have no built-in threshold targeting one named step: so an explicit duration assertion would be needed to trigger failure alerts.Would this address your need?
María de Antón
Jul 31, 2025
Thank you so much for these, Ammar! It helps us improve Playwright Check Suites as we’re scoping the updates to the check overview page.