vitest-qase-reporter 1.0.4 → 1.1.0

package/README.md

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

package/changelog.md

@@ -1,3 +1,9 @@
+# qase-vitest@1.1.0
+
+## What's new
+
+- Added support for multi-project support.
+
 # qase-vitest@1.0.4
 
 ## What's new

package/dist/index.d.ts

@@ -7,22 +7,8 @@ export declare class VitestQaseReporter implements Reporter {
     private reporter;
     private currentSuite;
     private testMetadata;
-    /**
-   * @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;
-    /**
-   * @param {string} title
-   * @returns {string}
-   * @private
-   */
-    private static removeQaseIdsFromTitle;
     constructor(options?: VitestQaseOptionsType);
     /**
      * Create TestResultType from Vitest TestCase

package/dist/index.js

@@ -6,31 +6,8 @@ class VitestQaseReporter {
     reporter;
     currentSuite = undefined;
     testMetadata = new Map();
-    /**
-   * @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(VitestQaseReporter.qaseIdRegExp) ?? [];
-        return ids ? ids.split(',').map((id) => Number(id)) : [];
-    }
-    /**
-   * @param {string} title
-   * @returns {string}
-   * @private
-   */
-    static removeQaseIdsFromTitle(title) {
-        const matches = title.match(VitestQaseReporter.qaseIdRegExp);
-        if (matches) {
-            return title.replace(matches[0], '').trimEnd();
-        }
-        return title;
-    }
     constructor(options = {}) {
         const composedOptions = (0, qase_javascript_commons_1.composeOptions)(options, {});
         this.reporter = qase_javascript_commons_1.QaseReporter.getInstance({
@@ -45,18 +22,23 @@ class VitestQaseReporter {
      */
     createTestResult(testCase) {
         const result = testCase.result();
-        const qaseIds = VitestQaseReporter.getCaseId(testCase.name);
+        const parsed = (0, qase_javascript_commons_1.parseProjectMappingFromTitle)(testCase.name);
         const diagnostic = testCase.diagnostic();
         const testId = testCase.id ?? testCase.name;
         const metadata = this.testMetadata.get(testId);
-        // Use title from metadata if available, otherwise use test name
-        const testTitle = metadata?.title ?? VitestQaseReporter.removeQaseIdsFromTitle(testCase.name);
+        // Use title from metadata if available, otherwise use cleaned name (multi-project markers stripped)
+        const testTitle = metadata?.title ?? (parsed.cleanedTitle.replace(/\s+/g, ' ').trim() || testCase.name);
         const testResult = new qase_javascript_commons_1.TestResultType(testTitle);
         testResult.id = testCase.id ?? '';
         testResult.signature = testCase.fullName ?? testCase.name;
-        // Set testops_id based on extracted qase IDs
-        if (qaseIds.length > 0) {
-            testResult.testops_id = qaseIds.length === 1 ? qaseIds[0] ?? null : qaseIds;
+        // Multi-project: set testops_project_mapping when any (Qase PROJECT: ids) is present
+        const hasProjectMapping = Object.keys(parsed.projectMapping).length > 0;
+        if (hasProjectMapping) {
+            testResult.testops_project_mapping = parsed.projectMapping;
+            testResult.testops_id = null;
+        }
+        else if (parsed.legacyIds.length > 0) {
+            testResult.testops_id = parsed.legacyIds.length === 1 ? parsed.legacyIds[0] : parsed.legacyIds;
         }
         else {
             testResult.testops_id = null;

package/dist/vitest.d.ts

@@ -1,5 +1,14 @@
 type StepFunction = () => Promise<void> | void;
+/** Project code → test case IDs for multi-project (testops_multi) mode. */
+export type ProjectMapping = Record<string, number[]>;
 export declare const addQaseId: (name: string, caseIds: number[]) => string;
+/**
+ * Build test name with multi-project markers (for testops_multi mode).
+ * @param name — test title
+ * @param mapping — e.g. { PROJ1: [1, 2], PROJ2: [3] }
+ * @example it(addQaseProjects('Login flow', { PROJ1: [100], PROJ2: [200] }), async () => { ... });
+ */
+export declare const addQaseProjects: (name: string, mapping: ProjectMapping) => string;
 type AnnotateFunction = (message: string, options?: unknown) => Promise<void>;
 export interface QaseWrapper {
     annotate(message: string, options?: unknown): Promise<void>;

package/dist/vitest.js

@@ -3,14 +3,24 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
     return (mod && mod.__esModule) ? mod : { "default": mod };
 };
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.withQase = exports.addQaseId = void 0;
+exports.withQase = exports.addQaseProjects = exports.addQaseId = void 0;
 const qase_javascript_commons_1 = require("qase-javascript-commons");
 const path_1 = __importDefault(require("path"));
-// Function to add Qase ID to test name
+// Function to add Qase ID to test name (single project)
 const addQaseId = (name, caseIds) => {
     return `${name} (Qase ID: ${caseIds.join(',')})`;
 };
 exports.addQaseId = addQaseId;
+/**
+ * Build test name with multi-project markers (for testops_multi mode).
+ * @param name — test title
+ * @param mapping — e.g. { PROJ1: [1, 2], PROJ2: [3] }
+ * @example it(addQaseProjects('Login flow', { PROJ1: [100], PROJ2: [200] }), async () => { ... });
+ */
+const addQaseProjects = (name, mapping) => {
+    return (0, qase_javascript_commons_1.formatTitleWithProjectMapping)(name, mapping);
+};
+exports.addQaseProjects = addQaseProjects;
 /**
  * Create qase wrapper for annotate function
  * @param annotate - Vitest annotate function

package/docs/MULTI_PROJECT.md

@@ -0,0 +1,53 @@
+# Multi-Project Support in Vitest
+
+Qase Vitest 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 Vitest config (e.g. in `vitest.config.ts` or `qase.config.json`) and add the `testops_multi` section with `default_project` and `projects`.
+
+## Using `addQaseProjects(name, mapping)`
+
+Use the `addQaseProjects(name, mapping)` helper from `vitest-qase-reporter/vitest` to build a test name that includes multi-project markers. The reporter parses the title and sets `testops_project_mapping`:
+
+```typescript
+import { addQaseId, addQaseProjects } from 'vitest-qase-reporter/vitest';
+
+// Single project (legacy)
+it(addQaseId('login flow', [100]), async () => { ... });
+
+// Multi-project
+it(addQaseProjects('login flow', { PROJ1: [100], PROJ2: [200] }), async () => { ... });
+
+// Multiple IDs per project
+it(addQaseProjects('checkout', { PROJ1: [10, 11], PROJ2: [20] }), async () => { ... });
+```
+
+Project codes must match `testops_multi.projects[].code` in your config.
+
+## Tests Without Project Mapping
+
+Tests whose name does not contain multi-project markers (and have no single-project `(Qase ID: …)`) are sent to the `default_project`. Results without any case ID are sent to the default project without linking to a test case.
+
+## Important Notes
+
+1. **Project codes must match**: Keys in `addQaseProjects('name', { PROJ1: [1], ... })` must match `testops_multi.projects[].code`.
+2. **Mode**: Use `mode: 'testops_multi'` in Vitest reporter config.
+3. **Title format**: The helper produces a title like `Name (Qase PROJ1: 1,2) (Qase PROJ2: 3)`.
+
+## Examples
+
+See the [multi-project Vitest example](../../examples/multiProject/vitest/) for a complete runnable setup.
+
+## Troubleshooting
+
+* Ensure `mode` is `testops_multi` and project codes match the config.
+* Use `addQaseProjects(name, mapping)` (or an equivalent title format) so the reporter can parse the mapping from the test name.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vitest-qase-reporter",
-  "version": "1.0.4",
+  "version": "1.1.0",
   "description": "Qase TMS Vitest Reporter",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
@@ -40,7 +40,7 @@
   "author": "Qase Team <support@qase.io>",
   "license": "Apache-2.0",
   "dependencies": {
-    "qase-javascript-commons": "~2.4.13"
+    "qase-javascript-commons": "~2.5.0"
   },
   "peerDependencies": {
     "vitest": ">=3.0.0"