Recording of the visual regression run on event-planning-system-six.vercel.app · EventEase — app walkthrough.

In this video· click a step to jump to it

E
Passed

Test recording

EventEase — app walkthrough

65,015 ms · 0 pixels changed · matches baseline

We built this regression test for event-planning-system-six.vercel.app — it's yours to keep, free.

Take this test with you

This is a real Playwright test, recorded against event-planning-system-six.vercel.app. Claim it into your own workspace and re-run it on every deploy — free.

export async function test(page, baseUrl, screenshotPath, stepLogger) {
  const UA = 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36';
  await page.context().setExtraHTTPHeaders({ 'User-Agent': UA }).catch(() => {});
  for (const pat of [
    '**/cdn-cgi/scripts/**/email-decode.min.js',
    '**/browser.sentry-cdn.com/**',
    '**/cdn.segment.com/**',
    '**/connect.facebook.net/**',
    '**/www.googletagmanager.com/**',
    '**/static.hotjar.com/**',
    '**/*.clarity.ms/**',
  ]) { await page.route(pat, r => r.abort()).catch(() => {}); }
+114 more lines claim the test to get the full code.

Checks run

Run
Visual
Text
DOM
Network
Console
A11y
B
Perf
14 drift
URL
Variables
Full report
Log in →
0
Diff px
1m 05s
Duration
B
Accessible
WCAG 2.2 · 83
A
Fast
Web Vitals · 100

Notes from the demo run

AI-generated

We signed up as a customer and drove EventEase end to end: the venue and caterer directories, a venue detail page, your five-step create-event wizard, bookings and profile. The thing that stands out is that your directories already carry real, specific inventory (Olaola in Lagos, Savory Bites Catering in Lekki) rather than lorem placeholders, so the search-to-shortlist path feels like a working marketplace on the very first visit.

Highlights
  • Signup lands straight in the product
    Register then log in put us on /customer/dashboard with no email-verification wall. For a marketplace where the visitor is comparison-shopping, removing that inbox round-trip is the right call.
  • The wizard is properly staged
    Create event breaks into 5 labelled steps and asks only four things up front (name, type, date, guest count) before it shows venues. That is a much lower first-ask than most booking tools.
  • Real inventory in both directories
    Venues and caterers both render populated cards with location, capacity and cuisine, and the detail pages resolve cleanly from the listing links.
Friction points
  • /about and /help are placeholder pages
    Both render 'We're putting together our story' and 'under construction'. They are linked from the global footer, so a visitor evaluating trust hits a dead end. Either fill them or unlink them until they exist.
  • Dashboard stat tiles double up
    The dashboard shows Total/Pending/Confirmed/Rejected and then a second 'Booking status' block repeating Confirmed/Pending/Rejected. On an empty account it reads as eight zeros; collapsing to one row would make the first-run state calmer.

Share this run

Earned · Lastest awards

Proof your app is not AI slop

LASTEST
starter
tests
all passing
regressions
0
Badges stay live, ratchet upward, only downgrade on confirmed regression.
56,753 test runs recorded · 1,006 products tested with Lastest

This test was built for event-planning-system-six.vercel.app — claim it free

One click copies the test and baseline screenshots into your own Lastest workspace. Re-run on every deploy and catch regressions before your users do — free, no card required.