Making Automation Easy.

1. Westpac Banking Corporation ABN 33 007 457 141.
AUTOMATION FRAMEWORK
MAKING AUTOMATION EASIER
PRESENTATION BY: BEN NGO

2. Manual Test Cases….
Short on Staff
Short on Time
Budget..
or
Just lost….

3. Manual to Automation….
Need forAutomation Framework
 Increase testing scope
 Increase comfort level to go live
 Increase quality and productivity
 Increase testing abilities
 Increase reporting and manageability
Reduce Risk
Most Reliableand Repeatabletests
Reduce Execution Time
Easy andFast Tests (Smoke , Functional and RegressionTests)
Reduce Script Development Time
RapidDesignand Development
Low Maintenanceandyet High Quality and
Productivity Increase
Reduce Training
Time Saving and ResourceSaving

4. Automation Framework
What is an Automation Framework?
Automation Framework is a well-structured, planned, practiced and supported
environment for Automation Testing.
It’s a warehouse where automation testing process:
begins, executes and accumulates results.
Automation Framework uses established implementation such as initiation,
moderation, execution and finalization.
Automation Framework is a complete reference of the Automation Testing
Process: the structure, guidelines and implementation.
A comprehensive architecture to drive the complete test automation process.

5. Automation Framework

6. Automation Framework

7. Automation Framework

8. Tallyman

9. Manual >> Automation
Current testing process…
Manual Test Scripts Automation Test Scripts

10. Manual >> Automation
10’s to 100’s of test cases preforming same steps

11. Conversion >> Automation

12. COLLECTION OF MODULES
Module = QTP Action
• A Module is a test case or Action
• Package is a collection of modules
built together to test a particular
scenario. Depending on a particular
scenario the QA Team can
create/update a module to fit a test
scenario, insuring minimum script
development.

13. LIBRARY OF MODULES COLLECTION OF PACKAGES
(Test Scenarios)

14. Requirements are built into the
modules for later Reporting use.

15. Automation Checkpoints
Check Form Change
Check Data Change

16. Automation Checkpoints
Check Form Change
Check Data Change
Check Results

17. Automation Checkpoints

18. Automation Framework

19. Automation Framework

20. Automation Framework

21. DATA DRIVEN FRAMEWORK
Data driven depends on the individual application and the scenario under test.
A clear direction is needed to utilised and maintain the data to its full potential.
RANDOM GENERATED DATA
Benefit: Data creation, Minimize: Datatable size, data
scenarios, errors.
DATA INSERTION – (Global Database)
Benefit: only insert the data we need.
DATA INSERTION – (Hard Code within Module)
DATA-TABLE INSERTION
Each modules object has a relationship with the data table.
Benefit: test a particular scenario over many records sets
or define by customer.

22. Automation Framework

23. Automation Framework

24. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
ROAD MAP

25. Automation Framework

26. The 4th framework is reporting.
Reporting the Solution/Functional Requirements.
What Requirement has been tested.
Reporting the Results of a Package.
Reporting the overall Results by HTML.
The Test Results Reports are located in the
Framework folder structure.
Automation Framework
REQUIREMENT REPORT
PACKAGE & MODULES REPORT
HTML SUMMARY REPORT
HTML report will only be produce once a Package
is run by the Driver script.

27. Automation Framework