Maksim Stepanov

Hello, @lJFoxl ! Starting from 2.10 the OneTimeSetUp/OneTimeTearDown methods of a TestFixture are executed in the context of Allure. This is necessary to convert those methods to Allure fixtures as...

Hi, everyone! We've just released a version that fixes lots of context-related issues including this one. Please, try it: [2.10.0](https://www.nuget.org/packages/Allure.NUnit/2.10.0). Please, note, that currently it's mandatory to apply `[AllureBefore]` or...

Hi, @DenisKorbovskyTds It happens because no test is run by NUnit once OneTimeSetUp fails (regardless of AllureBefore) Hence, there are no test results. It might be possible to create skipped...

That overload has been introduced as part of #371. Released in 2.10.0

Should be fixed in 2.10.0. Please, leave me a comment here in case it's not.

Custom labels can be created using a pattern defined in allureConfig.json (`specflow/labels/label`). Also, the tag-to-label conversion works in Allure Report now, starting from 2.27.0.

Hi, @sphinxy and everyone! We've put a lot of effort into making all integrations concurrency-friendly. In the recent 2.10.0 version of both Allure.XUnit and Allure.NUnit all those annoying async-related bugs...

Hi, @sanchos ! The original issue with `allure-behave` was resolved, so I'm closing this. If you faced a bug while using `allure-pytest` with `pytest_generate_tests`, please, do not hesitate to open...

Currently, only parameter\`s value could be inserted into a test title using the `@allure.title` decorator. Inserting a key of a parameter set through the decorator is not supported now. But...

Unable to reproduce. Closing. If someone is still facing this issue, please, let me know and I will reopen.