You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using 2.0.0, I used ScenarioResult to get the status of the test scenario and also the name of the current scenario. This was useful as I had a conditional statement on failure to take a screenshot and name it after the failed scenario, making it easy to see exactly where each scenario was falling. #919, I believe was used to 'fix' ScenarioResult as it was no longer functioning in more recent versions of Cucumber-js. I am now using V 3.0.3 as testCase gives me a similar function as ScenarioResult. However, unlike ScenarioResult, it does not contain the scenario name in the object (it does contain the status of the test though, at least). Is there a new method to get the name of the scenario? At the moment it seems to only give the name of the feature file this failure comes from, which is not specific enough for my needs. Thanks in advance :)
The text was updated successfully, but these errors were encountered:
When using 2.0.0, I used ScenarioResult to get the status of the test scenario and also the name of the current scenario. This was useful as I had a conditional statement on failure to take a screenshot and name it after the failed scenario, making it easy to see exactly where each scenario was falling. #919, I believe was used to 'fix' ScenarioResult as it was no longer functioning in more recent versions of Cucumber-js. I am now using V 3.0.3 as testCase gives me a similar function as ScenarioResult. However, unlike ScenarioResult, it does not contain the scenario name in the object (it does contain the status of the test though, at least). Is there a new method to get the name of the scenario? At the moment it seems to only give the name of the feature file this failure comes from, which is not specific enough for my needs. Thanks in advance :)
The text was updated successfully, but these errors were encountered: