Maksim Stepanov
Maksim Stepanov
In Allure.NUnit 2.10.0 package, an error began to occur in the AllureNUnitAttribute.AfterTest method
Hello, @AlexZhirkov1 ! Thanks for the report. I'll try to reproduce it. Would be much of a help if you provide me with a reproducible case though (the code of...
Hi, @evgeniy-skt ! We've reduced the requirement on AspectInjector. The newly released 2.10.0 version of the package now depends on AspectInjector v2.8.1. That should help until the actual fix is...
Hi, @vladdex ! Try to remove `[AllureNUnit]` from setup fixtures and base classes: ```csharp [SetUpFixture] public class Setup { [OneTimeSetUp] public void Setup1() { Console.Out.WriteLine("setup"); } } [TestFixture] [AllureNUnit] public...
Hi, @mingazhev ! Thank you for your report. Please, tell me the following: 1. The target framework 2. The OS 3. The processor architecture
Hi, @vladdex What runtime do you use?
This is because pytest-asyncio-cooperative messes with an expected lifecycle of a test. It calls a test function directly inside its own event loop before allure-pytest even knows that there actually...
Hi, @ushankax. Thank you for the feature request. That's something that might be implemented in the future. Sorry for not giving any specific date. That said, it's much quicker to...
Hi, @algirdasN , thank you for your contribution! You're correct. Since `MultipleAssertException` is clearly assertion-related and isn't derived from `AssertionException`, we want it to be included in the default `failExceptions`....
Hi, @Peyzzz . Thank you for the report. Unfortunately, it's unlikely I will have enough time to address that in the near future, though. Consider migrating to [Reqnroll](https://reqnroll.net/), the reboot...
No response from the OP. Superseded by #845