Replies: 2 comments 1 reply
-
|
duplicate of issue raised #892 |
Beta Was this translation helpful? Give feedback.
-
|
We should clarify this, because my fear is that the "need" (report skipped tests) behind this request and the "request" (invoke before/after step hooks on skipped steps) is too far away from each other. Side note on the "request" (invoke before/after step hooks on skipped steps): Currently Reqnroll does not provide a way to do this and I don't think it would be generally a good idea to invoke these hooks for the skipped steps. On the "need": The formatter infrastructure we have does support reporting skipped tests and those steps are included both in the cucumber messages and the HTML report we generate. So could you please clarify the circumstances of your need? What kind of reporting you refer to? In general, for reporting purposes, it is better to use the Reqnroll event infrastructure ( Reqnroll/Reqnroll/Formatters/PubSub/CucumberMessagePublisher.cs Lines 86 to 91 in 6f0e3a0 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
For reporting purposes, it is nicer to have all the steps to be able to be added to a report with skipped status when the previous step is failed (which makes the scenario status failed). Currently, this is not supported and thus the report looks like always the failure is with the last step. Rather it would be great if we can force the afterstep/beforestep to be invokable even when the step status is skipped (the status shouldn't be able to be modified).
Certainly other BDD tools allow this as far as I know Cucumber, but reqnroll lacks this.
Beta Was this translation helpful? Give feedback.
All reactions