QRun-IO/qbit-web-performance
3
0 Fork 0
Code Issues 2 Pull Requests 2 Actions Packages Projects Releases 7 Wiki Activity

Regressions, budget checks, site changes and comparisons are never written #8

New Issue
Open
opened 2026-10-14 15:24:55 +00:00 by KofTwentyTwo · 0 comments
KofTwentyTwo commented 2026-10-14 15:24:55 +00:00 (Migrated from github.com)
Copy link
Copy source

Found while writing the in-app help text (Website-Backend#196). (kof22 pins 0.1.0-RC.1; verified on origin/develop 31a33dc.)

The tables exist (WebPerfSchema.java:39,44: REGRESSION, BUDGET, CHANGE_EVENT, COMPARISON) with list screens, but no service code writes them: outside the schema/model/metadata packages the only reference is a hard-coded open_regression_count = 0 (service/WebPerfService.java:208). Budgets are seeded but never evaluated; the Dismiss and Mark resolved actions exist only in the design doc (qqq docs/specs/2026-10-12-web-performance-design.md). deploymentId and cdnStage on lab runs are never written. Also: Tested Pages allows Insert but only Label, Tier and Enabled are editable and URL is required, so a manual insert is impossible; Tier, Scope, Source, Strategy, Metric, Comparator and Severity are free text, so a typo (for example "key" for KEY) silently drops a page from the daily key-page tests.

Expected: implement regression/budget evaluation, or hide the tables until then; add dropdowns for the string enums.

Found while writing the in-app help text (Website-Backend#196). (kof22 pins 0.1.0-RC.1; verified on origin/develop 31a33dc.) The tables exist (WebPerfSchema.java:39,44: REGRESSION, BUDGET, CHANGE_EVENT, COMPARISON) with list screens, but no service code writes them: outside the schema/model/metadata packages the only reference is a hard-coded `open_regression_count = 0` (service/WebPerfService.java:208). Budgets are seeded but never evaluated; the Dismiss and Mark resolved actions exist only in the design doc (qqq docs/specs/2026-10-12-web-performance-design.md). `deploymentId` and `cdnStage` on lab runs are never written. Also: Tested Pages allows Insert but only Label, Tier and Enabled are editable and URL is required, so a manual insert is impossible; Tier, Scope, Source, Strategy, Metric, Comparator and Severity are free text, so a typo (for example "key" for KEY) silently drops a page from the daily key-page tests. **Expected:** implement regression/budget evaluation, or hide the tables until then; add dropdowns for the string enums.
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
bug
Something isn't working
 dependencies
documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 github_actions
Pull requests that update GitHub Actions code
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 java
Pull requests that update java code
 question
Further information is requested
 release:rc
Merging this develop PR cuts the next release candidate
 secuurity
ux
Admin UX / information architecture
 wontfix
This will not be worked on
No labels bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
forge-recovery (Forge Recovery) james.maes (James Maes)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: QRun-IO/qbit-web-performance#8