Is your application slow? Do you want to make sure it *isn’t* slow? Want to know what happens when a lot of people start using you application? Well, Visual Studio 2012’s Load Testing tools can help you out. Performance testing your application consists of four parts: 1) create the tests for each use case, 2) convert the use case tests into Load Tests, 3) run large-scale Load Tests simulating hundreds of users using a Load Test Rig, and 4) analyzing the results and fixing any problems. In this course, we’ll walk you through how to performance test your web-based or service-based application using the Visual Studio 2012 Load Testing and Performance Testing tools.
Benjamin Day is a consultant and trainer specializing in software development best practices using Microsoft-based technology. He is a Microsoft Visual Studio ALM MVP, a certified Scrum trainer via Scrum.org, and a speaker at conferences such as TechEd, DevTeach, and VSLive. He can be contacted via http://www.benday.com.
Introduction Hey everybody, how's it going? Welcome to Load Testing with Visual Studio 2012; this is the Introduction chapter. I'm Benjamin Day, owner of Benjamin Day Consulting, based out of Brookline, Massachusetts, and I've got a website and a blog www. benday. com and then if you feel like dropping me a line, my email address is benday@benday. com.
Web Performance Test Basics Hey everybody, this is Load Testing with Visual Studio 2012 and this is the Web Performance Test Basics section. If you are load testing an ASP. NET application that's got an HTML-based UI, well you're going to care about Web Performance Tests. And in this module I'm going to show you the Basics of Web Performance Tests. I'm going to talk about how to organize your Web Performance Test suite so that you can diagnose performance problems later on. Then we're going to talk about Validation Rules, Parameterization and Test Context, and Extraction, and how those things, Validation Rules, Parameterization, Test Context, and Extraction Rules can be used to make a smarter test.
Validation & Extraction Rules Hi, this is Load Testing with Visual Studio 2012 and this is the Validation & Extraction Rules module. So, quick review, how do you check that stuff is working? Validation Rules. How do you grab values in order to make a smarter test when you actually run your load test, your Web Performance Test? Well, you're going to use Extraction Rules. So in this module we're going to talk about the Out-of-the-box Validation Rules. We're also going to talk about the Out-of-the-box Extraction Rules. And then we're going to wrap up by creating our own Validation Rule and our own Extraction Rule.
Web Performance Tests Beyond the Basics This is the Load Testing with Visual Studio 2012: Web Performance Tests Beyond the Basics module. In this module we're going to talk about data-driven Web Performance Tests, how to handle security, Conditional and Loop Steps, and then also Web Test Plug-ins.
Load Test Basics Hey everybody, this is Load Testing with Visual Studio 2012 and this is the Load Test Basics section. So in this module, we're going to talk about ‘What is a Load Test' and then we're going to talk about what the ‘Pieces of a Load Test' are.
Load Test Beyond the Basics Hey everybody, how's it going? This is Load Testing with Visual Studio 2012 and this is the Load Test Beyond the Basics module. So in this module we're going to talk about Unit Tests as part of a Load Test. Then we're going to move onto Load Test Rigs, then I'm going to show you how to put Custom Performance Counters into your application so you can consume those Custom Performance Counters during the Load Test, and then finally I'm going to wrap up with a discussion about Coded UI Tests as part of a Load Test.
Case Study Alright, this is Load Testing with Visual Testing 2012 and this is the Case Study module. So in this module, we're going to be talking about stuff that happens in real life, so this is based on a true story, this is based on an actual customer engagement I did. And what we're going to be doing is we're going to be using Load Test to recreate problems in an application. This is not the real application, it's similar problems, but recreated in a different app. And then we're also going to find issues in the code using the Code Profiling tools.