We would like to have a custom Python scenario step generate a warning based on custom code logic. Generating a step failure is easy as we can just abort the step (as shown in this link) or just raise an exception in Python code. However there is no option to end the custom Python scenario step in a warning outcome. The use case is to surface some inconsistencies in our data layer APIs, which we access via Python, which need to be reviewed but don't warrant a step failure. We are currently using scenario variables to expose this but this obviously needs the additional use of a Scenario Reporter and requires human intervention (ie they need to see the Reporter). Having the ability to see it in the scenario outcome itself and find out which step threw the warning would make it much more visible and easy to see.
