cucumberjs-qase-reporter 2.1.8 → 2.2.0

package/README.md

@@ -80,6 +80,12 @@ https://app.qase.io/run/QASE_PROJECT_CODE
   <img src="./screenshots/demo.gif">
 </p>
 
+### Multi-Project Support
+
+Qase CucumberJS Reporter supports sending test results to multiple Qase projects simultaneously. Use tags in feature files: `@qaseid.PROJ1(1) @qaseid.PROJ2(2)`.
+
+For detailed information, configuration, and examples, see the [Multi-Project Support Guide](docs/MULTI_PROJECT.md).
+
 ## Configuration
 
 Qase Cucumber JS reporter can be configured in multiple ways:

package/changelog.md

@@ -1,3 +1,15 @@
+# qase-cucumberjs@2.2.0
+
+## What's new
+
+- Added support for multi-project support.
+
+# qase-cucumberjs@2.1.9
+
+## What's new
+
+- Added support for QaseSuite tag.
+
 # qase-cucumberjs@2.1.8
 
 ## What's new

package/dist/models.d.ts

@@ -1,10 +1,14 @@
+import type { TestopsProjectMapping } from 'qase-javascript-commons';
 export interface TestMetadata {
     ids: number[];
+    /** Multi-project mapping (from @qaseid.PROJ(ids) tags). */
+    projectMapping: TestopsProjectMapping;
     fields: Record<string, string>;
     title: string | null;
     isIgnore: boolean;
     parameters: Record<string, string>;
     group_params: Record<string, string>;
+    suite: string | null;
 }
 export interface ScenarioData {
     name: string;

package/dist/storage.js

@@ -10,6 +10,7 @@ const qaseTitleRegExp = /^@[Qq]ase[Tt]itle=(.+)$/;
 const qaseFieldsRegExp = /^@[Qq]ase[Ff]ields=(.+)$/;
 const qaseParametersRegExp = /^@[Qq]ase[Pp]arameters=(.+)$/;
 const qaseGroupParametersRegExp = /^@[Qq]ase[Gg]roup[Pp]arameters=(.+)$/;
+const qaseSuiteRegExp = /^@[Qq]ase[Ss]uite=(.+)$/;
 const qaseIgnoreRegExp = /^@[Qq]ase[Ii][Gg][Nn][Oo][Rr][Ee]$/;
 class Storage {
     /**
@@ -198,7 +199,20 @@ class Storage {
         let relations = null;
         let params = {};
         const nodeId = pickle.astNodeIds[0];
-        if (nodeId != undefined && this.scenarios[nodeId] != undefined) {
+        // If suite is specified in metadata, use it (split by tab for sub-suites)
+        if (metadata.suite) {
+            const suiteParts = metadata.suite.split('\t').filter(part => part.trim().length > 0);
+            relations = {
+                suite: {
+                    data: suiteParts.map((suite) => ({
+                        title: suite.trim(),
+                        public_id: null,
+                    })),
+                },
+            };
+        }
+        else if (nodeId != undefined && this.scenarios[nodeId] != undefined) {
+            // Otherwise, use feature name as suite
             relations = {
                 suite: {
                     data: [
@@ -209,6 +223,9 @@ class Storage {
                     ],
                 },
             };
+        }
+        // Extract parameters from Gherkin examples
+        if (nodeId != undefined && this.scenarios[nodeId] != undefined) {
             for (const id of pickle.astNodeIds) {
                 if (this.scenarios[nodeId]?.parameters[id] != undefined) {
                     params = { ...params, ...this.scenarios[nodeId]?.parameters[id] };
@@ -219,7 +236,8 @@ class Storage {
         // Parameters from tags take precedence over Gherkin examples
         params = { ...params, ...metadata.parameters };
         const steps = this.convertSteps(pickle.steps, tc);
-        return {
+        const hasProjectMapping = Object.keys(metadata.projectMapping).length > 0;
+        const result = {
             attachments: this.attachments[testCase.testCaseStartedId] ?? [],
             author: null,
             execution: {
@@ -240,9 +258,11 @@ class Storage {
             signature: this.getSignature(pickle, metadata.ids, params),
             steps: steps,
             testops_id: metadata.ids.length > 0 ? metadata.ids : null,
+            testops_project_mapping: hasProjectMapping ? metadata.projectMapping : null,
             id: tcs.id,
             title: metadata.title ?? pickle.name,
         };
+        return result;
     }
     /**
      * Convert test steps to test result steps
@@ -309,13 +329,17 @@ class Storage {
         [cucumber_1.Status.UNKNOWN]: qase_javascript_commons_1.StepStatusEnum.skipped,
     };
     parseTags(tags) {
+        const tagNames = tags.map((t) => t.name);
+        const { legacyIds, projectMapping } = (0, qase_javascript_commons_1.parseProjectMappingFromTags)(tagNames);
         const metadata = {
-            ids: [],
+            ids: [...legacyIds],
+            projectMapping: { ...projectMapping },
             fields: {},
             title: null,
             isIgnore: false,
             parameters: {},
             group_params: {},
+            suite: null,
         };
         for (const tag of tags) {
             if (qaseIdRegExp.test(tag.name)) {
@@ -323,7 +347,8 @@ class Storage {
                 continue;
             }
             if (newQaseIdRegExp.test(tag.name)) {
-                metadata.ids.push(...(tag.name.replace(/^@[Qq]ase[Ii][Dd]=/, '')).split(',').map(Number));
+                const idsStr = tag.name.replace(/^@[Qq]ase[Ii][Dd]=/, '');
+                metadata.ids.push(...idsStr.split(',').map((s) => Number(s.trim())));
                 continue;
             }
             if (qaseTitleRegExp.test(tag.name)) {
@@ -363,6 +388,10 @@ class Storage {
                     // do nothing
                 }
             }
+            if (qaseSuiteRegExp.test(tag.name)) {
+                metadata.suite = tag.name.replace(/^@[Qq]ase[Ss]uite=/, '');
+                continue;
+            }
             if (qaseIgnoreRegExp.test(tag.name)) {
                 metadata.isIgnore = true;
             }

package/docs/MULTI_PROJECT.md

@@ -0,0 +1,75 @@
+# Multi-Project Support in CucumberJS
+
+Qase CucumberJS Reporter supports sending test results to multiple Qase projects simultaneously. This feature allows you to report the same scenario execution to different projects with different test case IDs, which is useful when:
+
+* You need to report the same scenario 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 `qase.config.json` and add the `testops_multi` section with `default_project` and `projects`.
+
+## Using Tags in Feature Files
+
+Map scenarios to projects and case IDs using tags in your `.feature` files.
+
+### Multi-project tags: `@qaseid.PROJECT_CODE(ids)`
+
+Use one or more tags per scenario. Each tag specifies a project code and one or more test case IDs:
+
+```gherkin
+Feature: Multi-project example
+
+  @qaseid.DEVX(1)
+  @qaseid.DEMO(2)
+  Scenario: Scenario reported to two projects
+    Given I have a step
+```
+
+### Single project (legacy)
+
+For a single project you can still use the legacy tag format:
+
+```gherkin
+  @QaseID=3
+  Scenario: Scenario with legacy single-project tag
+    Given I have a step
+```
+
+### Scenarios without Qase ID
+
+Scenarios with no `@qaseid` or `@QaseID` tags are sent to the `default_project` from your configuration. The result is sent without linking to a test case (no case ID).
+
+## Tag Format
+
+* **Multi-project**: `@qaseid.PROJECT_CODE(id1,id2,...)` — project code must match `testops_multi.projects[].code`.
+* **Legacy single-project**: `@QaseID=123` or `@qaseid(123)` — sent to `default_project` with that ID.
+
+## Important Notes
+
+1. **Project codes must match**: The project code in `@qaseid.PROJ1(1)` must match a `code` in `testops_multi.projects`.
+2. **Mode**: Set `mode` to `testops_multi` in `qase.config.json`.
+3. **Default project**: Scenarios without any Qase tags are sent to `default_project` without a case ID.
+4. **Multiple tags**: You can combine multiple `@qaseid.PROJ(ids)` tags to report one scenario to multiple projects.
+
+## Examples
+
+See the [multi-project CucumberJS example](../../examples/multiProject/cucumberjs/) for a complete runnable setup.
+
+## Troubleshooting
+
+### Results not appearing in projects
+
+* Verify `mode` is `testops_multi` in `qase.config.json`.
+* Check that project codes in tags (e.g. `@qaseid.DEVX(1)`) match `testops_multi.projects[].code` exactly (case-sensitive).
+* Ensure all projects are listed in `testops_multi.projects`.
+
+### Scenarios sent to wrong project
+
+* For scenarios without tags, check the `default_project` setting.
+* Ensure tag spelling and project codes match the configuration exactly.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cucumberjs-qase-reporter",
-  "version": "2.1.8",
+  "version": "2.2.0",
   "description": "Qase TMS CucumberJS Reporter",
   "homepage": "https://github.com/qase-tms/qase-javascript",
   "main": "./dist/index.js",
@@ -40,7 +40,7 @@
   "license": "Apache-2.0",
   "dependencies": {
     "@cucumber/messages": "^22.0.0",
-    "qase-javascript-commons": "~2.4.16"
+    "qase-javascript-commons": "~2.5.0"
   },
   "peerDependencies": {
     "@cucumber/cucumber": ">=7.0.0"