我们是否可以在“空手道加特林报告"的“静态"部分中自定义和分组测试方案? [英] Is there an option for us to customize and group the test scenarios in the statics section of the Karate Gatling Report?

问题描述

在加特林"报告的静态"部分中，测试是根据路径进行分组的.但是，在我们的示例中，API URI +路径相同，并且功能流将基于标头值进行区分，并且请求方法为POST.因此，在这种情况下，即使我测试了四个不同的场景/流程，由于路径相同，所有测试也将被分组为一个测试.我们是否可以根据情况/其他方式对统计部分进行分组?

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?

我们是否可以根据这些方案对测试进行分组?期望与此类似.以下是gatling.io页面的屏幕截图.它似乎是一个基于Web的应用程序

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

推荐答案

讨论时间安排.这是我几个小时后提出的问题: https://github.com/intuit/karate/Issues/526

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

是的，这是我们计划解决的差距.依靠您进行Beta测试.

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

自0.9.0版开始可用-通过指定nameResolver起作用:首先在交易中放置标头，然后使用nameResolver将其用于对交易进行分组:

Available since version 0.9.0 - this works by specifying a nameResolver: first put a header in your transaction and use a nameResolver to use this to group the transactions:

protocol.nameResolver = (req, ctx) => req.getHeader("karate-name") 

请参阅文档: https://github.com/intuit /karate/tree/master/karate-gatling#nameresolver

这篇关于我们是否可以在“空手道加特林报告"的“静态"部分中自定义和分组测试方案?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！