Make the schedule performance run include slow devices and empty results
The fastest desktop run became the benchmark. It misses the narrow layout and empty-filter transition used by coordinators on older laptops.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Performance testing · Browser automation
Estimated field mix
- Quality engineering50%
- Performance engineering30%
- Frontend20%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional repair coordinator opens a week containing 2,000 jobs. The initial page loads, but filtering and selecting a job can freeze the interface. Build a synthetic scheduling screen with keyboard operation before measuring changes.
Setup prerequisites
- Create a local schedule UI with 2,000 synthetic jobs, long labels, empty results and deterministic responses.
- Record browser version, viewport, device emulation, CPU/network throttling and build mode for every comparison.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- PWEB-101 · Record the schedule workflow that freezes after filtering
- PWEB-102 · Identify which schedule code is shipped before the first interaction
- PWEB-104 · Load the schedule export code when export is requested
- PWEB-103 · Measure long tasks caused by filtering rather than counting renders alone
- PWEB-105 · Render only the visible schedule rows without losing keyboard position
Acceptance criteria
- Define two repeatable local profiles with explicit viewport, throttling and cache state.
- Run nonempty, empty and large-label workflows and assert visual state plus selected identity.
- Separate trace artifacts by profile and build revision; invalid runs report failure instead of a zero timing.
Implementation constraints
- Emulation defines an exercise profile, not a claim to reproduce every physical device.
Verification to include
- Execute both profiles three times with a fixed warmup rule and retain all measurements.
- Remove a required result element deliberately and confirm the run fails its correctness check before reporting success.
Deliverables
- Browser profile matrix and repeatable benchmark command
Rollout and recovery
Use both profiles in local release review; revise profiles only with a recorded reason and a new baseline.
Value of the work
For the engineer: Connect bundle, rendering and interaction measurements to user-visible behavior without losing accessibility.
For the team: Produce a bounded performance investigation and regression workflow for dense operational interfaces.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.