Open Venomicon opened 4 months ago
As part of the execution model, every step is always executed. But every step after a failing step is executed in dry-run mode and will not invoke the glue code. I.e. it is skipped.
The reasons for this are pretty much historic now. They have their origins in the original Ruby implementation. The test step event docs could probably be updated to include that information.
For now you may want to use the TestStepFinished
event instead and filter on it's result status.
Hi, we're using ConcurrentEventListener to access Step text via TestStepStarted event listener. These steps can later be logged to a file and attached to the failed test in the Allure report. Unfortunately, it does not work as expected.
👓 What did you see?
All steps for given scenario are being logged, even the ones that occur after the scenario failure.
✅ What did you expect to see?
I expect, that steps after the failed step are not logged, because as name suggests for "TestStepStarted" event - these steps have not yet started because of the failure.
📦 Which tool/library version are you using?
🔬 How could we reproduce it?
Given scenario:
ConcurrentEventListener implementation:
cucumber.properties: