When using Gherkin scripts for testing and importing test results from Cucumber via the REST API
I want to see which steps of a BDD Cucumber test, based on Gherkin, are executed, passed and even failed. As currently the overall status could be passed/failed but the steps are not reflected and are shown as not executed.
So that I can find the bug/error/failure quickly and precisely in the course of my test case
It's done when I am able to find a bug caused by a single step (e.g. "Given I launch browser") directly.
|I would like...||to see more detail from Cucumber executions in the test player|
|So that I...||can see where the source of failure is|