1. Building More Reliable And Better Performing Web Applications With Visual Studio 2005 Team System Gabriel Marius TLN312 Program Manager Microsoft Corporation

2. 2 A Real World Problems: A Web Developer at Work

3. 3 Review: Work Items, Bugs, etc Bug was logged from a customer and followed up by the Test team Load Test Result was attached to the bug Developer can review the Testers findings Developer can reproduce the failure Other artifacts can also be attached More test results Standard files (Specs, Images, etc) Static Analysis Results

4. 4 Review: Code Coverage & Testing Tests to check the state of our code Unit Tests Web Tests Load Tests Code Coverage to give us an idea of what Developer code was touched by test cases Assembly Level Class Level Method Level

5. 5 Review: Profiling Managed and UnManaged Code Sampling Profiler High-level data Don’t need source code Instrumentation Profiling Low-level data Need source code and build Integrated with Testing

6. 6 Review: Web & Load Testing Web and Load tests written via Visual Studio 2005 Team System Web Tests can be recorded or converted into code Records the HTTP traffic C#, VB.NET, etc. Load Tests are containers of other test cases along with metadata about the Load Session Contains most types of tests Does not support Manual Tests

7. 7 Review: Data-Driven Tests Can bind a Test Case to a Database Each Data row becomes a test case One Test Case associated with 1000 rows becomes 1001 test cases 1 for the overall process 1000 for the individual rows Test can be changed by editing the rows of the database without changing the code

8. 8 Review: Integrated Debugging Integrated debugging allowed us to walk into our test case and into are development code In the context of data-driven tests, we can see each execution of the test case with the different data elements Use standard debug windows as needed See variables and memory as we test Errors and debug information can be shared via work items with the rest of the team

9. 9 Review: Code Analysis & Team Policy Team Policy prevented us from checking in without Code Analysis Other actions can be part of Team Policy Execution of Test Lists Code Analysis found a security issue Rules are extensible Out-of-the-Box, Code Analysis is powerful SecurityPerformanceGlobalizationMore…

10. 10 The Web Dev Day: Viewed detail bug information with TFS integration Verified the Build State with tests Verified Code Coverage and identified test issues Found a Performance issue in our Beta code Verified Account Scenarios for Beta Functionality Identified a Security Issue Checked our Code in, Shared our Status

11. © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.