VS2010 Coded UI Tests vs Web Performance Test (what's the difference?)

Question

Playing with them for a couple of hours.

You use a coded interface test to record some actions and validate them through statements.

You use a web performance test to record some activities and validate them with validation / check tests ... basically the same thing ... then you can optionally convert to code, for example, in Coded UI Tests

But it looks like you can add the WEB PERFORMACE TEST test to loadTest ...

But arent they both pretty much the same thing? What? I do not understand?? Why not let the coded user interface be tested inside the load test?

Answer 1

I think this article is of great importance for this discussion.

CodedUI Tests - Coded user interface tests designed for automated functional testing. These tests will simulate user interaction with the user interface, such as button presses and text input. Coded user interface tests require an interactive desktop environment because they actually interact with the windows and objects of your application. The coded user interface tests in VS2010 are equivalent to using something like HP QuickTest Pro or Selenium to manage your automatic functional regression tests.

Web Performance Testing - Web testing has much more than GUI testing. Web performance tests are used to test the functionality and performance of a web page, web application, website, web services, and combinations thereof. Web performance testing can be created by recording HTTP requests and events while interacting with a web application. The record also records call forwarding, verification, viewing status information, authentication and all other actions. It can be classified in two ways, which include simple Web performance tests and website performance tests.

Simple Web performance tests generate and run a recording test using a series of valid event streams. After starting the test, there will be no intervention, and this is not conditional.

Coded Web performance tests are more complex, but provide more flexibility. These types of tests are used for conditional execution based on values. Encoded web tests can be created manually or generated from a Web Performance Test record.

Downloading Tests - Download the tests and run the application at the HTTP level. These tests simulate the interaction of mute users with your application server by directly sending HTTP requests without a user interface. Typically, load tests assume that your application works correctly for 1 user, but you need to check if it works under the load of a large user. Load tests are headless because simulating thousands of users with an interactive interface is not practical. Being headless, a single boot agent machine can simulate hundreds or thousands of users. VS load tests are equivalent to using HP LoadRunner or JMeter to provide virtual user loading.

Conclusion Functional testing and performance testing are two different types, with different strategies and processes. In this project, you can have hundreds of automated functional tests (for example, encoded ui), but only dozens of automated performance tests. You have so many functional tests because you are testing your application in many different scenarios compared to your business requirements. While in performance tests, you take the best of the most frequently used transactions and run them under load.

Answer 2

Coded user interface tests are designed for automated functional testing. These tests will simulate user interaction with the user interface, such as button presses and text input. Coded user interface tests require an interactive desktop environment because they actually interact with the windows and objects of your application. The coded user interface tests in VS2010 are equivalent to using something like HP QuickTest Pro or Selenium to manage your automatic functional regression tests.

Download the test record and run the application at the HTTP level. These tests simulate the interaction of mute users with your application server by directly sending HTTP requests without a user interface. Typically, load tests assume that your application works correctly for 1 user, but you need to check if it works under the load of a large user. Load tests are headless because simulating thousands of users with an interactive interface is not practical. Being headless, a single boot agent machine can simulate hundreds or thousands of users. VS load tests are equivalent to using HP LoadRunner or JMeter to provide virtual user loading.

Functional testing and performance testing are two different types, with different strategies and processes. In this project, you can have hundreds of automated functional tests (for example, encoded ui), but only dozens of automated performance tests. You have so many functional tests because you are testing your application in many different scenarios compared to your business requirements. While in performance tests, you take the best of the most frequently used transactions and run them under load.

Answer 3

Coded UI tests are new by 2010. They confirm the actual user interface (placement in the DOM, visibility, etc.) of the application, and the other is not. Web performance testing verifies the HTTP / HTTPS connection to the server.

This suggests functional testing of the user interface and shows the use of the coded interface test.

http://channel9.msdn.com/shows/10-4/10-4-Episode-18-Functional-UI-Testing/

Answer 4

Good news, from VS2012 you can add an encoded ui test to the Load Test.

http://msdn.microsoft.com/en-us/library/ff468125.aspx