Visual Studio 2010 Testing for Developers - from DevExpress webinar on 2/24/2011.

1. Visual Studio 2010 Testing for Developers Steve Lange Developer Technology Specialist Developer Platform & Evangelism Microsoft | Denver, CO

2. Agenda Testing Isn’t Just For Testers Quality-Centric Tooling in VS 2010 Getting it Right the First Time Diagnosing Issues Time-Permitting Other Test-Centric Capabilities Web Performance Testing Coded UI Testing Other Concepts not Discussed Today

3. Before we start..

4. Testing Isn’t Just for Testers

5. Wouldn’t It Be Nice If.. .. code quality was optimized before moving to QA? .. QA could file more rich & actionable bugs? .. Developers had tooling to more quickly debug issues?

6. Developer-Tester Ping Pong Tester Developer “I did the same thing and it works. Are you sure you did that?” “Let me come down to your desk and see what you did.” “It works on my machine. What’s different?” “How much RAM do you have?” “What do you want to know?” “What OS are you running?” “What steps did you take?” “I did this, then this.” “Yes, don’t you believe me?” “I found a bug.” “Windows 7.” “Four gigs.” A lot of wasted effort due to poor collaboration & integration

7. Quality-Centric Tooling for Developers Getting it Right the First Time Code Analysis & Metrics Test Impact Analysis Diagnosing Issues IntelliTrace Performance Profiling

8. Code Analysis Static “grammar” checking of your code Check for quality while you write it Uses “rule sets” & categories Naming conventions Non-secure data access Design Issues Accessibility Localization Can be run automatically as part of local build Create work item in TFS

9. Code Analysis Rule Sets

10. Code Metrics Measures complexity & maintainability of managed code Generated code is ignored User can’t change it For single project or entire solution Export to Excel Create work item in TFS

11. Understanding Code Metrics Values

12. Demo Code Analysis & Code Metrics

13. Test Impact Analysis Identifies tests impacted by code changes Reduces test time Compares code changes with coverage data

14. Demo Test Impact Analysis

15. Diagnosing Issues

16. Debug is Fine, But.. Forward-only Set breakpoint, run, pause, reset breakpoint, run again.

17. IntelliTrace DVR for your code Reduce “no repro” bugs Bridge gap between test and development Dynamically instruments code Records program execution flow Records program data (parameters & return values) Direct code version navigation when using symbols

18. Demo IntelliTrace

19. Performance Profiling Performance session capture Perf counter utilization (CPU, RAM, etc.) Concurrency Tier interaction (SQL Server) Client-side Javascript Provides Comprehensive data & reports Hot Path Benchmark comparison

20. Profiling Reports

21. Profiling Reports

22. Demo Performance Profiling

23. Is There Time?

24. Web Performance Tests “Headless” browser testing Test communication at protocol level Measures request/response times, server codes, etc. Add validations & extractions Can be data-driven

25. Demo Web Performance Tests

26. Coded UI Tests Functional UI Testing, in .NET code Validate behavior of application Record actions & turn into code, or use existing recordings from a test case

27. Demo Coded UI Tests

28. Other Testing Capabilities Not Discussed Today Test Case Management & Automation Load Testing

29. To Wrap Up Visual Studio 2010 provides.. Tools for not diagnosing existing issues, but mitigating potential ones Capabilities that cross the entire spectrum of testing, from the generalist tester to the true developer.

30. Questions?

31. Steve Lange Developer Technology Specialist Microsoft | Denver, CO stevenl@microsoft.com blogs.msdn.com/slange @stevelange