Software Testing Workshop Regression Automation 11-Jul-08 COPYRIGHT NOTICE Copyright © 2008 Polaris Software Lab Limited All rights reserved. These materials are confidential and proprietary to Polaris and no part of these materials should be reproduced, published in any form by any means, electronic or mechanical including photocopy or any information storage or retrieval system nor should the materials be disclosed to third parties without the express written authorization of Polaris Software Lab Limited and University of Western Sydney.

Presentation path Metrics When to go for Automation Best Practices Automation Suite Development Checklists & Guidelines Benefits

3 Benefits of Test Automation Tangible benefits Speed and Accuracy Accessibility Accumulation Manageability Early Discovery of issues Repeatability Availability Intangible benefits of test automation Formal process Retention of customers/user trust Greater job satisfaction for Testers

4 Metrics for Automation Cycle Time Reduction Reduction in Test Execution Efforts Cost Savings > 98% Defect Unearthing Efficiency > 50% Productivity Increase

5 Automation Suite – When to go for it > 3 new builds/patches/fixes > 1 cycle Application Stable Run in Multiple hardware or software (including multi-OS or Multi-Browser) Application to meet SLAs? Repetitive tasks Test conditions re-used for IT/ST/UAT? More Test execution efforts More of business flow testing and less of usability testing

6 Automation Suite Development – Design, Build and Execute (Not just record and replay) Deliverables Automated Test Cases Test Automation Framework Documentation on Reusable Components Test Driver Scripts, Transaction Scripts Object repository and Library

Regression Automation Life Cycle Requirement Analysis Requirement Analysis 1 Design 2 Scripting 3 Execution 4 Reporting 5 Application Functionality Study Define Approach Design Framework Define Data Structure Spec Preparation Batch Execution Evidence Capturing Results Analysis Customized Reports Traceability User Manual Business Flow Common Functionality Reusable Components Parameterization Static Review Script Dry Run Re-execution on need basis

8 Best Practices Do not Record, Write code Follow scripting guidelines and naming conventions Follow object repository guidelines and naming conventions to identify objects easily Provide traceability in result logs Data driven tests with the flexibility to test for various business conditions on the same transaction Modular approach in test scripts with plug and play feature for future enhancement Use checklists for code review and Integration testing of Test scripts

9 Checklists & Guidelines Test automation Standards & Scripting Guidelines Integration testing checklist for testing the Test scripts Code review checklist for testing the Test scripts

Thank You COPYRIGHT NOTICE Copyright © 2008 Polaris Software Lab Limited All rights reserved. These materials are confidential and proprietary to Polaris and no part of these materials should be reproduced, published in any form by any means, electronic or mechanical including photocopy or any information storage or retrieval system nor should the materials be disclosed to third parties without the express written authorization of Polaris Software Lab Limited and University of Western Sydney. For further details Please contact:

*Cycle Time Reduction * Based on Data gathered from Polaris projects Cycle time reduced upto 94%

Reduction in test execution* * Based on Data gathered from Polaris projects Saving of 1840 man-days over a period of 1 year. The Graph shows the effort saved through Automation for various applications for the a year.

*Cost Reduction * Based on Data gathered from Polaris projects Cost reduced upto 94%