- QTP Tutorial
- QTP - Home
- QTP - Introduction
- QTP - Test Automation
- QTP - Environment Setup
- QTP - Record and Play Back
- QTP - Object Repository
- QTP - Actions
- QTP - DataTables
- QTP - Checkpoints
- QTP - Synchronization
- QTP - Smart Identification
- QTP - Debugging
- QTP - Error Handling
- QTP - Recovery Scenarios
- QTP - Environment Variables
- QTP - Library Files
- QTP - Test Results
- QTP - GUI Objects
- QTP - Virtual Objects
- QTP - Accessing Databases
- QTP - Working with XML
- QTP - Descriptive Programming
- QTP - Automation Object Model
- QTP - Frameworks
- QTP - Designing a Framework
- QTP Useful Resources
- QTP - Questions and Answers
- QTP - Quick Guide
- QTP - Useful Resources
- QTP - Discussion
- Selected Reading
- UPSC IAS Exams Notes
- Developer's Best Practices
- Questions and Answers
- Effective Resume Writing
- HR Interview Questions
- Computer Glossary
- Who is Who
QTP - Frameworks
A Framework defines a set of guidelines/best practices that enforces a set of standards, which makes it easy to use for the end users to work with. There are different types of automation frameworks and the most common ones are listed below −
- Keyword-Driven Framework
- Data-Driven Framework
- Hybrid Framework
Keyword driven testing is a type of functional automation testing framework which is also known as table-driven testing or action word based testing.
In Keyword-driven testing, we use a table format, usually a spreadsheet, to define keywords or action words for each function that we would like to execute.
It is best suited for novice or a non-technical tester.
Enables writing tests in a more abstract manner using this approach.
Keyword driven testing allows automation to be started earlier in the SDLC even before a stable build is delivered for testing.
There is a high degree of reusability.
Initial investment in developing the keywords and its related functionalities might take longer.
It might act as a restriction to the technically abled testers.
Data Driven Framework
Data-driven testing is creation of test scripts where test data and/or output values are read from data files instead of using the same hard-coded values each time the test runs. This way, the testers can test how the application handles various inputs effectively. It can be any of the following data files −
- Excel files
- ADO objects
- CSV files
- ODBC sources
Data Driven Testing can be best understood by the following diagram −
- Data driven framework results in less amount of code
- Offers greater flexibility for maintaining and fixing the scripting issues
- Test Data can be developed
- Each script needs to be different to understand different sets of data.
Hybrid Framework is a combination of Keyword driven and data Driven framework that can be best described using the following flow diagram.
Following are the parameters one should take into account while developing the framework. The affects factors are listed below −
Framework files should support versioning controlling software such as SVN, CVS, MS Source Control
Framework should support executing the scripts in different environments viz- QA, SAT, DEV
Upon Object changes, scripts should execute with minimal changes.
Framework should configure itself and take care of prerequisite such as creating folders/databases.
Framework should have robust reporting structure so that issues in the script/application can be easily spotted
Framework should have greater flexibility so that it should be easy to use
Framework should follow coding standards so that files, functions, and history of changes are maintained correctly.
In the next chapter, we will learn how to design a simple framework.