TESTHEON Practice Lab
ExpertPW-RT-00660 minutesPlaywright

Prove bounded polling stops after recovery

A production-minded test must distinguish an explicit finite update sequence from a hidden background poller.

  • network
  • error-recovery
  • assertions

Objective

What to automate

Complete a refresh or recovery sequence and prove that no extra request is initiated after the final visible state.

Preconditions and test data

Preconditions

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

Test data

  • sequence length: 3
  • background updates: disabled

Expected result

The completed sequence disables Run next poll and makes no additional ticket request without another learner action.

Open practice pageRead related guide

Progressive hints

Hint 1

Record the ticket request count before the final step.

Hint 2

Use the visible completion state as the synchronization point.

Hint 3

Assert that the action is disabled and the request count stays unchanged.

I’ve tried it — show solution
  1. Record the ticket request count before the final step.
  2. Use the visible completion state as the synchronization point.
  3. Assert that the action is disabled and the request count stays unchanged.

The deliberately failing starter is in tests/realtime-updates.spec.ts inside the TypeScript starter ZIP.