stories duplication on different features about allure-pytest HOT 6 CLOSED

Sorry, but I cant undestand what exactly is wrong.
The test gets duplicate story labels? The test gets shown in different features, but it should not?
Could you please be a bit more precise?
Also, providing a minimal working example could greatly help -- so we can reproduce the issue locally.

from allure-pytest.

Yep a little bit later (i hope it would be today) i'd give full example what have I found pretty weird with python project.
Now I can just say that stories accumulating in features they should be in. For example if i have 40 features with only one mixin which runs configurable test agains testcase i would get 40 strories (test_unique_id) and these 40 strories would have each 40 tests for their features.

I hope my full example will provide more help than just raw problem description.

from allure-pytest.

demo:
https://github.com/tarvitz/python-allure-demo

its result:
http://178.79.168.130/#/features

from allure-pytest.

Ehm. Can you post the generated XML for those reports?
Also, the metaclass used has some non-trivial implementation, which makes it harder to see the possible real problem. Do you can reproduce similar behaviour via plain-old pytest?

from allure-pytest.

http://178.79.168.130/allure/
Metaclassed TestCases (TestCaseExtended) could be skipped in this demo just because the bug works and represents himself fine with test case Mixins.

I wrote them to see how modified test cases which has fully independeble bases and test_* methods would work with this bug :)

from allure-pytest.

UTR for 2.x

from allure-pytest.