1. Practical ALM:expanding testing horizons with VS2010 and TFS2010 Igor Moochnick Principal IgorShare Consulting igor@igorshare.com Blog: www.igorshare.com/blog

2. ALM – Application Lifecycle Management

3. Test Center Define test plans Test suites Static based suites Requirement based suites Query based suites Manage tests Execute tests Record tests

4. CodedUI demo

5. CodedUI Training video Video 1: Getting Started Getting started on creating Coded UI Test using Coded UI Test Builder, adding assertions and providing an overview of contents/structure of Coded UI Test Video 2: Maintenance and Debugging Detailed look at contents/structure of Coded UI Test, data driving of a Coded UI Test, resolving failures due to changes in Application under Test (AuT) Video 3: Hand-Coding Advanced topics of hand-coding automated test instead of using recorder and talks about the best practices for creating large Coded UI Test suites

6. CodedUI support matrix

7. CodedUI Best Practices Use the Coded UI Test Builder whenever possible. Do not modify the UIMap.designer.cs file directly - file will be overwritten. Create your test as a sequence of recorded methods Each recorded method should act on a single page, form, or dialog box. Use a meaningful method names instead of the default - helps identify the purpose of the method. When possible, limit each recorded method to fewer than 10 actions - easier to replace a method if the UI changes. Create each assertion using the Coded UI Test Builder If the UI changes, re-record affected the test or the assertion methods Create a separate UIMap file for each module in your application under test. In the tested application - use meaningful names for the UI controls Assertions by coding with the API - create a method for each assertion in the part of the UIMap class in the UIMap.cs. Call this method from your test method to execute the assertion. Directly coding with the API - use the properties and methods in the classes generated in the UIMap.Designer.cs in your code as much as you can. These classes will make your work easier, more reliable, and will help you be more productive.

8. Builds

9. Associate Test Plans with Builds

11. Reverse Engineer

13. Gated check-in demo

14. Code Test Impact Analysis demo

15. Test Impact Analysis demo Show calling tests Show impacted tests

16. Code Coverage demo

17. PEX demo Generates UnitTests for you

18. Lab management Create test configurations Save testing VMs snapshots and attach to the bug description Load on demand any pre-defined environments, including pre-specified multi-VM states Creation of Build-Deploy-Test workflow Create Lab Environments Query based suite for BVT

20. Load Testing

21. Spec Explorer

22. Contracts usingSystem.Diagnostics.Contracts; // ... public void SampleMethod(Item[] aCollection, ref Decimal total) { // Pre-ConditionsCodeContract.Requires(total >=0);CodeContract.Requires(aCollection!= null);// ...// PostconditionsCodeContract.Ensures(total >= CodeContract.OldValue(total)); }

23. Additional Links VS2010 demos for testing tools – MTLM, CUIT and related features http://blogs.msdn.com/b/anutthara/archive/2009/12/21/vs2010-demos-for-testing-tools-mtlm-cuit-and-related-features.aspx Content Index for Coded UI Testhttp://blogs.msdn.com/b/mathew_aniyan/archive/2010/02/11/content-index-for-coded-ui-test.aspx

24. Apendix

25. Ideas Use the product usage reports from Dotfuscator CE to decide what tests to run

26. Test Planning

27. Test Architecture – Architecture Validation

28. Test Case Management

29. Test Guidance

30. Lab Management

31. Scrum Guide

32. Practical ALM:expanding testing horizons with VS2010 and TFS2010 Igor Moochnick Principal IgorShare Consulting igor@igorshare.com Blog: www.igorshare.com/blog