From 5e8a2e98996a76dd84f38d4eaa5a8a756e1d50b4 Mon Sep 17 00:00:00 2001 From: Cristian Magherusan-Stanciu Date: Thu, 28 May 2026 17:00:50 +0200 Subject: [PATCH] test(frontend/settings): document grace-toast fix history (closes #514) PR #478 aggregated per-provider grace validation into one toast; the test assertions still expected the old per-provider wording, causing a pre-existing CI failure on feat/multicloud-web-frontend. PR #548 updated the assertions to match. Add a history note in the file header so the next reader understands why the expected message format is aggregated. --- frontend/src/__tests__/settings-purchasing-grace.test.ts | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/frontend/src/__tests__/settings-purchasing-grace.test.ts b/frontend/src/__tests__/settings-purchasing-grace.test.ts index 67b470241..fe6e8c9b7 100644 --- a/frontend/src/__tests__/settings-purchasing-grace.test.ts +++ b/frontend/src/__tests__/settings-purchasing-grace.test.ts @@ -9,6 +9,14 @@ * - Out-of-range input (< 0, > 30, non-integer) is rejected with a * targeted toast instead of silently succeeding or being clamped. * - Reset-to-defaults restores every input to 7. + * + * History: PR #478 aggregated per-provider validation errors into a single + * toast (one call listing every failing provider in input order rather than + * bailing on the first). The assertions here were originally written for the + * per-provider wording ("AWS grace period: Must be...") and updated in + * PR #548 to match the aggregated format ("Grace period must be a whole + * number between 0 and 30 days (AWS)."). Issue #514 tracked the pre-existing + * CI failure caused by the mismatch; PR #548 resolved it. */ import { loadGlobalSettings, saveGlobalSettings, resetSettings, setupSettingsHandlers } from '../settings';