ExpertPW-TKT-00660 minutesPlaywright

Prove ticket session isolation

Two Lab sessions must never see each other’s synthetic ticket mutations.

  • api
  • isolation
  • authentication

Objective

What to automate

Create a ticket in one header-mode session, prove it is absent from another, then reset the first.

Preconditions and test data

Preconditions

  • Use a fresh isolated Practice Lab browser context.
  • Open the fixture identified by FX-TKT-001.

Test data

  • session A: tkt-a
  • session B: tkt-b

Expected result

Session B never contains Session A data and reset affects only session A.

Progressive hints

Hint 1

Create two explicit Lab sessions.

Hint 2

Use each session CSRF token for mutations.

Hint 3

Compare ticket responses before and after resetting session A.

I’ve tried it — show solution
  1. Create two explicit Lab sessions.
  2. Use each session CSRF token for mutations.
  3. Compare ticket responses before and after resetting session A.

The deliberately failing starter is in tests/ticketing.spec.ts inside the TypeScript starter ZIP.