Is there an option for us to customize and group the test scenarios in the statics section of the Karate Gatling Report?

Is there an option for us to customize and group the test scenarios in the statics section of the Karate Gatling Report?



In the statics section of the Gatling report, the tests are grouped based on paths. However in our case the API URI + path is same and the functional flow will be differentiated based on the header values and the request method is POST. So in this case even if I test four different scenarios/flows, all the tests will be grouped as a single, since the path is same. Is there any option for us to group the statistics section based on scenarios/something else?



enter image description here



Is there any option for us to group the tests based on these scenarios? The expectation is something similar to this. The below one is a screen shot from a gatling.io page. It seems to be a web based application
enter image description here






can you build and test the latest from the cukexit branch ? github.com/intuit/karate/issues/526

– Peter Thomas
Sep 14 '18 at 9:55


cukexit






Tested with the version 0.9.0.RC2 and it works fine now. Added the details below

– Sree
Sep 17 '18 at 11:42





2 Answers
2



Talk about timing. Here's the issue I raised a few hours back: https://github.com/intuit/karate/issues/526



So yes, this is a gap we are planning to address. Counting on you for beta-testing.



This enhancement is now done on Karate-Gatling on the release 0.9.0.RC2 version. The statistical analysis will now display the results based on each business flows. So now onward you can have separate analysis for each business flow. This is the way the result will looks like in the new release
enter image description here



You can also do a detailed analysis of percentiles, deviations of each business flow separately.
enter image description here






awesome. thanks for the quick confirmation !

– Peter Thomas
Sep 17 '18 at 11:45



Thanks for contributing an answer to Stack Overflow!



But avoid …



To learn more, see our tips on writing great answers.



Required, but never shown



Required, but never shown




By clicking "Post Your Answer", you agree to our terms of service, privacy policy and cookie policy

-