Dmitry Baev
Dmitry Baev
will be implemented via https://github.com/webdriverio/webdriverio/pull/14719
Please update to `[email protected]` Not many changes are planned to be added before the 3.0.0 release, so it should be safe to use it.
closed as stale
@roydekleijn Sorry, mate. We're trying our best to react to all the community feedback. As for today, the best way to contact the team is to create a discussion: https://github.com/orgs/allure-framework/discussions....
As far as I understand, you're trying to set a description to test from before hooks. But what if the suite has multiple tests? The description will be only set...
It was like that in older versions, and lots of our users asked to exclude skipped tests from the success rate calculation. Actually, it was one of the most popular...
I guess the other option is to use Playwright tags after https://github.com/allure-framework/allure-js/pull/1034 gets merged: ```ts import { test } from '@playwright/test'; test("test with allure id", { tag: "@allure.id:123" }, async()...
The issue should be fixed in 3.2.0, please give it a try
@zyab1ik Since 3.0.0-beta.10, allure-codeceptjs integration was reworked. Now, it uses a Mocha reporter underneath (taking allure-mocha as a baseline) and enriches the report using some Codeceptjs events. I honestly don't...
@zyab1ik thanks According to https://github.com/codeceptjs/CodeceptJS/issues/698#issuecomment-327282346, the console output will not work if a custom reporter is used. Since Allure currently overrides the specified reporter configuration, the options mentioned above will...