boundary-ui
boundary-ui copied to clipboard
test(e2e): Add extra timeout for "delete resources" test
trafficstars
The Delete Resources e2e test can sometimes exceed the currently defined test timeout of 90s. This PR modifies the Delete Resources test to use its own timeout of 180s. See below for an example run
❯ yarn run e2e:ent:aws --project=chromium tests/delete-resources-ent.spec.mjs
yarn run v1.22.19
$ yarn run e2e --grep "(?=.*@ent)(?=.*@aws)" --project=chromium tests/delete-resources-ent.spec.mjs
$ yarn playwright test --config ./tests/e2e/playwright.config.mjs --grep '(?=.*@ent)(?=.*@aws)' --project=chromium tests/delete-resources-ent.spec.mjs
$ /Users/mycow/Developer/boundary-ui/node_modules/.bin/playwright test --config ./tests/e2e/playwright.config.mjs --grep '(?=.*@ent)(?=.*@aws)' --project=chromium tests/delete-resources-ent.spec.mjs
Running 1 test using 1 worker
✓ 1 [chromium] › tests/delete-resources-ent.spec.mjs:69:1 › Verify resources can be deleted (enterprise) @ent @aws (1.9m)
Slow test file: [chromium] › tests/delete-resources-ent.spec.mjs (1.9m)
Consider splitting slow test files to speed up parallel execution
1 passed (2.0m)
✨ Done in 119.63s.