Cucumber-Json flags failed tests as passed if an exception occurs

Version: bdd-4,0,2 pytest: 6.2.2

Summary
When a test fails with eg an keyerror exception due to an invalid test step, the cucumber-json will mark the test case as passed. When imported back into eg XRAY the test is marked as passed when in fact it has not.

This happens because the invalid step is not included in the test report scenario.steps and will therefore not appear in the cucumber-json causing test cases results to be inaccurate.

Steps to Repro:

1. Execute a feature file containing a step not defined in the framework. This will trigger an KeyError exception and a FixtureLookupError. Ensure the --cucumber-json flag was passed into pytest-bdd :

Scenario:  repro
    Given this step should exist and be valid
    And this step should not exist

2. Examine the resultant cucumber-json file. Notice the test case is marked as passed as the erroring test step was not included.

Reproduce the issue by running the feature with an undefined step and the --cucumber-json flag, then inspect the generated cucumber-JSON and scenario.steps handling. The fix is complete when a KeyError or FixtureLookupError makes the test case appear as failed rather than passed in the report.