Test the User Journey — Frontend Testing Lab

09:00 – 10:15

Draw the pyramid for a frontend

—what each layer buys, testing behaviour vs implementation, mapping your suite

—Takeaway Your current tests mapped onto the pyramid — including the passing suite that would not catch your last real bug, named out loud.

10:30 – 11:45

Write component tests that survive refactors

—render-interact-assert, querying by role, Testing Library discipline

—Takeaway A component refactored aggressively with its test still green — because the test knew the behaviour, not the markup.

12:00 – 13:00

Test flows, not widgets

—forms with validation, routing flows, multi-component integration

—Takeaway A whole form flow tested through its states — invalid, submitting, failed, succeeded — as a user meets them.

14:00 – 15:15

Mock the API honestly

—network-level mocking, error and loading states, contract drift

—Takeaway Tests that exercise loading, error and empty states on demand — and fail loudly when the API contract quietly changes.

15:30 – 17:00

Assemble the fast suite

—suite structure, what not to test, coverage read honestly

—Takeaway A fast suite organised by behaviour with coverage read as a map of risk — not chased as a number.

09:00 – 10:15

Meet the real browser with Playwright

—first end-to-end test, locators that last, auto-waiting

—Takeaway Your application driven by a robot user in a real browser — watched live, then headless, with locators that survive a redesign.

10:30 – 11:45

Test the journeys that pay the bills

—the critical paths, authentication in E2E, test data setup and teardown

—Takeaway The login-to-done journey of your application tested end to end — with auth handled once, not re-clicked in every test.

12:00 – 13:00

Tame the flaky test

—why E2E flakes, waiting correctly, isolation and retries read honestly

—Takeaway A deliberately flaky test hunted to its root cause and fixed — not wrapped in retries and forgotten.

14:00 – 15:15

Wire the suite into CI

—the pipeline, parallelism, traces and screenshots on failure

—Takeaway The whole pyramid running on every push — with a failed journey leaving a trace you can replay like a recording.

15:30 – 17:00

Diagnose failures like a professional

—reading traces, triage discipline, the capstone review

—Takeaway A planted regression found from CI artifacts alone — no local re-run — and your suite defended layer by layer to the room.