mocha-qase-reporter 1.1.8 → 1.2.0

package/README.md

@@ -67,6 +67,12 @@ A test run will be performed and available at:
 https://app.qase.io/run/QASE_PROJECT_CODE
 ```
 
+### Multi-Project Support
+
+Qase Mocha Reporter supports sending test results to multiple Qase projects simultaneously. You can specify different test case IDs for each project using `qase.projects(mapping, name)`.
+
+For detailed information, configuration, and examples, see the [Multi-Project Support Guide](docs/MULTI_PROJECT.md).
+
 ### Parallel execution
 
 The reporter supports parallel execution of tests.

package/changelog.md

@@ -1,3 +1,9 @@
+# qase-mocha@1.2.0
+
+## What's new
+
+- Added support for multi-project support.
+
 # qase-mocha@1.1.8
 
 ## What's new

package/dist/mocha.d.ts

@@ -1,3 +1,5 @@
+/** Project code → test case IDs for multi-project (testops_multi) mode. */
+export type ProjectMapping = Record<string, number[]>;
 /**
  * Set IDs for the test case
  *
@@ -9,4 +11,7 @@
  * });
  * @returns {string}
  */
-export declare const qase: (caseId: number | string | number[] | string[], name: string) => string;
+export declare const qase: {
+    (caseId: number | string | number[] | string[], name: string): string;
+    projects(mapping: ProjectMapping, name: string): string;
+};

package/dist/mocha.js

@@ -1,6 +1,7 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.qase = void 0;
+const qase_javascript_commons_1 = require("qase-javascript-commons");
 /**
  * Set IDs for the test case
  *
@@ -30,3 +31,12 @@ const qase = (caseId, name) => {
     return `${name} (Qase ID: ${caseIds.join(',')})`;
 };
 exports.qase = qase;
+/**
+ * Build test name with multi-project markers (for testops_multi mode).
+ * @param mapping — e.g. { PROJ1: [1, 2], PROJ2: [3] }
+ * @param name — test title
+ * @example it(qase.projects({ PROJ1: [100], PROJ2: [200] }, 'Login flow'), function() { ... });
+ */
+exports.qase.projects = (mapping, name) => {
+    return (0, qase_javascript_commons_1.formatTitleWithProjectMapping)(name, mapping);
+};

package/dist/reporter.d.ts

@@ -76,13 +76,8 @@ export declare class MochaQaseReporter extends reporters.Base {
     /**
      * @type {RegExp}
      */
+    /** @deprecated Use parseProjectMappingFromTitle from qase-javascript-commons for multi-project support. */
     static qaseIdRegExp: RegExp;
-    /**
-     * @param {string} title
-     * @returns {number[]}
-     * @private
-     */
-    private static getCaseId;
     /**
      * Extract expected result and data from step title and return cleaned string
      * @param {string} input

package/dist/reporter.js

@@ -159,10 +159,12 @@ class MochaQaseReporter extends mocha_1.reporters.Base {
             this.currentTest = new currentTest();
             return;
         }
+        const fromTitle = (0, qase_javascript_commons_1.parseProjectMappingFromTitle)(test.title);
         const ids = this.getQaseId();
         if (ids.length === 0) {
-            ids.push(...MochaQaseReporter.getCaseId(test.title));
+            ids.push(...fromTitle.legacyIds);
         }
+        const hasProjectMapping = Object.keys(fromTitle.projectMapping).length > 0;
         const suites = this.getSuites(test);
         let relations = {};
         if (suites.length > 0) {
@@ -193,7 +195,7 @@ class MochaQaseReporter extends mocha_1.reporters.Base {
             group_params: this.metadata.groupParameters ?? {},
             relations: relations,
             run_id: null,
-            signature: this.getSignature(test, ids, this.metadata.parameters ?? {}),
+            signature: this.getSignature(test, hasProjectMapping ? [] : ids, this.metadata.parameters ?? {}),
             steps: this.currentTest.steps,
             id: (0, uuid_1.v4)(),
             execution: {
@@ -204,8 +206,9 @@ class MochaQaseReporter extends mocha_1.reporters.Base {
                 stacktrace: test.err?.stack ?? null,
                 thread: null,
             },
-            testops_id: ids.length > 0 ? ids : null,
-            title: this.metadata.title && this.metadata.title != '' ? this.metadata.title : this.removeQaseIdsFromTitle(test.title),
+            testops_id: hasProjectMapping ? null : (ids.length > 0 ? ids : null),
+            testops_project_mapping: hasProjectMapping ? fromTitle.projectMapping : null,
+            title: this.metadata.title && this.metadata.title != '' ? this.metadata.title : (fromTitle.cleanedTitle || this.removeQaseIdsFromTitle(test.title)),
         };
         void this.reporter.addTestResult(result);
         this.metadata.clear();
@@ -360,16 +363,8 @@ class MochaQaseReporter extends mocha_1.reporters.Base {
     /**
      * @type {RegExp}
      */
+    /** @deprecated Use parseProjectMappingFromTitle from qase-javascript-commons for multi-project support. */
     static qaseIdRegExp = /\(Qase ID: ([\d,]+)\)/;
-    /**
-     * @param {string} title
-     * @returns {number[]}
-     * @private
-     */
-    static getCaseId(title) {
-        const [, ids] = title.match(MochaQaseReporter.qaseIdRegExp) ?? [];
-        return ids ? ids.split(',').map((id) => Number(id)) : [];
-    }
     /**
      * Extract expected result and data from step title and return cleaned string
      * @param {string} input

package/docs/MULTI_PROJECT.md

@@ -0,0 +1,53 @@
+# Multi-Project Support in Mocha
+
+Qase Mocha Reporter supports sending test results to multiple Qase projects simultaneously. This feature allows you to report the same test execution to different projects with different test case IDs, which is useful when:
+
+* You need to report the same test to different projects
+* Different projects track the same functionality with different test case IDs
+* You want to maintain separate test runs for different environments or teams
+
+## Configuration
+
+For detailed configuration options, refer to the [qase-javascript-commons README](../../qase-javascript-commons/README.md#multi-project-support).
+
+### Basic Multi-Project Configuration
+
+Set `mode` to `testops_multi` in your Mocha reporter options (e.g. in `.mocharc.js` or `qase.config.json`) and add the `testops_multi` section with `default_project` and `projects`.
+
+## Using `qase.projects(mapping, name)`
+
+Use `qase.projects(mapping, name)` to set the test title with multi-project markers. Use the returned string as the first argument to `it()`:
+
+```javascript
+const { qase } = require('mocha-qase-reporter');
+
+// Single project
+it(qase(100, 'login flow'), function () { ... });
+
+// Multi-project
+it(qase.projects({ PROJ1: [100], PROJ2: [200] }, 'login flow'), function () { ... });
+
+// Multiple IDs per project
+it(qase.projects({ PROJ1: [10, 11], PROJ2: [20] }, 'checkout'), function () { ... });
+```
+
+Project codes (e.g. `PROJ1`, `PROJ2`) must match `testops_multi.projects[].code` in your config.
+
+## Tests Without Project Mapping
+
+Tests that do not use `qase.projects()` and have no `(Qase PROJ: ids)` in the title are sent to the `default_project`. If they use `qase(id, name)` (single-project), that ID is used for the default project.
+
+## Important Notes
+
+1. **Project codes must match**: Codes in `qase.projects({ PROJ1: [1], ... })` must match `testops_multi.projects[].code`.
+2. **Mode**: Set `mode` to `testops_multi` in reporter config.
+3. **Title format**: The helper produces a title like `Name (Qase PROJ1: 1,2) (Qase PROJ2: 3)` so the reporter can parse the mapping.
+
+## Examples
+
+See the [multi-project Mocha example](../../examples/multiProject/mocha/) for a complete runnable setup.
+
+## Troubleshooting
+
+* Verify `mode` is `testops_multi` and project codes in `qase.projects()` match the config.
+* Ensure the first argument to `it()` is the string returned by `qase.projects(mapping, name)` (or an equivalent title with markers).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mocha-qase-reporter",
-  "version": "1.1.8",
+  "version": "1.2.0",
   "description": "Mocha Cypress Reporter",
   "homepage": "https://github.com/qase-tms/qase-javascript",
   "sideEffects": false,
@@ -43,7 +43,7 @@
   "dependencies": {
     "mocha": "^11.7.5",
     "deasync-promise": "^1.0.1",
-    "qase-javascript-commons": "~2.4.13",
+    "qase-javascript-commons": "~2.5.0",
     "uuid": "^9.0.1"
   },
   "devDependencies": {