@camunda/e2e-test-suite 0.0.756 → 0.0.758

package/dist/pages/SM-8.10/UtilitiesPage.js

@@ -128,7 +128,28 @@ async function completeTaskWithRetry(page, taskPanelPage, taskDetailsPage, taskN
                 catch {
                     // No toast to dismiss
                 }
-                await page.reload();
+                // A transient backend 500 while opening the task can leave the page on
+                // the raw Tasklist API URL (the JSON error renders as the top-level
+                // document). A bare reload then re-requests that broken URL and never
+                // restores the SPA, so every remaining attempt is wasted. Re-navigate
+                // to the Tasklist list — which uses a different endpoint than the
+                // single-task fetch that 500s — so the app re-mounts and the task can
+                // be re-opened once the blip clears. Progressive backoff gives the
+                // backend time to recover between attempts.
+                await (0, sleep_1.sleep)(2000 * (attempt + 1));
+                const orchestrationContextPath = process.env.ORCHESTRATION_CONTEXT_PATH ?? '/orchestration';
+                const normalizedOrchestrationPath = orchestrationContextPath.startsWith('/')
+                    ? orchestrationContextPath
+                    : `/${orchestrationContextPath}`;
+                try {
+                    await page.goto(`${normalizedOrchestrationPath}/tasklist`, {
+                        timeout: 60000,
+                        waitUntil: 'domcontentloaded',
+                    });
+                }
+                catch {
+                    await page.reload();
+                }
                 await page.waitForLoadState('networkidle');
             }
             else {

package/dist/resources/test-api-v2-complete.sh

@@ -393,9 +393,32 @@ _curl_common() {
   # with a short backoff. Without this, brief network blips during long test
   # runs surface as empty responses (`<none>` status) and false-positive
   # FAILEDs in print_result. --max-time still bounds total time per attempt.
-  curl --http1.1 --max-time 30 --connect-timeout 10 \
-    --retry 3 --retry-delay 1 --retry-connrefused --retry-all-errors \
-    -i -s -H 'Expect:' "$@"
+  #
+  # Outer gateway-retry loop: an nginx `502 Bad Gateway` / `504 Gateway
+  # Timeout` (or an empty/no-status response) is emitted by the ingress when
+  # it cannot reach the upstream orchestration REST API — e.g. while an
+  # orchestration pod is rolling during an upgrade-minor run. That is never a
+  # valid response to any assertion in this suite (the API returns JSON status
+  # bodies, never a bare nginx HTML page), so re-issue the whole request with
+  # capped backoff to ride out a brief upstream restart window. curl's own
+  # --retry budget (~4s) is too small for a pod restart; this widens it to
+  # ~90s. A sustained outage still returns the real 502/504 once the budget is
+  # exhausted, so it surfaces as a genuine FAILED (not masked).
+  local gw_attempt=0 gw_max=12 gw_response gw_status
+  while :; do
+    gw_response="$(curl --http1.1 --max-time 30 --connect-timeout 10 \
+      --retry 3 --retry-delay 1 --retry-connrefused --retry-all-errors \
+      -i -s -H 'Expect:' "$@")"
+    gw_status="$(echo "$gw_response" | grep -m1 -E '^HTTP/[0-9.]+' | awk '{print $2}' || true)"
+    if { [[ "$gw_status" != "502" && "$gw_status" != "504" && -n "$gw_status" ]]; } \
+        || (( gw_attempt >= gw_max )); then
+      printf '%s\n' "$gw_response"
+      return 0
+    fi
+    gw_attempt=$((gw_attempt + 1))
+    # Backoff 2,4,6,8,10,10,... capped at 10s -> ~90s total across 12 attempts.
+    sleep $(( gw_attempt < 5 ? gw_attempt * 2 : 10 ))
+  done
 }
 
 # Helper to get curl -F argument for tenantId in multipart forms

package/dist/tests/SM-8.10/migration-path-user-flows.spec.js

@@ -111,30 +111,30 @@ if (process.env.IS_MIGRATION === 'true') {
         (0, SM_8_10_1.test)('Assert Users Persist in Management Identity With Correct Roles @tasklistV2', async ({ managementIdentityPage, identityUsersPage, }) => {
             await managementIdentityPage.clickUsersLink();
             await identityUsersPage.assertUserIsAssignedCorrectRole('demo', [
-                'Console',
                 'Default user role',
                 'ManagementIdentity',
                 'Optimize',
                 'Orchestration',
                 'Web Modeler',
+                'Web Modeler Admin',
             ]);
             await managementIdentityPage.clickUsersLink();
             await identityUsersPage.assertUserIsAssignedCorrectRole('bart', [
-                'Console',
                 'Default user role',
                 'ManagementIdentity',
                 'Optimize',
                 'Orchestration',
                 'Web Modeler',
+                'Web Modeler Admin',
             ]);
             await managementIdentityPage.clickUsersLink();
             await identityUsersPage.assertUserIsAssignedCorrectRole('lisa', [
-                'Console',
                 'Default user role',
                 'ManagementIdentity',
                 'Optimize',
                 'Orchestration',
                 'Web Modeler',
+                'Web Modeler Admin',
             ]);
         });
         (0, SM_8_10_1.test)('Assert Demo User Can Deploy Processes', async ({ page, modelerHomePage, navigationPage, modelerCreatePage, operateHomePage, operateProcessesPage, operateProcessInstancePage, taskDetailsPage, taskPanelPage, }) => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camunda/e2e-test-suite",
-  "version": "0.0.756",
+  "version": "0.0.758",
   "description": "End-to-end test helpers for Camunda 8",
   "repository": {
     "type": "git",

package/resources/test-api-v2-complete.sh

@@ -393,9 +393,32 @@ _curl_common() {
   # with a short backoff. Without this, brief network blips during long test
   # runs surface as empty responses (`<none>` status) and false-positive
   # FAILEDs in print_result. --max-time still bounds total time per attempt.
-  curl --http1.1 --max-time 30 --connect-timeout 10 \
-    --retry 3 --retry-delay 1 --retry-connrefused --retry-all-errors \
-    -i -s -H 'Expect:' "$@"
+  #
+  # Outer gateway-retry loop: an nginx `502 Bad Gateway` / `504 Gateway
+  # Timeout` (or an empty/no-status response) is emitted by the ingress when
+  # it cannot reach the upstream orchestration REST API — e.g. while an
+  # orchestration pod is rolling during an upgrade-minor run. That is never a
+  # valid response to any assertion in this suite (the API returns JSON status
+  # bodies, never a bare nginx HTML page), so re-issue the whole request with
+  # capped backoff to ride out a brief upstream restart window. curl's own
+  # --retry budget (~4s) is too small for a pod restart; this widens it to
+  # ~90s. A sustained outage still returns the real 502/504 once the budget is
+  # exhausted, so it surfaces as a genuine FAILED (not masked).
+  local gw_attempt=0 gw_max=12 gw_response gw_status
+  while :; do
+    gw_response="$(curl --http1.1 --max-time 30 --connect-timeout 10 \
+      --retry 3 --retry-delay 1 --retry-connrefused --retry-all-errors \
+      -i -s -H 'Expect:' "$@")"
+    gw_status="$(echo "$gw_response" | grep -m1 -E '^HTTP/[0-9.]+' | awk '{print $2}' || true)"
+    if { [[ "$gw_status" != "502" && "$gw_status" != "504" && -n "$gw_status" ]]; } \
+        || (( gw_attempt >= gw_max )); then
+      printf '%s\n' "$gw_response"
+      return 0
+    fi
+    gw_attempt=$((gw_attempt + 1))
+    # Backoff 2,4,6,8,10,10,... capped at 10s -> ~90s total across 12 attempts.
+    sleep $(( gw_attempt < 5 ? gw_attempt * 2 : 10 ))
+  done
 }
 
 # Helper to get curl -F argument for tenantId in multipart forms