Settings test: a 60 s timeout for the thirteen-click backup scenario on CI
CI / check (push) Successful in 3m23s
CI / image (push) Successful in 1m23s

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
This commit is contained in:
DenozordecandClaude Sonnet 5.5 committed 2026-10-27 13:12:35 +07:00
1 parent fe7aa08633
commit 261f17a117
1 file changed
+2 -2
+2 -2
View File
@@ -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 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 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 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 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. ("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() server()
await mount() await mount()
await userEvent.click(screen.getByRole('button', { name: 'Backup Settings' })) await userEvent.click(screen.getByRole('button', { name: 'Backup Settings' }))