Hybrid Framework in Automation (Part-1)

We started our journey to grasp the concept of framework in automation using keyworddriven approach, today we are going to shape our existing code into a more versatile form known as Hybrid framework.

Note:- Please read our post on Keyword Driven framework before starting with Hybrid concept.

Follow us on Facebook for more updates and learning!!!

Moving from Keyword to Hybrid Framework in UFT
Moving from Keyword to Hybrid Framework

What is Hybrid Framework?
In laymen terms it is the combination of all the frameworks (Keyword + Data + Modular), which takes the best of all of the available frameworks to create a robust approach for automation.

Thus hybrid approach takes the features of all the available frameworks plus the user specific modification to achieve an easier route for automation testing of the application.

Note: – There is no standard definition or guidelines for Hybrid approach and its components are the vision of the automation tester to make automation task least maintainable, easy to implement and adapt.

Steps for using the above framework:-
Note: – Similar to our keyword driven framework code, after downloading the code -> Extract the zip files -> open the “HybirdApproach” folder -> paste it inside c:Temp -> open the Driver script in UFT/QTP.
Folder structure Hybrid Framework
Folder structure of Framework

Before Run:-

Enable or disable the required features:-
  1.    Test Properties change set “Screenshot ” value to “Yes”, incase we want to capture error screenshots
  2. Similarly set “Email” value to “Yes”, to send test case run email with Pass/Fail status

Change the TestCase property to the required test sheet name of the test case.

Test Properties in UFT
Properties tab in UFT

After Run:-
Reset the counter in the excel to the starting data row, else it would always run for the last set of test data in “Data” tab of excel sheet.
Keyword sheet in Hybrid Framework
Reset the counter to 2 

What changes we need to do for using the framework for different test case?
To achieve this we need to do few basic changes:-

  • Simply save the given test case with the required new test case name say “TC_02_Search”
  • Input parameters:- change the value of “TestCase” to the required test case sheet say “TC_02_Search” and we are ready to run.

We learned the implementation part of our Hybrid Framework.
Hope You are able to successfully execute the test cases using this approach.
Please share your feedback or queries as comments below (further You can connect with us using 

In our next post we are going to discuss how we converted our Keyword driven framework to Hybrid Framework.

One reply on “Hybrid Framework in Automation (Part-1)”

Leave a Reply

Your email address will not be published. Required fields are marked *