September 2009. QTP Automation Framework. Objective. Introduction to Automation Benefits of Automated Testing Automated Testing Process Introduction to QTP Framework Framework Structure Environment Supported. Manual Testing. Introduction to Automation. Drawbacks of Manual testing
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
QTP Automation Framework
Introduction to Automation
Drawbacks of Manual testing
- Manual testing is time-consuming and tedious.
- Requiring a heavy investment in human resources.
- Time constraints often make it impossible to manually
test every feature thoroughly before the application is
- Low reliability.
Benefits of Automation Testing
Automated testing involves three main steps
Data Driven Framework
Keyword Driven Framework
Hybrid = Keyword Driven + Data Driven
Hybrid = Modularity + Data Driven
Driver script is the single main script of the Driver Engine.
It iteratively traverses through the data of business scenario flow and calls the respective reusable scripts sequentially.
It also enables us to execute a reusable script any number of times in a particular data row of the variable test data sheet.
It also updates the database for execution results of a particular script run
There can be situations when you need to schedule your QTP scripts so that they can run when you are not present in front of your PC.
How QTP Stores Test Objects
ACTION - N
ACTION - N
Object Repository Contd.
Per Action Object Repository
Object Repository Contd.
Shared Object Repository
As per the scenarios which are in regression test suite, enter all the required test data into the excel file and save it in the test data folder which is specified in the framework.
When executing the scripts through QTP, we can get the HTML reports which is user friendly, where as running them through QC then auto generic reports.
Report on Test
Automation Framework Structure
Create Automation Scripts
Refactoring Manual Test Cases
Create Reusable Actions or User Defined Functions
Debug Automation Scripts
Test Report Analysis
Create Test Data
Upload Scripts & Mapped To QC
Identification of Reusable Components
Create Recovery Scenarios
Run The Automation Scripts from QC
Automation Work Flow
Formal selection of manual test cases for automation:
Decision will be been taken on what can be automated and what cannot be automated.
Selection of the test cases to be automated will be based on the business risk attached to each test
Tests that need to run once and those that need frequent human intervention are usually not worth the investment to automate and need not be considered for automation
Avoiding business scenarios where complex hardware is involved
Sample feasibility analysis report.
Feasibility Report for a Test Case
Following is the list of mandatory properties that will be used for UI elements:
Note : The list of mandatory properties for GUI elements may change if required.
Main Test Runner Structure
Main Test Runner
Environment File / Initialization file
User defined functions
Test Components of each Module
Test Data for the CR
Update Test Cases as per CR
New / Modify Master Scripts
User defined Functions
New / Modify QTP Test Scripts
Test Case Step Level Reporting
Suresh Kumar C
Designation and Address