[allure-behave] Support @flaky tag for scenarios (to mark them as flaky in the allure report)

[m-i-tk]

I'm submitting a ...

• bug report
• feature request
• support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?

In an allure report based on the output of the allure-behave formatter, a @flaky tag is simply shown in the list of all scenario tags.
But the scenario is not marked as flaky or special in any way.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

Use the allure-behave formatter for testruns with scenarios containing a @flaky tag and view the corresponding allure test report.

What is the expected behavior?

It would be nice if a scenario tagged as flaky was marked as flaky in the json file produced by the allure-behave formatter (allure's flaky attribute set to True) - and thus shown as flaky test in a resulting allure test report.

What is the motivation / use case for changing the behavior?

Scenarios tagged as flaky could be more easily spotted in the overall allure test report.

Allure does support marking tests as flaky:
https://docs.qameta.io/allure/#_flaky_tests

Tagging a scenario or feature as flaky is apparently already supported by allure-cucumber-jvm:
https://docs.qameta.io/allure/#_test_markers

Please tell us about your environment:

• allure-behave 2.5.1
• allure-python-commons 2.5.1
• allure 2.3-SNAPSHOT

Other information

[sseliverstov]

As I know, allure commandline marks tests as flaky by history of rans. No way to mark from code, but hope, in next major versions it will be possible.

[enrico-semrau]

any update on this? it seems its still not working when adding a "flaky" tag within the code.