Currently allure_robotframework listener can send just four statuses to Allure - PASSED, FAILED, SKIPPED, UNKOWN (only in failure case), those are hardcoded in get_allure_status function.
What is the expected behavior?
Add possibility to send other test statuses, for example, BROKEN that actually in the default allure statuses list.
What is the motivation / use case for changing the behavior?
In my case we need to divide failed cases by different statuses on allure(failed for usual failures and broken for known cases with opened issues)
I'm submitting a ...
What is the current behavior?
Currently allure_robotframework listener can send just four statuses to Allure - PASSED, FAILED, SKIPPED, UNKOWN (only in failure case), those are hardcoded in
get_allure_status
function.What is the expected behavior?
Add possibility to send other test statuses, for example, BROKEN that actually in the default allure statuses list.
What is the motivation / use case for changing the behavior?
In my case we need to divide failed cases by different statuses on allure(failed for usual failures and broken for known cases with opened issues)
Please tell us about your environment:
allure-python-commons 2.13.2 allure-robotframework 2.13.2