11/09/2011 03:07:00 pm
Software Testing
This article explains the details to improve the performance of QTP tool if the performance reduces during the script execution.The following steps needs to be followed to improve the performance.
01. Load the required add ins:
Assume that we are working on Windows based application.To work on windows based application we need to load only the corresponding add ins. Otherwise it'll reduce the performance of the tool. For example, web add in used to load by default. We no need to add such kind of add ins for windows based application. If we do so, the performance of the automation tool will be drastically reduced.
02. Set the Run mode as Fast:
To set the run mode as Fast we need to enable the script debugger during the tool installation.To do this navigate to Tools...Options.. Run Mode...and set to Fast.
03. Disable Active Screens:
Active screen used to take lot of disk space when the script is running. As soon as the tool is installed this screen will be activated by default. We can disable this by navigating to View.. Active screen option or by clicking on close the window('x').We can observe that the slowness during script editing if the option active screen is enabled.
We have to disable the active screen capture during the test saving also by un checking "save active screen files" in save test dialog box.In some scenarios, capturing the screen shot is mandatory. We can do this by navigating If it is really needed, make sure in file settings>recovery scenario, you configure "activate recovery scenarios" appropriately. See if 'On error' would handle the job instead of 'on every step'.
04.Capturing Images & Movies:
Like active screens, capturing images and videos should be disabled during run time if it is not mandatory.We can do this by navigating to Tools.. Options.. Run.... uncheck "save movie results" and "save still images". But in some scenarios we may need to capture the videos and images.For example, some exception may happen in some of the screens. In such situations we need to select 'for errors' instead of 'always' option.
05. Recovery Scenarios:
This plays a major role in affecting the performance of the tool.Instead of using recovery scenarios we can use exist method to check whether a particular exception/error is occurred during the script execution. So, it's always better to avoid the recovery scenarios as much as possible.
If it's mandatory we can enable the recovery scenarios "on error" conditions by navigating to "activate recovery scenarios"
06. Run script in a cleaned machine:
I am sure that most of the organizations will not provide this option. If we are getting a separate machine with the required application and the automation tool, we can very well improve the performance of the tool due to the processor usage. We need to make sure that the pop up is disabled during the script recording to avoid the unwanted exceptions.
We can also avoid installing the unwanted software such as anti virus, printers etc.
I have given my points to increase the performance of the automation tool during the script execution. If anyone knows more information kindly let me know.
01. Load the required add ins:
Assume that we are working on Windows based application.To work on windows based application we need to load only the corresponding add ins. Otherwise it'll reduce the performance of the tool. For example, web add in used to load by default. We no need to add such kind of add ins for windows based application. If we do so, the performance of the automation tool will be drastically reduced.
02. Set the Run mode as Fast:
To set the run mode as Fast we need to enable the script debugger during the tool installation.To do this navigate to Tools...Options.. Run Mode...and set to Fast.
03. Disable Active Screens:
Active screen used to take lot of disk space when the script is running. As soon as the tool is installed this screen will be activated by default. We can disable this by navigating to View.. Active screen option or by clicking on close the window('x').We can observe that the slowness during script editing if the option active screen is enabled.
We have to disable the active screen capture during the test saving also by un checking "save active screen files" in save test dialog box.In some scenarios, capturing the screen shot is mandatory. We can do this by navigating If it is really needed, make sure in file settings>recovery scenario, you configure "activate recovery scenarios" appropriately. See if 'On error' would handle the job instead of 'on every step'.
04.Capturing Images & Movies:
Like active screens, capturing images and videos should be disabled during run time if it is not mandatory.We can do this by navigating to Tools.. Options.. Run.... uncheck "save movie results" and "save still images". But in some scenarios we may need to capture the videos and images.For example, some exception may happen in some of the screens. In such situations we need to select 'for errors' instead of 'always' option.
05. Recovery Scenarios:
This plays a major role in affecting the performance of the tool.Instead of using recovery scenarios we can use exist method to check whether a particular exception/error is occurred during the script execution. So, it's always better to avoid the recovery scenarios as much as possible.
If it's mandatory we can enable the recovery scenarios "on error" conditions by navigating to "activate recovery scenarios"
06. Run script in a cleaned machine:
I am sure that most of the organizations will not provide this option. If we are getting a separate machine with the required application and the automation tool, we can very well improve the performance of the tool due to the processor usage. We need to make sure that the pop up is disabled during the script recording to avoid the unwanted exceptions.
We can also avoid installing the unwanted software such as anti virus, printers etc.
I have given my points to increase the performance of the automation tool during the script execution. If anyone knows more information kindly let me know.
Posted in: Improving QTP Performance
0 comments:
Post a Comment