@wdio/junit-reporter 10.0.0-alpha.149 → 10.0.0-alpha.18

package/README.md

@@ -149,23 +149,18 @@ export const config = {
 The following options are supported:
 
 ### outputDir
-
-<Option type="String">
-
 Define a directory where your XML files should get stored. Ignored if either `logFile` or `setLogFile` are defined.
 
-</Option>
+Type: `String`
 
 ### outputFileFormat
-
-<Option type="Object" default={`(opts) => \`wdio-\${opts.cid}-junit-reporter.log\``}>
-
 Function for defining the filename format for the reporter log files. Ignored if either `logFile` or `setLogFile`
 are defined.
 
 The function accepts an object input parameter with the `cid` and `capabilities` keys.
 
-</Option>
+Type: `Object`<br />
+Default: ``(opts) => `wdio-${opts.cid}-junit-reporter.log` ``<br />
 Example:
 ```js
 // wdio.conf.js
@@ -180,13 +175,10 @@ export const config = {
 ```
 
 ### logFile
-
-<Option type="String">
-
 Path to the reporter log file relative to the current directory. Overrides `outputDir` and `outputFileFormat`.
 Ignored if `setLogFile` is defined.
 
-</Option>
+Type: `String`<br />
 Example:
 ```js
 // wdio.conf.js
@@ -200,14 +192,11 @@ export const config = {
 ```
 
 ### setLogFile
-
-<Option type="Object">
-
 Function for defining the path for the reporter log files. Overrides `outputDir`, `outputFileFormat`, and `logFile`.
 
 The function accepts two input parameters: `cid` and `name` (the reporter name, set to `junit`).
 
-</Option>
+Type: `Object`<br />
 Example:
 ```js
 // wdio.conf.js
@@ -221,32 +210,25 @@ export const config = {
 ```
 
 ### stdout
-
-<Option type="boolean" default="false">
-
 Output the generated XML to the console instead of creating a log file.
 
-</Option>
+Type: `boolean`<br />
+Default: `false`
 
 ### writeStream
-
-<Option type="WriteStream">
-
 Set a stream to which the generated XML should be output, instead of creating a log file.
 
 Note: `logFile` must not be set, unless `stdout` is set to `true`.
 
-</Option>
+Type: `WriteStream`
 
 ### suiteNameFormat
-
-<Option type="Regex | Object" default="/[^a-zA-Z0-9@]+/">
-
 Format the generated name of a test suite, using custom regex or a function.
 
 The function accepts an object input parameter with the `name` and `suite` keys.
 
-</Option>
+Type: `Regex | Object`,<br />
+Default: `/[^a-zA-Z0-9@]+/`<br />
 Example with Regex:
 ```js
 // wdio.conf.js
@@ -273,15 +255,12 @@ export const config = {
 ```
 
 ### classNameFormat
-
-<Option type="Object">
-
 Format the generated classname of a test case.
 
 The function accepts an object input parameter with the [`packageName`](#packagename), `activeFeatureName`
 (Cucumber only), and `suite` (non-Cucumber only) keys.
 
-</Option>
+Type: `Object`<br />
 Default (Cucumber): ``(opts) => `${opts.packageName}${opts.activeFeatureName}` ``<br />
 Default (others): ``(opts) => `${opts.packageName}.${(opts.suite.fullTitle || opts.suite.title).replace(/\s/g, '_')}` ``<br />
 Example (Cucumber):
@@ -309,14 +288,14 @@ export const config = {
 };
 ```
 
-### addFileAttribute
 
-<Option type="Boolean" default="false">
+### addFileAttribute
 
 Adds a `file` attribute to each testcase. The value of this attribute matches the filepath property of the parent test
 suite. This config is primarily for CircleCI, but may break on other CI platforms.
 
-</Option>
+Type: `Boolean`<br />
+Default: `false`<br />
 Example simplified XML:
 ```xml
 <testsuite>
@@ -331,11 +310,9 @@ Example simplified XML:
 
 ### packageName
 
-<Option type="String">
-
 You can break out packages by an additional level by setting `'packageName'`. For example, if you wanted to iterate over a test suite with a different environment variable set:
 
-</Option>
+Type: `String`<br />
 Default (Cucumber): `CucumberJUnitReport-${sanitizedCapabilities}`<br />
 Default (others): `${sanitizedCapabilities}`<br />
 Example:
@@ -354,8 +331,6 @@ export const config = {
 
 ### errorOptions
 
-<Option type="Object" default={`errorOptions: { error: "message" }`}>
-
 Allows to set various combinations of error notifications inside xml.<br />
 Given a Jasmine test like `expect(true).toBe(false, 'my custom message')` you will get this test error:
 
@@ -372,7 +347,8 @@ Given a Jasmine test like `expect(true).toBe(false, 'my custom message')` you wi
 
 Therefore you can choose *which* key will be used *where*, see the example below.
 
-</Option>
+Type: `Object`,<br />
+Default: `errorOptions: { error: "message" }`<br />
 Example:
 
 ```js
@@ -393,11 +369,10 @@ export const config = {
 
 ### addWorkerLogs
 
-<Option type="Boolean" default="false">
-
 Attach console logs from the test in the reporter.
 
-</Option>
+Type: `Boolean`<br />
+Default: `false`<br />
 Example:
 
 ```js
@@ -451,5 +426,3 @@ If there is no such post-build step in your CI system, there is probably a plugi
 ----
 
 For more information on WebdriverIO see the [homepage](https://webdriver.io).
-
-

package/build/index.js

@@ -331,7 +331,7 @@ ${stepsOutput}
     this._addAmbiguousBasenameSuites(builder, runner, isCucumberFrameworkRunner, assignedSuiteKeys);
     return builder.build();
   }
-  _buildOrderedReport(builder, runner, specFileName, type, isCucumberFrameworkRunner, assignedSuiteKeys) {
+  _buildOrderedReport(builder, runner, specFileName, type, isCucumberFrameworkRunner, assignedSuiteKeys = /* @__PURE__ */ new Set()) {
     const suiteKeys = Object.keys(this.suites);
     if (suiteKeys.length === 0) {
       if (!isCucumberFrameworkRunner || isCucumberFrameworkRunner && type === "feature") {

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "@wdio/junit-reporter",
-  "version": "10.0.0-alpha.149+ce13bea83",
+  "version": "10.0.0-alpha.18+dbf0f4971",
   "description": "A WebdriverIO reporter that creates Jenkins compatible XML based JUnit reports",
   "author": "Christian Bromann <mail@bromann.dev>",
   "homepage": "https://github.com/webdriverio/webdriverio/tree/main/packages/wdio-junit-reporter",
   "license": "MIT",
   "engines": {
-    "node": ">=22.19.0"
+    "node": ">=18.20.0"
   },
   "repository": {
     "type": "git",
@@ -33,12 +33,12 @@
       "require": "./build/index.cjs"
     }
   },
-  "typeScriptVersion": "6.0.3",
+  "typeScriptVersion": "3.8.3",
   "dependencies": {
-    "@wdio/reporter": "10.0.0-alpha.149+ce13bea83",
-    "@wdio/types": "10.0.0-alpha.149+ce13bea83",
+    "@wdio/reporter": "10.0.0-alpha.18+dbf0f4971",
+    "@wdio/types": "10.0.0-alpha.18+dbf0f4971",
     "json-stringify-safe": "^5.0.1",
-    "junit-report-builder": "^5.1.2"
+    "junit-report-builder": "^5.1.1"
   },
   "devDependencies": {
     "@types/json-stringify-safe": "^5.0.0"
@@ -46,5 +46,5 @@
   "publishConfig": {
     "access": "public"
   },
-  "gitHead": "ce13bea839fb037eceda429dbf94cd387b7c3584"
+  "gitHead": "dbf0f497130676040ce4212d9cf6459adfe16c42"
 }

package/AGENTS.md

@@ -1,20 +0,0 @@
-# @wdio/junit-reporter
-
-JUnit XML reporter. It extends `@wdio/reporter`. User docs are this package's `README.md`.
-
-## Commands
-
-```sh
-pnpm run test:package wdio-junit-reporter
-```
-
-CJS `addProperty` load check: `pnpm --filter @wdio/test-interop-cjs run test:junit-reporter`.
-
-## Test ownership
-
-- JUnit XML shape (suites, failures, skips, Cucumber scenarios, BrowserStack package names, and file association) is owned by `tests/reporter.test.ts` through `_buildJunitXml`. Keep those snapshots. Do not stub the suite builders and assert the stub.
-- `onRunnerEnd` must write the built report. Assert that document. A mocked `undefined` snapshot does not.
-- Whitespace-stripped snapshots do not lock command-log spacing. Exact `COMMAND:` / `RESULT:` text stays on the stdout test.
-- `addProperty` is the public worker API (process event `junit:addProperty`). Call `addProperty`, not the private listener.
-- `addWorkerLogs` is owned by writing to `stdout` while a test is current, then restoring `stdout.write`.
-- The CJS interop check uses `assert.equal(typeof fn, 'function')`. `assert(typeof fn, 'function')` cannot fail.