Maksim Stepanov

Fixed in 2.0.0.beta-20 via #510. Remains fixed in 3.0.0-beta.3, which uses a different approach to the parallel mode.

The issue has been fixed in 3.0.0-beta.1. If anyone still struggles with using Allure API in parallel mode, feel free to open a new issue or post an update here.

Allure-mocha now handles the parallel mode differently. We don't rely on how Mocha serializes its events anymore. Instead, we emit the results directly from the worker processes, which have access...

Pre 2.10 version of allure-python did too much of thread isolation, leading to hooks added in one thread being inaccessible from another. Hooks responsible for flushing test results to the...

This happens because `historyId` of a test result is calculated based on the `nodeid` of a test, i.e doesn\`t depend on environment in which the test was run. A `historyId`...

Reproducible even with function-scoped fixture. #### Steps to reproduce 1. Given `issue475.feature`: ```gherkin Feature: Issue 475 investigation Scenario: Reproducing the issue 475 ``` 1. And `issue475_test.py`: ```python import allure import...

Keywords are steps in allure terminology. All logging inside a keyword is step-scoped, hence, one file per keyword. It\`s not an ideal solution but a consistent one. We can probably...

#### Less verbose case to reproduce the issue Given the following feature file (lets name it `issue432.feature`): ```gherkin Feature: Reproduce issue 432 Scenario: Scenario to reproduce issue 432 Given scenario...

Unfortunately, can't tell for sure now. Will provide you with more details as soon as I have any.

Hello, @NikitaEgorov ! Thank you for your report. I'll look into how Rider runs xUnit and if we can do something about it. Just for now, I see two options:...