Typical Architecture of Automation Frameworks
An Automation Framework primarily comprises of elements like:
A) Function Library
A) Function Library:
Every application consists of following two types of function libraries
1) Containing common functions that are not dependent on the application functions.
2) Containing functions, which are specific, the application.
The script designer strives to utilize the common functions, which are independent of the application, to the maximum possible extent. However there is no hard & fast rule to always use common functions only. Whenever there is absolute necessity of using some functions, which are essential for the application, the same are created on the spot & are stored in the concerned function library.
“ExecuteScenarioFile” is a function present in our common function library & is called from the Driver Script or from outside the function library. This function is used for accessing the keywords, various objects and all other parameters from the Scenario File. This is also used to call other relevant functions as well from the function library.
The function library files with (*.vbs) extension are stored in the Function Library folder.
B) Object Repository:
The MS Access database files with (*.mdb) extension are stored in the Database folder.
D) Application Scenario Files:
The subject matter experts (SME’s) who usually don’t have much of programming knowledge are able to easily use these application scenario files for creating automated tests by making quick selection of keywords from the dropdown lists.
We can save tremendous amount of automation effort by creating maximum number of common which can be reused again & again thereby getting the maximum benefit.
The application scenario files with (*.xls) extension are stored in the application folder corresponding to the particular application.
E) Sequence File:
1) Name of Application Scenario file
Every application carries a “Run” or “Ignore” flag specifying the application scenario being executed. This sequence file in the form of spreadsheet is used by the Initialization VB Script uses & decides as to which application & which scenario is to be executed, for getting the information on the concerned Application Scenario file & for doing the initialization settings for the application.
The Sequence File with (*.xls) extension are stored directly in the root folder.
F) Initialization VB Script:
It carries out the following settings for the Driver Script.
1) Setting the Work Area according to user input.
Once the above settings are completed, Initialization VB Script launches the Driver Script in read only mode, & makes it ready for execution by the user. Thereafter the Driver Script takes over the entire control.
The Initialization VB Script with (*.vbs) extension are stored directly under the root folder.
G) Driver Script:
These Driver Scripts call the “ExecuteScenarioFile” function for accessing the keywords, various objects and all other parameters from the Scenario File and making calls to suitable functions in the function library.
The Driver Scripts are stored directly under the root folder.
H) Test Case List File:
These Test Case List Files are stored directly under the root folder.
Many more articles on Automation Frameworks are available at: