-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve cucumber json / html report output for called features #379
Comments
Hi Peter, thanks for adding the feature request! All the features I call have always only one scenario that is designed in a generic way, in order to be able to call them with different payloads and evaluate different responses. |
also there was an xml node bug that borked the svg image in html report only for demo, looks like classpath lib changes via gatling caused different behavior, xml parser changed ? anyway fixed with safer xml node conversion approach
@backfloep 0.8.0.RC3 is available, please try this and let me know if it looks ok |
@ptrthomas I was also looking for something like posted as part of this issue, i have taken 0.8.0.RC3, wanted to know if we need to any format for printing some reference text for any Step like below: Scenario: Verify that User is able to login
|
@gondos just use the |
released 0.8.0 |
is there a way to have specific rendering of print output in the cucumber report ? |
@ouquoi you can look at HTML via |
@ouquoi yep ! keep in mind this is a 3rd-party report. eventually we will have our own "native" karate report where we will have full control. for now it is a good strategy to be cucumber-compliant and make use of the ecosystem, for example we have the following other integrations: allure, assertThat, trivago cluecumber I just opened a roadmap item: https://github.com/intuit/karate/projects/3#card-23900118 |
As reported here: https://stackoverflow.com/q/49984628/143475
There's an opportunity to add the text of the called Feature title and the (first?) Scenario if it is present.
The text was updated successfully, but these errors were encountered: