W13 May 14, 2003 3:15 PM B UILDING A F LEXIBLE A UTOMATED T ESTING - PDF document

BIO PRESENTATION W13 May 14, 2003 3:15 PM B UILDING A F LEXIBLE A UTOMATED T ESTING A RCHITECTURE Jack Harris Washington Mutual Bank International Conference On Software Testing Analysis & Review May 12-16, 2003 Orlando, FL USA

Jack Harris Jack Harris is currently a Manager in the Technology Solutions Group of Washington Mutual Bank, located in Irvine California. Jack has been with the bank since August of 2001. During that time he has led a dedicated project team of developers and test analysts in bringing test automation to the Home Loans and Insurance Services group of Washington Mutual. Additionally, he has responsibility for leading the Program Management Office, Test Management, and Technical Services organizations. Prior to 2001 Jack was employed by Epicor Software Corporation (formerly Platinum Software Corporation) also located in Irvine, California. He held many positions over nearly a 7 year period from Test Analyst, Team Lead, Manager and finally Director of Quality Assurance and Documentation for the Corporation. He was responsible for developing an automated testing solution for Epicor while also working with multiple divisions and vendors to improve the quality of their software products. During this period Jack won two President’s awards given annually for his research and development of automated software testing tools. Jack was also selected to participate in the Leadership and Management Program for Technology Professionals (LAMP) at the University of California, at Irvine where he was selected by his peers to be the primary speaker for the graduating class. Previously Jack worked for 30 years for Fortune 500 companies in the Aerospace and Semiconductor industries located in Southern California. Jack held a variety of both Management and Technical positions in the Finance, Accounting, and IT organizations. Jack graduated from Fullerton College.

Optis Test Automation Project Slide Jack Harris May 14, 2003

Optis Test Automation • Test Automation Strategy – Build test automation engine – Make the testing tools data driven – Segregate test scripts from the data – Build the tools with flexible components – Invest in coding a library of proven functions – Create standard test scripting template to enforce scripting standards – Developers code, SME’s test Slide 2

Test Automation High Level Component Diagram Screen Scraper XML Excel Test Optis Application Script XML Application Applications (VB) Files Reader Convert to XML Map Writer Builder Map Under Test C++ Files Reader HTML Files Reader Script Reader Test Cycle WinRunner Test Software Manager Excel User Interface Test Library Test Execution Engine Scripts Functions Error Handling Recovery Log & Test User Report File Script Application Under Test Operator Reader Viewer Create Test Scripts Automation Commands Results Test Automation Main Repository Slide 3

Map Library Third Party Software Slide 4

Optis Test Automation • Application Map for each Application Under Test – Batch process – parses code to identify windows, objects – Creates road map of what is being tested (object recognition method) – Produces XML output of each application under test (re-run after each drop) Screen Scraper .FRM (VB) Files Reader Converts to XML Applications under XML Application Map Writer Test PBL (PB) Files Reader HTML Files Reader Application Map Builder Slide 5

Optis Test Automation • Test Script Builder – Points to Application Map from prior step – Special Excel Workbook with embedded code – Does not require 3rd party tool installed to use – Sheet 1 used to Document Test/Environment – Sheet 2 used for Test Script Creation and data – Sheet 3 used for data creation as needed • works with any ODBC compliant data source Slide 6

Optis Test Automation Slide 7

Optis Test Automation Slide 8

Data Sheet Slide 9

Optis Test Automation • Test Engine – Compiles Excel based scripts into WinRunner language – Executes action words from scripts for each object in each window from WinRunner library function – Use Excel based scripts as utilities (log on/off etc.) – Same script can execute variable amounts of data – Eliminates need for redundant scripts – Reduces script maintenance Slide 10

Optis Test Automation Library Functions - Why they are important Library Functions CheckBox EditBox ListBox Custom Controls Slide 11

Optis Test Automation • Benefits of WinRunner Library Routines – Users can only pick valid actions for objects – Library functions can be tested individually and certified by object type – Object functions rarely change – Eliminates writing a program to test a program – When changes occur you modify function in one place, not every script! Slide 12

Library Routine For EditBox Slide 13

Application Map XML Slide 14

Optis Test Automation User Interface Slide 15

Automation Test Results Test Results Log: ---Unique log generated each time the script is run. ---Generated and stored in PDF format. ---Summarizes test id, environment and results data. Slide 16

Automation Test Results Execution and results of each test step are captured in detail and recorded. Failures are identified with a unique color. Slide 17

Automation Test Results Print screens capture the visual identification of the failure. Slide 18

Automation Test Results Summary information is captured and can be used to prepare statistical analysis. Slide 19