From 261f17a1176d039e84c4a4c8d690aed22f872917 Mon Sep 17 00:00:00 2001 From: Denozordec Date: Tue, 27 Oct 2026 13:12:35 +0700 Subject: [PATCH] Settings test: a 60 s timeout for the thirteen-click backup scenario on CI Co-Authored-By: Claude Sonnet 5.5 --- src/screens/settings/Settings.test.tsx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/screens/settings/Settings.test.tsx b/src/screens/settings/Settings.test.tsx index 1813d4c..3f8b0b7 100644 --- a/src/screens/settings/Settings.test.tsx +++ b/src/screens/settings/Settings.test.tsx @@ -344,7 +344,7 @@ describe('Settings: action bar', () => { }) /* - With a timeout of its own, and not on a whim: this test does THIRTEEN `userEvent` + With a timeout of its own (60 s: the CI runner is several times slower than a laptop), and not on a whim: this test does THIRTEEN `userEvent` interactions (it opens the dialog and unticks the twelve checkboxes), and each one goes through `act()`. On its own the whole file takes 5.9 s against a five-second per-test cap, so this one lived right on the edge: it passed or not depending on @@ -355,7 +355,7 @@ describe('Settings: action bar', () => { behaved exactly the same. It is not sped up here because the thirteen interactions are the scenario ("a backup with nothing ticked"), and trimming them would be testing something else. */ - it('a backup with nothing checked alerts with the literal text', { timeout: 15000 }, async () => { + it('a backup with nothing checked alerts with the literal text', { timeout: 60000 }, async () => { server() await mount() await userEvent.click(screen.getByRole('button', { name: 'Backup Settings' }))