1. Automation Testing Trainer: Eran Ruso

2. Training Agenda Automation Testing Introduction Microsoft Automation Testing Tool Box Coded UI Test and Unit Test Performance Testing

3. ALM

4. ALM (2)

5. QA Process

7. Tester’s Role In Agile Part of the team Little Planning and Test Case writing Plans only for the functionality in the Iteration/Spring Functional Testing happens in each Iteration/Spring System Testing and Performance Testing happens in last sprints

8. Automation Testing Definition Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions. Commonly, test automation involves automating a manual process already in place that uses a formalized testing process. (Wiki pedia)

9. When? Repeatable Test Scenarios Application Logic Level Unit Test the code Checking the Performance Data Driven Tests

10. When Not? Test Cases that are complicated for coding like image comparison Test Cases that we run only a small number of times Complex to code Premature parts in the Application (Constant Changes)

11. Why not Automate Everything? Low ROI (Return On Investment) Many times the Test Case is too complicated for a machine Most of the time the Look and Feel needs to be done by Human Tester

12. Project Manager Developer Tester Infrastructure Architect Solution Architect Business Stakeholder Motivation

13. Visual Studio 2010

14. VSTS 2010 Test Capabilities Coded UI Test Unit Testing Web Test Load Test Test Runner Test Case Management Virtual Lab Management Data Collectors (Historic Debugging, System Info.) Team Foundation Server with Reporting Manual Test

15. Cloud Development Office Development Windows Development New WPF Editor Customizable IDE Multi-core DevelopmentSilverlight Tools Web Development SharePoint Development Generate from Usage Static Code Analysis Database Deployment Code Metrics Database Unit Testing Test Data Generation Test Impact Analysis UI Test Automation Code Coverage Performance Profiling Database Change Mgmt Manual Testing Layer Diagram UML Modeling Load Test Testing Web Performance Testing Test Case Management IntelliTrace™ Architecture Explorer FFwd for Manual Test Logical Class Designer Test Manager Rich Actionable Bugs Testing Capabilities

16. Manage Test Cases

17. Code UI Test

18. Unit Test

19. Performance Testing LESS Approach: Less is the initials of: Load, Endurance, Stress and Spike Load Test: The test target is to check that the system can handle expected load of users doing different scenarios in the system. Endurance Test: The test target is to check the reliability of the system.

20. Performance Testing (2) Stress Test: The test target is to find the upper limit that the system can handle. Spike Test: The test target is to check that the system can handle spikes of users and can gracefully handle a sudden load in the system.

21. Performance Testing

22. Summary Automation Testing Introduction Microsoft Automation Testing Tool Box Coded UI Test and Unit Test Performance Testing

23. For More Information… Eran Ruso Blog: http://blogs.microsoft.co.il/blogs/eranruso/ http://blogs.microsoft.co.il/blogs/eranruso/ Team System Guides: http://tfsguides.codeplex.com/ http://tfsguides.codeplex.com/