qase-javascript-commons 2.6.0 → 2.6.2

package/changelog.md

@@ -1,3 +1,15 @@
+# qase-javascript-commons@2.6.2
+
+## Bug fixes
+
+- Fixed Cypress failure classification in real browser environments. Cypress errors false-positive on the `"http"` non-assertion pattern because (a) browser stack traces contain URLs like `https://localhost/__cypress/runner/...` and (b) all error messages include docs links like `https://on.cypress.io/...`. The classifier now unconditionally trusts Cypress' retry-ability prefix (`Timed out retrying after Nms:`) as a genuine test failure signal, since this prefix is exclusive to DOM-interacting commands and never appears in infrastructure failures (`cy.request()`, `cy.task()`).
+
+# qase-javascript-commons@2.6.1
+
+## Bug fixes
+
+- Fixed Cypress test failures being classified as `invalid` instead of `failed`. Cypress uses retry-ability (`Timed out retrying after Nms: ...`) and command syntax (`cy.click() failed`, `cy.wait() timed out`) that don't contain the word `expect`, so genuine UI/command failures previously fell through to the timeout catch-all and were mislabeled as environment errors. `cy.request()` with infrastructure-level errors (e.g. `ECONNREFUSED`) continues to be classified as `invalid`.
+
 # qase-javascript-commons@2.6.0
 
 ## What's new

package/dist/utils/test-status-utils.js

@@ -79,6 +79,11 @@ function isAssertionError(error, originalStatus) {
     // Check for non-assertion patterns (excluding timeout for special handling above)
     const nonAssertionPatternsWithoutTimeout = nonAssertionPatterns.filter(pattern => pattern !== 'timeout');
     const hasNonAssertionPattern = nonAssertionPatternsWithoutTimeout.some(pattern => errorMessage.includes(pattern) || errorStack.includes(pattern));
+    // Cypress retry-ability prefix: "Timed out retrying after Nms:" is added by
+    // Cypress' retry mechanism exclusively for DOM-interacting commands (cy.get,
+    // cy.click, cy.should, cy.wait with aliases). It never appears in infra
+    // failures (cy.request, cy.task). This is the most reliable Cypress signal.
+    const isCypressRetryTimeout = /timed out retrying after \d+ms/.test(errorMessage);
     if (hasNonAssertionPattern) {
         const hasAssertionContext = assertionPatterns.some(pattern => errorMessage.includes(pattern) || errorStack.includes(pattern));
         const isRunnerFailed = normalizedOriginalStatus === 'failed' || normalizedOriginalStatus === 'timedout' || normalizedOriginalStatus === 'interrupted';
@@ -88,8 +93,21 @@ function isAssertionError(error, originalStatus) {
         if (isRunnerFailed && hasAssertionContext && !isSyntaxError) {
             return true;
         }
+        // Cypress override: the retry-ability prefix is a strong signal that the
+        // test was actively interacting with the application via a retryable command.
+        // Cypress errors false-positive on "http" because (a) browser stack traces
+        // contain URLs and (b) all error messages include docs links
+        // (https://on.cypress.io/...). The retry prefix itself is never
+        // infrastructure, so we trust it unconditionally.
+        if (isCypressRetryTimeout && isRunnerFailed) {
+            return true;
+        }
         return false;
     }
+    // Cypress failure without any non-assertion pattern (clean stack trace)
+    if (isCypressRetryTimeout) {
+        return true;
+    }
     // For timeout errors without expect, treat as invalid
     if (errorMessage.includes('timeout')) {
         return false;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "qase-javascript-commons",
-  "version": "2.6.0",
+  "version": "2.6.2",
   "description": "Qase JS Reporters",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
@@ -63,7 +63,7 @@
     "@types/mime-types": "^2.1.4",
     "@types/minimatch": "^6.0.0",
     "@types/uuid": "^9.0.8",
-    "axios": "^1.13.5",
+    "axios": "^1.15.0",
     "jest": "^29.7.0",
     "ts-jest": "^29.4.5"
   }