I am sure everyone has read or heard about the types of automation framework and also used them in test automation with different type of tools.
But while doing the scripting most us also thought about why are we using it or is it helping me or am I getting benefit from it.
Most of the people uses the framework which is already created in there respective organization and project but while using it they were get frustrated or make changes according to there comfort.
While creating or updating the automation framework, we should think from 3 stages:
1. While scripting
2. While maintenance
2. While execution
Most of the times people only think from the perspective of scripting and never thinks from execution perspective like how much time it will take or whether the maintenance or parameter input will be easy for the users.
Most of the time we create the framework which make our life easy while scripting but it makes the scripts very slow and difficult to maintain. It goes vice versa also.
For e.g. resources create the framework where the scripts need to be created using keywords or functions in functional libraries. But in these cases they tend to repeat the same type of steps for multiple scripts. And if we create the reusable functions or actions then that will remove the keyword functionality.
From my understanding and experience the framework creation should be dependent on below points:
1. faster script creation
2. Does not hamper execution time by a great extent because in the end customer wants automation for faster and independent execution to save time and save money on resources.
3. Consistency in published results for test automation across organization or business unit.
4. easy to maintain
5. easier for manual resources to update scripts in future releases.
6. Whether the execution will be on individual machines or testing hosts.
7. Are automation scripts started from ALM or local machine.
And last but not the least when we are using UFT/QTP, instead of using the tools capability most of the time we choose to create functions and uses the tool only as a platform to execute. If this is the case then we can use any open source tools available in the market.
In my next post, I will cover the guidelines for different type of points i have given above for automation framework creation.
But while doing the scripting most us also thought about why are we using it or is it helping me or am I getting benefit from it.
Most of the people uses the framework which is already created in there respective organization and project but while using it they were get frustrated or make changes according to there comfort.
While creating or updating the automation framework, we should think from 3 stages:
1. While scripting
2. While maintenance
2. While execution
Most of the times people only think from the perspective of scripting and never thinks from execution perspective like how much time it will take or whether the maintenance or parameter input will be easy for the users.
Most of the time we create the framework which make our life easy while scripting but it makes the scripts very slow and difficult to maintain. It goes vice versa also.
For e.g. resources create the framework where the scripts need to be created using keywords or functions in functional libraries. But in these cases they tend to repeat the same type of steps for multiple scripts. And if we create the reusable functions or actions then that will remove the keyword functionality.
From my understanding and experience the framework creation should be dependent on below points:
1. faster script creation
2. Does not hamper execution time by a great extent because in the end customer wants automation for faster and independent execution to save time and save money on resources.
3. Consistency in published results for test automation across organization or business unit.
4. easy to maintain
5. easier for manual resources to update scripts in future releases.
6. Whether the execution will be on individual machines or testing hosts.
7. Are automation scripts started from ALM or local machine.
And last but not the least when we are using UFT/QTP, instead of using the tools capability most of the time we choose to create functions and uses the tool only as a platform to execute. If this is the case then we can use any open source tools available in the market.
In my next post, I will cover the guidelines for different type of points i have given above for automation framework creation.
