cesnimda/jobtrackingapp
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

test(calendar): qualify connected follow-up and agenda refresh

Browse Source
This commit is contained in:
cesnimda
2026-11-09 22:12:27 +01:00
parent c0ef4171d5
commit e585561a02
112 changed files with 2770 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ui-modernisation/visual-correction/FOLLOWUP_JOURNEY_REVIEW.md
+17
View File
@@ -0,0 +1,17 @@
# Application status, follow-up and agenda refresh
4 November 2026. Runtime `c0ef4171d5451abfeba09321990380c395728c20`, after local CV-caption receipte70c7098. Remote publication was HTTP502 at that preceding checkpoint; do not infer remote identity from local commits.
The initial unchanged-source122956 client journey passed8 configurations/40 states: Table→Board→Waiting→actual app navigation (including phone More)→Reminders→schedule3 days ahead→linked application context. Its source-bound evidence is retained in `evidence/followup-before-agenda`. It did not verify agenda refresh and is not a complete successor pass or additive total.
Extending the fixture to expose the recorded date reproduced a real stale-agenda defect: the reminder card updates but CalendarAgenda remains empty. CalendarPage renders the two siblings independently; only the reminder resource reloads after PATCH. Browser failure and native RED are retained. The native test independently reproduces the missing agenda link after successful scheduling.
Fix at the existing common parent: CalendarPage owns a small refresh counter, CalendarAgenda includes its optional token in existing resource dependencies, and RemindersView notifies only after a successful follow-up PATCH. No event bus, polling, provider/model, dependency, data model, migration or backend endpoint change. Every production caller was inspected; optional props preserve standalone callers/tests. The agenda stays mounted, preserving selected month/date/view instead of resetting it.
PASSED:23 native cases/four suites (new cross-component scheduling/clear/failure/view-preservation regression, existing agenda/reminder/calendar-action contracts), type-check, full lint, build and whitespace checks. The new test freezes synthetic time; it is not native-device or production scheduling evidence. Scheduling and clearing each refresh once; failed PATCH does not refresh; selected month and month-grid preference survive.
PASSED successor browser qualification:8 representative390/1440×EN/NB×theme journeys/48 states, six each including the refreshed agenda and linked context. Zero unavailable reads, page exceptions, unexpected writes or axe violations. The overlapping pilot1/6 is not additive. Every response/write is intercepted: exactly eight existing status PATCHes and eight date-only follow-up PATCHes. Date calculation retains the existing UTC-slice3-day policy; original timezone precision, interview appointments and provider calendars remain separate gaps. No email/provider job or actual database scheduling runs.
Examples: [phone refreshed agenda](evidence/followup-journey/agenda-refreshed-en-light-390.png), [desktop Bokmål/dark agenda](evidence/followup-journey/agenda-refreshed-nb-dark-1440.png), [phone linked context](evidence/followup-journey/linked-context-en-light-390.png). Frozen A3 calendar references remain at [390](evidence/reference/approved-calendar-390.png) and [1440](evidence/reference/approved-calendar-1440.png).
Remaining: actual backend scheduling/tenant/revision qualification, failure/retry across navigation, original timezone/precision data model and human/native/owner acceptance. Historical unchanged date-rendering evidence stays source-bound; no PDF metrics reopened. Rollback reverts the parent/token/callback delta and its regression; no data rollback. Full A3/Phase10/European/integrated security/recovery/release acceptance remain OPEN.