Dmitry Baev

the problem should be already fixed in `[email protected]`, could you please give it a try

Kotest issues should be reported here https://github.com/kotest/kotest-extensions-allure The Allure Team doesn't yet maintain it. However, I'll try to squeeze it into the team's schedule so we can at least review...

Fixed in 3.0.0-beta.11

@dzianisMazhuhou, please make sure you're using the latest versions of vitest and allure-vitest. The issue should be fixed in `[email protected]`; see https://github.com/allure-framework/allure-js/pull/885.

The report duration is the time between the very first test start and the very last test stop. In case you preserve `allure-results` folder between the runs, it may show...

The workaround is to specify `nestedName`: ```kts dockerCompose { nestedName = "test" } ```

There are two issues in there: 1. Since `2.7.0` `detail` and `suiteTitle` are now set to true by default. Because of that system `attach` steps are now reported. I completely...

Disabling the Allure integration will break the Allure Runtime API calls. Why does having the Allure plugin bother you?

The error isn't in the Allure code. Allure accepts environment constructor arguments and passes them to the `NodeEnvironment` without modifications. And only then, `NodeEnvironment` complains about the missing `projectConfig`. It...

The issue could be reproduced by using jest@27 or below: ```json { "name": "jest-esm-typescript", "version": "1.0.0", "type": "module", "description": "", "main": "index.js", "scripts": { "test": "node --experimental-vm-modules node_modules/jest/bin/jest.js" }, "keywords":...