Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Practical alm testing


Published on

Published in: Technology, Education
  • Be the first to comment

Practical alm testing

  1. 1. Practical ALM:expanding testing horizons with VS2010 and TFS2010<br />Igor Moochnick<br />Principal<br />IgorShare Consulting<br /><br />Blog:<br />
  2. 2. ALM – Application Lifecycle Management<br />
  3. 3. Test Center<br />Define test plans<br />Test suites<br />Static based suites<br />Requirement based suites<br />Query based suites<br />Manage tests<br />Execute tests<br />Record tests<br />
  4. 4. CodedUI<br />demo <br />
  5. 5. CodedUI Training<br />video<br />Video 1: Getting Started<br />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<br />Video 2: Maintenance and Debugging<br />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)<br />Video 3: Hand-Coding<br />Advanced topics of hand-coding automated test instead of using recorder and talks about the best practices for creating large Coded UI Test suites<br />
  6. 6. CodedUI support matrix<br />
  7. 7. CodedUI Best Practices<br />Use the Coded UI Test Builder whenever possible.<br />Do not modify the UIMap.designer.cs file directly - file will be overwritten.<br />Create your test as a sequence of recorded methods<br />Each recorded method should act on a single page, form, or dialog box. <br />Use a meaningful method names instead of the default - helps identify the purpose of the method.<br />When possible, limit each recorded method to fewer than 10 actions - easier to replace a method if the UI changes.<br />Create each assertion using the Coded UI Test Builder<br />If the UI changes, re-record affected the test or the assertion methods<br />Create a separate UIMap file for each module in your application under test. <br />In the tested application - use meaningful names for the UI controls<br />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.<br />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.<br />
  8. 8. Builds<br />
  9. 9. Associate Test Plans with Builds<br />
  10. 10. Architecture Validation<br />demo <br /><ul><li>Define ahead
  11. 11. Reverse Engineer
  12. 12. During the build or check-in validation</li></li></ul><li>Code Complexity Analysis<br />demo <br />Enable on build<br />Enable on check-in (team settings, check-in policy)<br />
  13. 13. Gated check-in<br />demo <br />
  14. 14. Code Test Impact Analysis<br />demo <br />
  15. 15. Test Impact Analysis<br />demo <br />Show calling tests<br />Show impacted tests<br />
  16. 16. Code Coverage<br />demo <br />
  17. 17. PEX<br />demo <br />Generates UnitTests for you<br />
  18. 18. Lab management<br />Create test configurations<br />Save testing VMs snapshots and attach to the bug description<br />Load on demand any pre-defined environments, including pre-specified multi-VM states<br />Creation of Build-Deploy-Test workflow Create Lab Environments<br />Query based suite for BVT<br />
  19. 19.
  20. 20. Load Testing<br />
  21. 21. Spec Explorer<br />
  22. 22. Contracts<br />usingSystem.Diagnostics.Contracts;<br />// ...<br />public void SampleMethod(Item[] aCollection, ref Decimal total)<br />{ // Pre-ConditionsCodeContract.Requires(total >=0);CodeContract.Requires(aCollection!= null);// ...// PostconditionsCodeContract.Ensures(total >= CodeContract.OldValue(total)); <br />}<br />
  23. 23. Additional Links<br />VS2010 demos for testing tools – MTLM, CUIT and related features<br />Content Index for Coded UI Test<br />
  24. 24. Apendix<br />
  25. 25. Ideas<br />Use the product usage reports from Dotfuscator CE to decide what tests to run<br />
  26. 26. Test Planning<br />
  27. 27. Test Architecture – Architecture Validation<br />
  28. 28. Test Case Management<br />
  29. 29. Test Guidance<br />
  30. 30. Lab Management<br />
  31. 31. Scrum Guide<br />
  32. 32. Practical ALM:expanding testing horizons with VS2010 and TFS2010<br />Igor Moochnick<br />Principal<br />IgorShare Consulting<br /><br />Blog:<br />