qase-javascript-commons 2.5.10 → 2.6.1

package/changelog.md

@@ -1,3 +1,17 @@
+# 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
+
+- Added `tags: string[]` field to `TestResultType` domain model for tag support.
+- Tags are mapped to `fields.tags` as a comma-separated string when sending results to API v2.
+- Tags are included in report serialization output.
+
 # qase-javascript-commons@2.5.10
 
 ## What's new

package/dist/client/clientV2.js

@@ -140,6 +140,12 @@ class ClientV2 extends clientV1_1.ClientV1 {
             defect: this.config.defect ?? false,
             signature: result.signature,
         };
+        if (result.tags.length > 0) {
+            model.fields = {
+                ...model.fields,
+                tags: [...new Set(result.tags)].join(','),
+            };
+        }
         this.logger.logDebug(`Transformed result: ${JSON.stringify(model)}`);
         return model;
     }

package/dist/models/test-result.d.ts

@@ -28,6 +28,7 @@ export declare class TestResultType {
     relations: Relation | null;
     muted: boolean;
     message: string | null;
+    tags: string[];
     preparedAttachments?: string[];
     constructor(title: string);
     /**

package/dist/models/test-result.js

@@ -24,6 +24,7 @@ class TestResultType {
     relations;
     muted;
     message;
+    tags;
     preparedAttachments;
     constructor(title) {
         this.id = '';
@@ -42,6 +43,7 @@ class TestResultType {
         this.relations = null;
         this.muted = false;
         this.message = null;
+        this.tags = [];
         this.preparedAttachments = [];
     }
     /**

package/dist/reporters/report-reporter.js

@@ -192,6 +192,7 @@ class ReportReporter extends abstract_reporter_1.AbstractReporter {
             relations: result.relations,
             muted: result.muted,
             message: result.message,
+            tags: result.tags,
         };
         // Internal-only fields are excluded: testops_id, group_params, run_id, author, testops_project_mapping, preparedAttachments
         return serialized;

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

@@ -90,6 +90,21 @@ function isAssertionError(error, originalStatus) {
         }
         return false;
     }
+    // Cypress-specific failure detection.
+    // Cypress uses retry-ability and command-based error syntax that don't contain
+    // the word "expect" (unlike Jest/Playwright assertions). Without this branch,
+    // genuine UI/command failures fall through to the "timeout → invalid" catch-all
+    // below and get misclassified as environment errors.
+    //
+    // Why this order: the hasNonAssertionPattern check above already returned
+    // invalid for cy.request() failures (which contain "network"/"connection"),
+    // so reaching this point with a Cypress signature means the error has no
+    // infrastructure markers — the test app failed to behave as expected.
+    const isCypressRetryTimeout = /timed out retrying after \d+ms/.test(errorMessage);
+    const isCypressCommandFailure = /cy\.\w+\(\)\s+(failed|timed out)/.test(errorMessage);
+    if (isCypressRetryTimeout || isCypressCommandFailure) {
+        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.5.10",
+  "version": "2.6.1",
   "description": "Qase JS Reporters",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",