mirror of
https://github.com/jcreek/LivingDexTracker.git
synced 2026-09-16 02:22:17 +00:00
acaf760b36
The server load fetched a full combined-data page at a 9999 item page size, carrying detail text and ownership fields the grid never renders, and the client re-fetched the same payload after hydration. Load a trimmed grid row instead and pack it as positional tuples so field names are not repeated for every one of a thousand-plus entries. Entry detail is fetched on demand from the new per-entry endpoint when a cell is opened, and the grid marks itself interactive so other page-start work can queue behind it.
20 lines
722 B
Gherkin
20 lines
722 B
Gherkin
Feature: Signed-in page speed
|
|
As a trainer
|
|
I want my Pokédexes to open and switch quickly
|
|
So that tracking catches never feels sluggish
|
|
|
|
Lighthouse CI covers the public pages; these budgets cover the signed-in ones it can't reach.
|
|
|
|
Background:
|
|
Given I am signed in
|
|
And I have a Living Dex named "Speed Check"
|
|
|
|
Scenario: A Pokédex opens without a second round trip for its entries
|
|
When I load the Pokédex page directly
|
|
Then its entries appear within 5 seconds
|
|
And the browser did not request the grid separately
|
|
|
|
Scenario: Moving between my Pokédex list and a Pokédex is quick
|
|
When I switch between my Pokédex list and the Pokédex
|
|
Then each switch finishes within 3 seconds
|