Proposal for a ReqnRoll Test Execution Report #400
ExpressiumOSS
started this conversation in
Ideas
Replies: 2 comments 1 reply
-
Currently, it is impossible to get the step definition information via hooks when a scenario is ignored or the step definitions are undefined... |
Beta Was this translation helpful? Give feedback.
0 replies
-
There's actually some ongoing work in #233 to allow standard tooling to generate these kinds of reports and to integrate more easily with the broader cucumber ecosystem. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
SpecFlow has reached its end-of-life and we need a replacement for the SpecFlow Living Doc functionality in ReqnRoll...
From my perspective, an MVP for a ReqnRoll Living Doc should be a CLI program designed to post-process an HTML report, similar to the current Living Doc functionality in SpecFlow.
This demo solution is intended to serve as input and inspiration for a potential final solution...
During test execution, an output file named TestAutomation.json will be generated, containing the majority of the information needed to build a custom report generator utilizing the FeatureContext and ScenarioContext classes. Additionally, a lightweight TestExecutionReportGenerator will produce a simple HTML report based on the TestAutomation.json file.
GitHub: https://github.com/ExpressiumOSS/ReqnRollTestExecutionReport
Beta Was this translation helpful? Give feedback.
All reactions