Maksim Stepanov

Results 106 comments of Maksim Stepanov

False positive test count when same test is associated with multiple features.

This is outside of the scope of allure-pytest. The generated result file is well-defined and contains multiple feature labels (I have omitted unrelated fields and labels): ```json { "name": "test_issue604_reproduction",...

Allure Dynamic methods - allure.dynamic.feature( 'feature name') , this duplicates the tests, under given feature in reports if same feature is added multiple times via allure.dynamic.feature() method

Same problem as in allure-framework/allure2#1883. This is not a bug, more of unspecified behavior area, since no label uniqueness policy was implemented to begin with. We need first to come...

Allure Dynamic methods - allure.dynamic.feature( 'feature name') , this duplicates the tests, under given feature in reports if same feature is added multiple times via allure.dynamic.feature() method

Ok, so this should be implemented on the report generator level. I'm transferring the issue now.

Test duplication in the report when dynamically applying the same title or story multiple times

Basically, what happens is that `allure.story` is called multiple times within the same test function. Putting `hypothesis` and `schemathesis` aside, the issue could be reproduced with the following test: ```python...

Test duplication in the report when dynamically applying the same title or story multiple times

Update: this should be implemented on the reported level. I'm transferring the issue now.

Add posibility to allure_robotframework listener to send "broken" test status to allure

Hi, @MrBIN89 Yep, we should definitely use `BROKEN` for non-assertion-related errors. Also, take a look at [allure categories](https://docs.qameta.io/allure/#_categories_2). That might be the feature you're looking for.

allure-pytest raises an exception when writing to log from a thread started inside pytest_generate_tests

Hi, @eltimen, thanks for the report. Looks like our long-running problem with concurrency. See #697 and #720 We'll fix that eventually, but unfortunately, I can't estimate the date right now.

Use 3rd listeners interface version for allure_robotframework listener

Hello, @MrBIN89 ! Thank you for the feature request! Could you please elaborate on what do you mean by extending the listener? How would you have used the listener to...

allure-pytest: using the same @pytest.mark.parametrize for tests with different browsers appear as retries of the same test in the test report.

Hi, @win5923 I'll take a look today or tomorrow.

allure-pytest: using the same @pytest.mark.parametrize for tests with different browsers appear as retries of the same test in the test report.

Hi, @win5923 ! Some updates regarding this issue. I confirm there is a bug in allure-pytest related to how a dynamic parameter updates an existing parameter specified by pytest (or...