https://veriwasp-playtest-sandbox-3bgai6m71-veriwasp.vercel.app
desktop · VeriWasp Demo
Want this on your own app?
VeriWasp runs the same kind of test against your site, on demand or on every pull request via the GitHub App. Free credits, no card required.
Run history
Summary
Last step to pass: #01 navigate, Load the homepage (flagged, see below)
[warning] "[GSI_LOGGER]: Your client application uses one of the Google One Tap prompt UI status methods that may stop functioning when FedCM becomes mandatory.
[network] Fetch https://o205439.ingest.sentry.io/api/1323670/envelope/?sentry_key=d00780d432ac4ccf882f60dd02062e14&sentry_version=7&sentry_client=sentry.javascr
✕ Failed: #02 type, the Your name field
could not find an element matching "the Your name field"
⚠ 4 page-level issue(s) (accessibility), see below.
Suggested next step
Step 1 (homepage load) took 23.6s (up from 1.9s) and the screenshot is ~98% different from the last run, and every subsequent step (2, 4, 6) that depends on the signup form failed to find its target field/element — this pattern points to the homepage failing to render its normal signup form (likely stuck loading, a broken deploy, or a blocking error before the form mounts) rather than the test's selectors being wrong, especially since steps 2 and 4 explicitly regressed from passing to failing since the last run. Next action: open the Step 1 screenshot/report for this run and compare it to the prior run's screenshot to see what's actually on the page now (e.g., an error state, loading spinner, or missing form) — if the signup form isn't there, check recent deploys/commits around this Vercel preview for a build or rendering regression before touching the test steps.
Timeline
Replay
[warning] "[GSI_LOGGER]: Your client application uses one of the Google One Tap prompt UI status methods that may stop functioning when FedCM becomes mandatory.
[network] Fetch https://o205439.ingest.sentry.io/api/1323670/envelope/?sentry_key=d00780d432ac4ccf882f60dd02062e14&sentry_version=7&sentry_client=sentry.javascr
Visual diff vs previous run (changed regions highlighted)
could not find an element matching "the Your name field"
Before
After
Visual diff vs previous run (changed regions highlighted)
Locator: [data-playtest-id="3"]
Before
After
Visual diff vs previous run (changed regions highlighted)
could not find an element matching "the Password field"
Before
After
Visual diff vs previous run (changed regions highlighted)
Locator: [data-playtest-id="11"]
Before
After
Visual diff vs previous run (changed regions highlighted)
could not find an element matching "a welcome message greeting the new user by name"
Before
After
Visual diff vs previous run (changed regions highlighted)
Issues found
WCAG rates each accessibility rule Level A, AA, or AAA. Most teams target Level AA, which means fixing every Level A and AA failure. Level AAA and best-practice items are optional polish, not required for AA.
New to this? Read what WCAG is and why it matters, or how to fix the most common issues.
Step 2 (type) failed after 2 retries: the Your name field
could not find an element matching "the Your name field"
Step 4 (type) failed after 2 retries: the Password field
could not find an element matching "the Password field"
Step 6 (assert) failed after 3 retries: a welcome message greeting the new user by name
could not find an element matching "a welcome message greeting the new user by name"
1 browser console error(s) logged during the test
1 failed third-party request(s) (analytics, telemetry, or another external service), unlikely to affect your users
[network] Fetch https://o205439.ingest.sentry.io/api/1323670/envelope/?sentry_key=d00780d432ac4ccf882f60dd02062e14&sentry_version=7&sentry_client=sentry.javascript.browser%2F7.111.0 failed: net::ERR_FAILED
Elements must meet minimum color contrast ratio thresholds (1 element)
Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds
Links must be distinguishable without relying on color (2 elements)
Ensure links are distinguished from surrounding text in a way that does not rely on color
Zooming and scaling must not be disabled (1 element)
Ensure <meta name="viewport"> does not disable text scaling and zooming
All page content should be contained by landmarks (1 element)
Ensure all page content is contained by landmarks
Step 1 (navigate) looks 98.0% different from 2 days ago
This step's screenshot changed noticeably from the previous run of this flow. Could be a layout shift, a broken image, a font failing to load, or an intentional design change. Compare the screenshots on the report to tell which.
Step 1 (navigate) has 1 new console error(s) since 2 days ago
[warning] "[GSI_LOGGER]: Your client application uses one of the Google One Tap prompt UI status methods that may stop functioning when FedCM becomes mandatory. Refer to the migration guide to update your code accordingly and opt-in to FedC... (click to expand)
[warning] "[GSI_LOGGER]: Your client application uses one of the Google One Tap prompt UI status methods that may stop functioning when FedCM becomes mandatory. Refer to the migration guide to update your code accordingly and opt-in to FedCM to test your changes. Learn more: https://developers.google.com/identity/gsi/web/guides/fedcm-migration?s=dc#display_moment and https://developers.google.com/identity/gsi/web/guides/fedcm-migration?s=dc#skipped_moment"
Step 1 (navigate) has 1 new failed third-party request(s) since 2 days ago (analytics, telemetry, or another external service)
[network] Fetch https://o205439.ingest.sentry.io/api/1323670/envelope/?sentry_key=d00780d432ac4ccf882f60dd02062e14&sentry_version=7&sentry_client=sentry.javascript.browser%2F7.111.0 failed: net::ERR_FAILED
Step 1 (navigate) took 23.6s, up from 1.9s 2 days ago
This step has gotten noticeably slower than the previous run of this flow. Could be a new slow query, a bigger payload, or a third-party dependency slowing down.
Step 2 (type) passed 2 days ago and fails now
This step (the Your name field) passed in the previous run of this flow and now fails. Likely broken by a recent change.
Step 2 (type) looks 97.9% different from 2 days ago
This step's screenshot changed noticeably from the previous run of this flow. Could be a layout shift, a broken image, a font failing to load, or an intentional design change. Compare the screenshots on the report to tell which.
Step 2 (type) took 7.7s, up from 1.5s 2 days ago
This step has gotten noticeably slower than the previous run of this flow. Could be a new slow query, a bigger payload, or a third-party dependency slowing down.
Step 3 (type) looks 97.9% different from 2 days ago
This step's screenshot changed noticeably from the previous run of this flow. Could be a layout shift, a broken image, a font failing to load, or an intentional design change. Compare the screenshots on the report to tell which.
Step 4 (type) passed 2 days ago and fails now
This step (the Password field) passed in the previous run of this flow and now fails. Likely broken by a recent change.
Step 4 (type) looks 97.9% different from 2 days ago
This step's screenshot changed noticeably from the previous run of this flow. Could be a layout shift, a broken image, a font failing to load, or an intentional design change. Compare the screenshots on the report to tell which.
Step 4 (type) took 8.5s, up from 1.4s 2 days ago
This step has gotten noticeably slower than the previous run of this flow. Could be a new slow query, a bigger payload, or a third-party dependency slowing down.
Step 5 (click) looks 98.0% different from 2 days ago
This step's screenshot changed noticeably from the previous run of this flow. Could be a layout shift, a broken image, a font failing to load, or an intentional design change. Compare the screenshots on the report to tell which.
Step 5 (click) took 9.1s, up from 2.5s 2 days ago
This step has gotten noticeably slower than the previous run of this flow. Could be a new slow query, a bigger payload, or a third-party dependency slowing down.
Step 6 (assert) looks 98.0% different from 2 days ago
This step's screenshot changed noticeably from the previous run of this flow. Could be a layout shift, a broken image, a font failing to load, or an intentional design change. Compare the screenshots on the report to tell which.
▸ Show step-by-step technical detail
1 console error(s), 1 network error(s) (click to expand)
[warning] "[GSI_LOGGER]: Your client application uses one of the Google One Tap prompt UI status methods that may stop functioning when FedCM becomes mandatory. Refer to the migration guide to update your code accordingly and opt-in to FedCM to test your changes. Learn more: https://developers.google.com/identity/gsi/web/guides/fedcm-migration?s=dc#display_moment and https://developers.google.com/identity/gsi/web/guides/fedcm-migration?s=dc#skipped_moment"
[network] Fetch https://o205439.ingest.sentry.io/api/1323670/envelope/?sentry_key=d00780d432ac4ccf882f60dd02062e14&sentry_version=7&sentry_client=sentry.javascript.browser%2F7.111.0 failed: net::ERR_FAILED
Visual diff vs previous run (changed regions highlighted)
could not find an element matching "the Your name field"
Before
After
Visual diff vs previous run (changed regions highlighted)
Locator: [data-playtest-id="3"]
Before
After
Visual diff vs previous run (changed regions highlighted)
could not find an element matching "the Password field"
Before
After
Visual diff vs previous run (changed regions highlighted)
Locator: [data-playtest-id="11"]
Before
After
Visual diff vs previous run (changed regions highlighted)
could not find an element matching "a welcome message greeting the new user by name"
Before
After
Visual diff vs previous run (changed regions highlighted)
Screenshots and video are deleted 14 days after the run. Use the download buttons at the top of this report to keep it longer.
This report took one paste and a URL.
Run the same kind of test against your own SaaS. Free credits, no card required.
Test your SaaS free →