@camunda/e2e-test-suite 0.0.874 → 0.0.876

package/dist/pages/SM-8.9/NavigationPage.d.ts

@@ -10,6 +10,8 @@ declare class NavigationPage {
     readonly keyboardPageBanner: Locator;
     readonly managementIdentityPageBanner: Locator;
     constructor(page: Page);
+    private isRetriableNavigationNetworkError;
+    private gotoWithNetworkRetry;
     goTo(url: string, banner: Locator, sleepTimeout?: number, { username, password, }?: {
         username?: string;
         password?: string;

package/dist/pages/SM-8.9/NavigationPage.js

@@ -15,6 +15,22 @@ const CONSOLE_CONTEXT_PATH = process.env.CONSOLE_CONTEXT_PATH ?? '/console';
 const MANAGEMENT_IDENTITY_CONTEXT_PATH = process.env.MANAGEMENT_IDENTITY_CONTEXT_PATH ?? '/identity';
 const IDENTITY_FIRSTUSER_USERNAME = process.env.DISTRO_QA_E2E_TESTS_IDENTITY_FIRSTUSER_USERNAME || 'demo';
 const IDENTITY_FIRSTUSER_PASSWORD = process.env.DISTRO_QA_E2E_TESTS_IDENTITY_FIRSTUSER_PASSWORD || 'demo';
+// Navigation errors raised by Chromium's network stack rather than by the app:
+// the cluster host stopped resolving or stopped accepting connections. These
+// are not login problems, so retrying the login flow does nothing for them —
+// they need wall-clock waiting instead (see `gotoWithNetworkRetry`).
+const RETRIABLE_NAVIGATION_NETWORK_ERRORS = [
+    'ERR_NAME_NOT_RESOLVED',
+    'ERR_CONNECTION_REFUSED',
+    'ERR_CONNECTION_RESET',
+    'ERR_CONNECTION_CLOSED',
+    'ERR_CONNECTION_TIMED_OUT',
+    'ERR_ADDRESS_UNREACHABLE',
+    'ERR_EMPTY_RESPONSE',
+    'ERR_SOCKET_NOT_CONNECTED',
+];
+const NETWORK_OUTAGE_BUDGET = constants_1._1_MINUTE_IN_MS * 5;
+const NETWORK_OUTAGE_POLL_INTERVAL = constants_1._1_SECOND_IN_MS * 10;
 class NavigationPage {
     page;
     modelerPageBanner;
@@ -53,8 +69,40 @@ class NavigationPage {
             .first();
         this.keyboardPageBanner = page.locator('#keycloak-bg');
     }
+    isRetriableNavigationNetworkError(error) {
+        const message = error instanceof Error ? error.message : String(error);
+        return RETRIABLE_NAVIGATION_NETWORK_ERRORS.some((code) => message.includes(code));
+    }
+    // Navigate, absorbing DNS/connection-level failures until
+    // `networkOutageDeadline` passes. The nightly cluster's ingress hostname can
+    // stop resolving mid-run (run 30329717154: every navigation to /modeler died
+    // instantly — 5 attempts in ~200ms — while the same suite had passed against
+    // the same host 35 minutes earlier). The login retry loop below fails fast on
+    // each of its attempts, so it burns its whole budget inside such a window.
+    // Waiting on a shared deadline lets the host come back while a sustained
+    // outage still exhausts the budget and surfaces as a failed login.
+    async gotoWithNetworkRetry(url, networkOutageDeadline) {
+        for (;;) {
+            try {
+                await this.page.goto(url, {
+                    timeout: 60000,
+                    waitUntil: 'domcontentloaded',
+                });
+                return;
+            }
+            catch (error) {
+                if (!this.isRetriableNavigationNetworkError(error) ||
+                    Date.now() >= networkOutageDeadline) {
+                    throw error;
+                }
+                console.warn(`[${new Date().toISOString()}] [NavigationPage] ${url} unreachable at the network level (${error instanceof Error ? error.message : error}); waiting for the cluster host to come back`);
+                await (0, sleep_1.sleep)(NETWORK_OUTAGE_POLL_INTERVAL);
+            }
+        }
+    }
     async goTo(url, banner, sleepTimeout, { username = IDENTITY_FIRSTUSER_USERNAME, password = IDENTITY_FIRSTUSER_PASSWORD, } = {}, maxRetries = 5) {
         const startTime = Date.now();
+        const networkOutageDeadline = startTime + NETWORK_OUTAGE_BUDGET;
         let timeout = constants_1._1_SECOND_IN_MS * 10;
         if (url === '/modeler') {
             timeout = constants_1._1_SECOND_IN_MS * 20;
@@ -64,10 +112,7 @@ class NavigationPage {
                 if (sleepTimeout) {
                     await (0, sleep_1.sleep)(sleepTimeout);
                 }
-                await this.page.goto(url, {
-                    timeout: 60000,
-                    waitUntil: 'domcontentloaded',
-                });
+                await this.gotoWithNetworkRetry(url, networkOutageDeadline);
                 const loginPage = new LoginPage_1.LoginPage(this.page);
                 const loginEntryPoint = banner
                     .or(loginPage.usernameInput)
@@ -109,8 +154,13 @@ class NavigationPage {
                     }
                 }
                 else {
-                    console.error(`[${now.toISOString()}] (+${elapsed}ms) [NavigationPage] Login (${url}) failed after ${maxRetries} attempts`);
-                    throw new Error(`Login (${url}) failed after ${maxRetries} attempts`);
+                    // Carry the last underlying failure into the message: without it the
+                    // report only shows "failed after N attempts", and the screenshot of
+                    // a failed navigation is a blank page, so the real cause (a Keycloak
+                    // 5xx vs. net::ERR_NAME_NOT_RESOLVED) is invisible in triage.
+                    const cause = error instanceof Error ? error.message : String(error);
+                    console.error(`[${now.toISOString()}] (+${elapsed}ms) [NavigationPage] Login (${url}) failed after ${maxRetries} attempts: ${cause}`);
+                    throw new Error(`Login (${url}) failed after ${maxRetries} attempts: ${cause}`);
                 }
             }
         }

package/package.json

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