VS2010 编码 UI 测试与 Web 性能测试(有何不同??) [英] VS2010 Coded UI Tests vs. Web Performance test (Whats the difference??)

问题描述

和两个人一起玩了几个小时.

Been playing with both for a couple hours.

您使用编码的 UI 测试来记录一些操作并通过断言对其进行验证..

You use a Coded UI test to record some actions and verify them through assertions..

您使用 Web 性能测试来记录一些操作并通过验证测试/提取测试来验证它们...基本上相同的事情...然后您可以像编码的 UI 测试一样选择性地转换为代码

You use a Web Performance test to record some actions and verify them through validation tests/extraction tests... basically same thing... then you can convert to code optionally like the Coded UI Tests

但似乎你只能将 WEB PERFORMACE TEST 添加到 loadTest...

But it seem you can only add a WEB PERFORMACE TEST to a loadTest...

但它们不是几乎一样的东西吗??我有什么不明白的??为什么不允许编码 UI 测试在负载测试中?

But arent they both pretty much the same thing?? What am I not understand?? Why not allow a Coded UI Test to be inside a load test?

推荐答案

我认为这个 文章 对这次讨论很有价值

i think this article has a great value on this discussion

CodedUI 测试 –编码的 UI 测试用于自动化功能测试.这些测试将模拟用户对 UI 的交互，例如按钮点击和输入文本.编码的 UI 测试需要交互式桌面环境，因为它们实际上与应用程序的窗口和对象进行交互.VS2010 中的编码 UI 测试相当于使用 HP QuickTest Pro 或 Selenium 之类的东西来驱动自动功能回归测试.

CodedUI Tests – Coded UI tests are for automated functional testing. These tests will simulate user interaction against the UI, such as button clicks and entering text. Coded UI tests require an interactive desktop environment, because they actually interact with the windows and objects of your application. Coded UI Tests in VS2010 are the equivalent of using something like HP QuickTest Pro or Selenium to drive your automated functional regression tests.

Web 性能测试 -Web 测试不仅仅是 GUI 测试.Web 性能测试用于测试网页、Web 应用程序、网站、Web 服务以及所有这些的组合的功能和性能.可以通过记录用户与 Web 应用程序交互期间的 HTTP 请求和事件来创建 Web 性能测试.记录还捕获网页重定向、验证、查看状态信息、身份验证和所有其他活动.它可以分为两种方式，包括简单的 Web 性能测试和编码的 Web 性能测试.

Web Performance Tests - Web testing has much more than GUI testing. Web Performance Tests are used for testing the functionality and performance of the web page, web application, web site, web services, and combination of all of these. Web Performance Tests can be created by recording the HTTP requests and events during user interaction with the web application. The recording also captures the web page redirects, validations, view state information, authentication, and all the other activities. It can be classified in two ways which includes Simple Web Performance Tests and Coded Web Performance Tests.

Simple Web Performance Tests 根据一系列有效事件流的记录生成并执行测试.一旦开始测试，将不会有任何干预，也没有条件.

Simple Web Performance Tests generate and execute the test as per the recording with a series of valid flows of events. Once the test is started there won’t be any intervention and it is not conditional.

编码的 Web 性能测试更复杂，但提供了很大的灵活性.这些类型的测试用于基于值的条件执行.编码的 Web 测试可以手动创建，也可以从 Web 性能测试记录中生成.

Coded Web Performance Tests are more complex but provide a lot of flexibility. These types of tests are used for conditional execution based on values. Coded web tests can be created manually or generated from the Web Performance Test recording.

负载测试-负载测试在 HTTP 级别记录和驱动您的应用程序.这些测试通过直接发送 HTTP 请求来模拟无头用户与您的应用服务器的交互，无需 UI.负载测试通常假设您的应用程序对 1 个用户正常工作，但旨在查看它是否在重用户负载下运行.负载测试是无头的，因为用交互式 UI 模拟成千上万的用户是不切实际的.通过无头，单个负载代理机器可以模拟成百上千的用户.VS 负载测试相当于使用 HP LoadRunner 或 JMeter 来驱动虚拟用户负载.

Load Tests- Load tests record and drive your application at the HTTP level. These tests simulate headless user interaction against your app server by sending HTTP requests directly, without a UI. Load tests typically assume that your application works correctly for 1 user, but aim to see if it functions under a heavy user load. Load tests are headless because simulating thousands of users with an interactive UI is not practical. By being headless, a single load agent machine can simulate hundreds or thousands of users. VS load tests are the equivalent of using HP LoadRunner or JMeter to drive virtual user load.

结论功能测试和性能测试是两种截然不同的类型，具有不同的策略和流程.在给定的项目中，您可能有数百个自动化功能测试(例如编码的 ui)，但只有数十个自动化性能测试.您有更多的功能测试，因为您正在与业务需求相关的许多不同场景中测试您的应用程序.而在性能测试中，您可以选择最常用的前十个事务并在负载下运行它们.

Conclusion Functional and performance testing are two distinct types, with different strategies and processes. On a given project, you might have hundreds of automated functional tests (coded ui, for example), but only dozens of automated performance tests. You have so many more functional tests because you are testing your app in many different scenarios relative to your business requirements. Whereas with performance tests, you take your top dozen most commonly used transactions and run them under load.

这篇关于VS2010 编码 UI 测试与 Web 性能测试(有何不同??)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！