Web and load testing with Visual Studio 2010 Ultimate


Published on

Visual Studio 2010 Ultimate also gives you access to advanced web and load testing features that help you ensure that whatever application you are building it is ready for the most demanding uses. The Web and Load testing capabilities of Visual Studio 2010 Ultimate help you ensure that whatever application you are building it is ready for whatever scenarios your organization can envisage taking you one step closer to knowing your application is ready for prime time.

Published in: Technology
1 Comment
  • Hi,
    Can you please share the soft copy of this PPT?

    Email - prabhu.somasundaram@gmail.com
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Talk about web performance tests.Use them as scripts inside load testsThese are not fit for testing the user interface. They are run at the HTTP protocol level by test agent and no browser is involved.Renamed from Web Test in Visual Studio 2008Talk about Challenges faced…. During real world scenariosWriting better test scripts.
  • You create a Web Test By recording a particular usage scenario for your application using Web Test Recorder.Web test recorder creates a Web Test, Analyzes the requests and responses for dynamic parameters and correlates requests with each other.Web test recorder also creates a log file for recording which can be used to fine tune/customize the web performance test.Once you have customized the web test you can run it using visual studio test agent by using a visual studio ide or MSTest.exe from command lineThe Web Test engine sends HTTP Requests to the sever and recieces the HTTP response which it saves in a Web Test result log file.You can load Request/Response in Visual Studio 2010 from the log file to view the results.Key Considerations:-Sends and receives data at the HTTP layer. Does NOT run a browser. Does NOT run java script. Does NOT host ActiveX controls or plugins. Thus they can Web Tests Can Succeed Even Though It Appears They Failed
  • Extraction rules are useful when you have a piece of data from one page that is needed on another page. For example, extraction rules can be used to extract information from responses, such as http header, attribute value, form field, hidden field, text, and regular expression. The extracted values can then be added to the Web test context for future usageValidation rules are useful when you want to verify that expected data, such as http tag, attribute, request time and text, appear in the responses or perform Web functional testingThe Web test plug-in is run one time for every test iteration. Code in the PreWebTest handler will be called before the Web test starts issuing requests. Code in the PostWebTest handler will be called after the Web test completes. For example, the cleanup code can be inserted here.Web request plug-ins provide a way for you to isolate code outside the main individual requests in your Web test. A request plug-in allows you to call code as each request is run in a Web test. Code in the PreRequestHandler function will be called before a request is issued. For example, you can skip a request if certain condition is met. Code in the PostRequestHandler function can be used to retrieve information from response pages.More informationhttp://msdn2.microsoft.com/en-us/library/ms404703(VS.80).aspxMore Informationhttp://msdn2.microsoft.com/en-us/library/ms404670(VS.80).aspx
  • ControllerThe controller provides a general architecture for running tests, and includes special features for running load tests. The controller sends the load test to all agents and waits until all the agents have initialized the test. When all agents are ready, the controller sends a message to the agents to start the test.You can configure the controller to select agents based on the properties of the agent, for example, the operating system installed on the agent. You do this on the Controller and Agents tab of the run configuration file. For more information, see How to: Specify a Test Run Configuration.AgentThe agent runs a service that listens for requests from the controller to start a new test. When a request is received, the agent service starts a process on which to run the tests. Each agent runs the same load test.Agents are assigned a weight by the administrator, and load is distributed according to an agent’s weighting. For example, if agent 1 has a weighting of 30, and agent 2 has a weighting of 70, and the load is set to 1000 users, then agent 1 simulates 300 virtual users while agent 2 simulates 700 virtual users. For more information about how to assign a weight to an agent, see How to: Administer a Rig.The agent takes as input a set of tests and a set of simulation parameters. A key concept in Visual Studio Team Edition for Testers is that tests are independent of the computer on which they are run.
  • The possible reasons for this are the counter category is not installed on the computer, the user account does have permission to collect the counters, or a firewall issueIt happens because this rule depends on a counter which was not collected for the sample period the error occurred.
  • Web and load testing with Visual Studio 2010 Ultimate

    1. 1. Performance Testing your applications with VS 2010 Ultimate<br />Abhimanyu Singhal<br />Co-Founder<br />iMentor Knowledge Services<br />
    2. 2. Abhimanyu Singhal<br />Background<br />First Laid Hands on computers in 1994, been a geek for quite some time<br />Spent Last 15 Years in working on Different Projects, Technologies and development platforms<br />Currently<br />Helping companies scale applications developed on different platforms<br />Co-Founder and Lead Consultant for iMentor Knowledge Services<br />Provide High-End Technical Training and Consultancy<br />
    3. 3. Objectives<br />Plan and Design Tests<br />Execute Tests<br />Analyze Results and Reports<br />
    4. 4. Demo Web Application<br />Home<br />About Us<br />Login<br />Register<br />
    5. 5. Performance Testing<br />Challenges<br />Writing better scripts<br />Taking care of Requests and Dependent requests<br />Writing scripts for key usage scenarios and there variances<br />Data<br />Navigation Paths<br />Determining Relative Distribution and Simulating the same<br />Think Times<br />Test Run Mix<br />Load Test Time Duration<br />User abandonment<br />Target Load Levels<br />Quantifying volume of application usage<br />
    6. 6. Performance Testing - Execution<br />Challenges<br />Simulating New Production Environment<br />Setting up Test Rigs and Distributing Load among machines<br />Validating Test Runs<br />Understanding the reports and which information to look for?<br />Math Intensive<br />
    7. 7. Web Performance Tests<br />Tests the functionality of Web Application/Web Service for:-<br />Performance<br />Any Other Validation you specify<br />Not fit for testing user interfaces<br />Use them as scripts in load tests to model user actions<br />
    8. 8. Web Performance Tests (Execution)<br />
    9. 9. Demo – Creating and Running Web Performance Test<br />
    10. 10. Web Performance Test Components<br />Request<br />Dependent Request<br />Extraction Rule<br />Validation Rule<br />Web Test Plug-In<br />Web Request Plug-in<br />Comments<br />Context Parameters<br />Date Sources<br />
    11. 11. Coded Web Performance Test<br />
    12. 12. Load Test<br />Load Testing Applications<br />Stress Testing Applications<br />Smoke Tests<br />Spike Tests<br />Can be used for Web Applications<br />Can also be used for Internal Application Components<br />
    13. 13. Load Simulation Architecture<br />Client 1<br />VS 2010<br />Client 2<br />MTM<br />Test Rig 2<br />Test Rig 1<br />Controller 1<br />Controller 2<br />Agent 1<br />Agent 2<br />Agent 3<br />Agent 4<br />Agent 5<br />Agent6<br />
    14. 14. How machines in test rig communicate<br />
    15. 15. Demo Creating and Running Load Tests<br />
    16. 16. Key Measures I watch for<br />% CPU Usage<br />Requests Per Second<br />Request Queue Length<br />Total Bytes in Heap<br />
    17. 17. Considerations for running load Tests<br />Load pattern<br />Connection Model<br />Sample rate and data collection<br />Think time<br />Response time goals<br />Percentage of new users<br />Enabling SQL tracing<br />Maintaining an appropriate number of agents<br />
    18. 18. Common Issues with counter collection<br />LoadTestCounterCategoryNotFoundException<br />Could not find dependent counter needed to apply threshold rule<br />
    19. 19. Resources<br />Performance Testing Guidance for Web Applications @ Microsoft Patterns and Practices<br />http://msdn.microsoft.com/en-us/library/bb924375.aspx<br />Visual Studio 2010 Online<br />http://www.microsoft.com/visualstudio/en-us<br />Microsoft Developer Network<br />Resource Links for Performance Testing<br />http://www.imentor.co.in/blog/?p=35<br />
    20. 20. Thank you and Q.A.<br />Please post your questions<br />You can also send in your questions to <br />abhimanyu@imentor.co.in<br />