[email protected]

What's new

The new release of Qase API client brings a number of new features:

• Full support of the latest state of the Qase API;
• Full support of the experimental v2 API for working with test results.
• Uploading test attachments from strings and buffers.
• New API endpoints: v1/system-fields/ and v1/configurations/.

[email protected]

What's new

This is the first release in the 2.x series of the Playwright reporter.
It brings a new annotation syntax with test parametrization and field values,
new and more flexible configs, uploading results in parallel with running tests,
and other powerful features.

This changelog entry will be updated soon.
For more information about the new features and a guide for migration from v1, refer to the
reporter documentation

[email protected]

What's new

This is the first release in the 2.x series of the Jest reporter.
It brings new and more flexible configs, uploading results in parallel with running tests,
and other powerful features.

This changelog entry will be updated soon.
For more information about the new features and a guide for migration from v1, refer to the
reporter documentation

[email protected]

What's new

This is the first release version of the Qase JavaScript SDK.
It is numbered 2.0.0 (and not 1.0.0) to match the release series of
test reporters for Playwright, Cypress, Jest, and other frameworks.

Annotating test with field data

Tests can now be annotated with data for the system and custom fields in Qase.
This feature is already implemented in the Playwright reporter:

test('Test with annotated fields', () => {
    qase.id(1);
    qase.fields({ 'severity': 'high', 'priority': 'medium' })
    // ...
});

Parametrized tests

Qase JavaScript SDK enables annotating tests with parameters, and passing parameter values to Qase.
Parameterized tests can report to a single test case, but each parameter variation is registered as
a standalone result, with its own run history.

Attachments from files and variables

Reporters can now upload attachments of various data types to Qase,
both from files and from variables.
It enables flexible and meticulous logging, such as collecting full HTTP request data,
including URL, headers, and payload.

Uploading results in flexible batches, asynchronously

Test reporters can now upload results in batches, while tests are still running.
It helps bring test results faster and enables acting on them long before the test run is complete.

Uniform configuration

Qase JavaScript SDK brings configuration with config files and environment variables
to a common standard, used with Qase reporters in all languages and frameworks.

For details, see the Configuration
section in the README.

Latest API

Qase JavaScript SDK is using the latest Qase API client,
employing the full power of the stable v1 API version,
and enabling the use of experimental v2 API, tailored for uploading
huge amounts of test results.

[email protected]

What's new

This is the first release in the 2.x series of the Cypress reporter.
It brings new and more flexible configs, uploading results in parallel with running tests,
and other powerful features.

This changelog entry will be updated soon.
For more information about the new features and a guide for migration from v1, refer to the
reporter documentation

[email protected]

What's new

Improved debug logging for better testing and reporting errors.

• Separate logger class for use in reporters, supporting logging to console and files.
• Extra debug logs in both reporter modes: TestOps and Local.

Fixed an issue with duplicate test runs created when the testing framework
(such as Cypress) uses more than one instance of the Qase reporter.
Now reporter handles Qase test runs in the following way:

1. The first instance of the reporter creates a Qase test run and stores the run ID
   in the ENV variable QASE_TESTOPS_RUN_ID.
2. Other instances of the reporter read this variable and report test results
   to the existing test run.

Nothing has changed in cases when there is a single instance of a reporter or
when it is using a test run, created with other tools, such as with an API request
or manually in the Qase app.

[email protected]

Fixed an issue with multiple test runs created when Cypress is running
multiple tests in parallel.

[email protected]

What's new

• Using the qase annotation in a chain:

test('Ultimate Question of Life, The Universe, and Everything', async ({ page }) => {
    qase.id(42)
      .title('Ultimate Question of Life, The Universe, and Everything')
      .fields({ severity: high, priority: medium })
      .attach({ paths: '/path/to/file'});
    ...
})

[email protected]

What's new

• Renamed the QASE_TESTOPS_CHUNK environment variable to QASE_TESTOPS_BATCH_SIZE.
• Renamed the chunk field in the reporter's configuration to batch.size:

{
  ...
  "testops": {
-   "chunk": 10
+   "batch": {
+      "size": 10
+    }
    ...
  },
  ...
}

[email protected]

The first major beta release for the version 2 series of the Qase Cypress reporter.

A detailed changelog will be added later.