Phase 28 · Lesson 09

Playwright Critical End to End Workflows

≈ 2 min core reading · 167 source/companion words

Learning contract

What you should be able to do after this

Explain Playwright Critical End to End Workflows without relying on framework buzzwords.
Connect the lesson to the phase outcome: Build a testing strategy that proves pure rules, service orchestration, repositories, HTTP contracts, frontend behavior, and critical browser flows at the right cost.
Reproduce the relevant behavior and verify it with evidence.
Diagnose at least one representative failure instead of guessing.

Figure 28.9 — TaskFlow boundary map

risk/question

choose boundary

arrange controlled state

execute behavior

assert outcome/contract

cleanup

This lesson belongs to Phase 28. Keep the full request/data path visible even when today's code changes only one box.

Instructor workflow: predict first → implement the smallest slice → run it → inspect evidence → break one assumption → diagnose → explain it back. Do not copy the whole code block before understanding the first failing boundary.

Playwright Critical End-to-End Workflows TaskFlow - Full Stack Developer 2026

What belongs in browser E2E Critical TaskFlow user journey

Browser Next.js NestJS Prisma Postgres sign in form auth/rules query state

Playwright critical-path test one test can prove the wiring across the stack

Browser tests are expensive but high-confidence. Reserve them for workflows where broken wiring, navigation, authentication, JavaScript behavior or browser semantics would hurt users materially.

Recommended TaskFlow journey • Start with a known test account/session fixture.

• Open authorized Workspace Tasks.

• Create a Task through the real form.

• Observe it in the list.

• Change status and confirm UI converges.

• Reload the page and confirm persistence.

• Attempt one forbidden action with a lower-privilege user.

Locator rule await page.getByRole("button", { name: "Create task", }).click()

await page.getByLabel("Title") .fill("Prepare payroll")

await expect( page.getByText("Prepare payroll"), ).toBeVisible()

Production-like execution Next.js recommends running Playwright against a built/running app for production-like behavior. Playwright gives each test an isolated browser context and supports Chromium, Firefox and WebKit.

Executable lesson studio · ci

Now turn the explanation into engineering skill.

CI turns repository rules into automated gates. A useful pipeline must be understandable, reproducible locally, secure, and able to fail for the right reasons.

By the end, you should be able to

Explain Playwright Critical End to End Workflows in terms of concrete inputs, ownership, outputs, and evidence.
Implement or reproduce the smallest TaskFlow slice that demonstrates this ci concept.
Diagnose one representative ci failure using observable evidence instead of trial-and-error.

Figure 28.9B — Mental model

git event

runner

install

quality gates

artifact/deploy decision

Read left-to-right while implementing. When debugging, walk right-to-left until the first observed fact differs from your prediction.

Code-along sequence

One coherent change at a time

01
Restate the goal of “Playwright Critical End to End Workflows” as one observable behavior. Write the success signal before touching code.
02
Trace the boundary map: git event → runner → install → quality gates → artifact/deploy decision. Mark the one boundary this lesson changes.
03
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
04
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
05
Connect the slice to TaskFlow’s phase artifact: Vitest + integration + Playwright test suite with deterministic fixtures and CI-ready commands.. Verify behavior from the outside as a user or API client would.
06
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
07
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.

yamlBuild the quality gate one step at a time

name: CI
on: [pull_request]

jobs:
  verify:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: corepack enable
      - run: pnpm install --frozen-lockfile
      - run: pnpm lint && pnpm typecheck && pnpm test && pnpm build

Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.

Verification

Prove the happy path

Run the narrowest relevant command or request and require a clean exit/status.
Inspect the boundary-specific evidence: terminal output, Network panel, database row/query plan, test report, container health, or deployment logs.
Repeat the behavior once after the change so a one-off cached or stale result cannot masquerade as success.

Break it on purpose

Build debugging memory

Mocking the thing the test is supposed to prove
Change one assumption in the ci example—identity, input, configuration, ordering, connectivity, or state—and predict the exact symptom before running it.

SymptomInvestigation path

Works locally, fails in CI

Compare Node/pnpm versions, lockfile state, environment variables, OS assumptions, and generated artifacts.

Workflow has excessive privileges

Set least-privilege permissions at workflow/job level and isolate untrusted pull-request code from secrets.

Closed-reference challenge

Can you transfer the idea?

Without copying the final source, create a second small scenario that applies “Playwright Critical End to End Workflows” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.

Explain-back

Answer these without reopening the solution

What problem does Playwright Critical End to End Workflows solve in TaskFlow, and what would be observably wrong without it?
Which part of the ci boundary owns the decision, and which neighboring layer must not own it?
What evidence proves the happy path instead of merely suggesting it worked?
Name one realistic failure or abuse case and the first place you would inspect.
If requirements doubled tomorrow, which part of this design should stay stable and which part is allowed to change?

Lesson studio

Turn the reading into skill

Do it

Test a service with controlled dependencies and assert business outcome rather than private calls.

Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.

Break it safely

Mocking the thing the test is supposed to prove

Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.

Explain it back

Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?

If your explanation is vague, repeat the boundary trace before moving on.

Exit ticket

Before marking complete

Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.

← TanStack Query Testing and Cache Isolation Fixtures Factories Determinism and Isolation →