Files
dc/client/cypress
dc e8cdc37a05
Build / Build-and-ng-test (pull_request) Successful in 5m10s
Lighthouse Checks / lighthouse (pull_request) Successful in 8m34s
Build / Build-and-test-development (pull_request) Successful in 32m58s
test(deploy): match the picker's requests with regexps, and sign in on a secured estate
The spec failed on CI: the browse button never appeared. Two causes, both
found by reproducing the CI estate locally (seeded drive):

- The intercept pattern '**/drive/folder**' does not match the request the
  app makes ('/SASjsApi/drive/folder?_folderPath=...') in this Cypress
  version, so the app saw the real drive, loaded the startup service and
  never routed to the deploy screen. Both intercepts are now regexps, which
  match deterministically. Verified on the seeded estate: the app routes to
  #/deploy and the agreement card renders.

- A secured estate shows a login form first. The boot helper now waits for
  one of the states it can act on (a visible login form, the agreement card,
  or the deploy screen), signs in when the form is visible, then waits for
  the deploy screen. The login form stays in the DOM hidden on other routes,
  so visibility - not presence - decides.
2026-11-05 15:10:51 +00:00
..
2026-08-28 21:29:15 +01:00
2023-07-13 13:44:05 +02:00
2023-07-13 13:44:05 +02:00