test(e2e): skip the admin save happy-path test while #241 stands (#245) #246

Merged
bermudalamb merged 1 commits from fix/245-skip-flaky-admin-save into main 2026-08-30 16:36:13 -05:00
Showing only changes of commit 66c696ce40 - Show all commits
+17 -1
View File
@@ -59,7 +59,23 @@ test.describe('Admin save failures', () => {
await expect(adminInventory.row(name)).toBeVisible(); await expect(adminInventory.row(name)).toBeVisible();
}); });
test('saves an item successfully when the server accepts it', async ({ // SKIPPED, temporarily, to get main green while #241 is outstanding. See #245
// before deleting this comment or the skip.
//
// It fails in CI and passes locally, and which test fails moves around: a
// local parallel run of the whole suite on the same commit failed four
// *different* specs and not this one. That is #241 — fullyParallel against a
// single shared database — so fixing this test on its own would be guessing at
// a symptom that will simply reappear somewhere else.
//
// Not the image work from #226: addItem fills a name and a price and saves,
// attaching nothing, so the re-encoding path is never entered here.
//
// What this stops covering is not trivial. It is the only end-to-end check
// that adding an item actually reaches the database rather than just firing a
// toast — the happy path of the core admin action. Un-skip it as soon as #241
// lands; if it still fails then, it is a real defect and worth chasing.
test.skip('saves an item successfully when the server accepts it', async ({
page, page,
admin, admin,
adminInventory adminInventory