我们能否在检查站使用Visual Studio VSTS。 [英] Can we checkpoints in VSTS using Visual Studio.

问题描述

我们可以插入脚本中的检查点。例如，在负载测试。我们得到每个URL的结果。如果网站使用相同的URL为许多不同的页面，这页混为一谈入结果单个URL。在QALoad，有可能创建脚本闯关，这是我们如何能够看到性能的每一页，无论URL的。我们可以通过VSTS实现这一目标？请帮助。

Can we insert checkpoints in the scripts. For example In load tests. we get results for each URL. If site is using same URL for many different pages, that pages lumped together into single URL in the result. In QALoad, it was possible to create "checkpoints" in the script, and that is how we were able to see the performance for each page, regardless of URL. Can we achieve this by VSTS ? Please help.

推荐答案

有至少两个可能的机制。

There are at least two possible mechanisms.

在每个请求你可以设置一个报告名称。这可以被设置，并通过该请求的属性面板更新;但是这可能是很乏味的使用。在设置要求详细信息面板可以用的Web测试图标之一被打开并允许报告的名称（和也认为时间和响应时间目标），以用于在测试的所有请求进行设置。报告名称在从Visual Studio的各种报告中。有些人建议的报告名称来给所有的请求，他们包括序列号，使其明确的各项要求如何与通过测试的流量。

On each request you can set a "reporting name". This can be set and updated via the properties panel of the request; but that can be tedious to use. The "Set request details" panel can be opened with one of the web test icons and that allows reporting names (and also think times and response time goals) to be set for all the requests in the test. The reporting names are used in the various reports from Visual Studio. Some people recommend that reporting names be given to all requests and that they include sequence numbers that make it clear how the various requests relate to the flow through the test.

另一种选择是把请求变成交易的。然而，交易是用于分组报告为一组，以及单独的请求数量较少更加有用。

Another option is to put requests into "transactions". However, transactions are more useful for grouping small numbers of requests that are to be reported as a group as well as individually.

这篇关于我们能否在检查站使用Visual Studio VSTS。的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！