我可以在 VS.Net 2010 负载测试中排除失败的 Web 测试计数吗？
我正在使用 Visual Studio 2010 Ultimate 来执行负载测试。这些负载测试使用记录的网络测试。
当并发用户数量不断增加时运行负载测试时，我的网络测试中的某些步骤将开始失败。第一个错误通常是内部服务器错误 500。这会给平均 page_load 带来错误的印象，因为这些内部服务器错误通常返回得非常快，与生成成功的响应相反。因此，当负载增加时，平均 page_load 会下降。
当然，我需要注意这些内部服务器错误，但与此同时，我想从我的测量中排除失败的网络测试。
有人知道这是否可以做到吗？
提前致谢。
I am using Visual Studio 2010 Ultimate to perform loadtests. These loadtest use recorded webtests.
When running a loadtest with an increasing number of concurrent users, some steps in my webtests will start to fail. The first error is often an internal server error 500. This will give a wrong impression of the average page_load, because these internal server errors are often returned very fast, in contrast to the generation a succesful response. So, when the load increases, the average page_load drops.
Of course, I need to attend to these internal server errors, but in the meantime, I would like to exclude failed webtests from my measurements.
Does anybody know if this can be done?
Thanks in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
可以在测试结果数据库上运行您自己的查询来忽略错误，但即使这样也是不准确的。
请记住，页面返回统计信息实际上仅在与硬件负载结合读取时才有用。
本质上，负载测试是记录给定负载对硬件的影响。如果您的网站快速返回大量 500 个错误页面，则硬件上的负载将受到影响，并且任何页面统计信息都会反映服务器负载的变化。
您必须调查 500 错误的原因，并解决问题或在负载测试结果中报告，一旦服务器上达到“x”负载，页面“y”将给出内部服务器错误 500 结果而不是请求的页面。
这为您的应用程序的企业主提供了一些信息，以决定是解决问题还是忍受它。
It may be possible to run your own query on the test results database that ignores errors, but even that will be inaccurate.
Remember that the page return stats are really only useful when read in conjunction with the load on the hardware.
Essentially, the load test is recording the effect on your hardware of a given load. If you website is returning a large number of 500 error pages quickly, the load on the hardware will be affected and any page stats will reflect the change in server loading.
You will have to investigate the cause of the 500 errors and either fix the issue or report in your load testing results that once a load of 'x' is reached on the servers, the pages 'y' will give an internal server error 500 result instead of the requested page.
This gives the business owners of you app some information to make the decision whether to fix the problem or live with it.