TESTEVERYTHING

Wednesday, 15 February 2012

Tips to Optimize QTP Scripts to Yield Better Performance



Tips to Optimize QTP Scripts to Yield Better Performance


We use Automated-testing tools to optimize our manual testing processes. But in order to reap full benefits of any automated testing tool, we must know the complete ins and outs of the tool otherwise it would be a huge waste of money spent on automation. We have to learn the automation tool very thoroughly. We also need to learn the language of the automation tool to do coding more effectively and efficiently. I believe that a software testing tool is as good as the person who is actually using it.
I have been getting so many emails from my esteemed readers asking about HP QuickTest Professional tutorials, QTP tips and tricks etc. Some readers even complain that their QTP scripts are too slow to execute. This time I decided to write a post on how to use QTP more effectively which means how to make our QTP scripts perform better. In order words, this post will throw light on some points, which will optimize your QTP scripts.
Some of the QTP optimization tips can be:  
Tip – 1: You should not use hard coded wait statement until absolutely necessary. Instead of the wait statement, you should use either exist or synchronization (sync) statements. The wait statement waits for the number of seconds, which have been provided. For example using wait(5) will wait for 5 seconds even if the browser gets into a ready state even after 2 seconds which means a waste of 3 seconds. Imagine how much time would be wasted if you have say 10 wait statements per script and you are running a batch of 500 scripts. A better alternative is using sync or exist statements for example:
 
Browser("").Page("").Sync
var=Browser("").Page("").Exist(2)
 

Never use the exist statement without a value as it will take the default object synchronization timeout value from QTP settings. You can navigate to these settings from File->Settings and then go to Run tab. So use Exist(0) instead of Exist(10). Moreover, I will suggest to set the global object synchronization timeout to 1 second. 
 Tip – 2: Use declared variables instead of using variables on the fly. In order to enforce this in your scripts, use Option Explicit statement which forces the variable declaration. Moreover, using declared variables, scripts perform a bit faster. Also if you are using Option Explicit, it has to be the very first line of the code otherwise you will get an error.
Tip – 3: Using QTP for a longer period of time has a direct impact on the performance. It has been observed that a lot of Random Access Memory(RAM) gets consumed by QTP if QTP is running scripts for prolonged time. QTP starts eating system memory(memory leak) and sooner or later it will get hanged and we will be required to kill the qtpro.exe process and restart QTP all over again. In such a case, I will suggest you is to use QTP on computers with particular good amount of RAM and equally good clock speed.
Tip – 4: Do not load all addins while opening QTP. Use only the addins, which are required. This directly impacts QTP performance.
Tip – 5: I have personally experienced that opening QTP through a vbs file is faster than loading QTP through the icon.

Tuesday, 10 January 2012

Jmeter: pass a value between threads


Synopsis: 

Find out ways to pass a value between threads (i.e. capturing a value in one of the thread and passing it to the other thread in the same test plan).

Tool Used:     JMeter: Performance testing tool.


Solution:       Sharing Variables





1)      Used Sampler : BSF Sampler
1)      Screenshot displaying the use of the BSF Sampler using  ${__setProperty(storeid, ${storeid})}; for capturing the time. The website used is http://www.mail-archive.com/jmeter-user@jakarta.apache.org/info.html for displaying the value captured in one thread to the other thread.
Screenshot 1: Displaying the BSF Sampler capturing the time value using ${__setProperty(storetime, ${__time(HMS)})};





Screenshot 2: Displaying the time captured using ${__property(storetime)} in the other thread.

Screenshot3: Successful execution of the script displaying the time value captured in Thread2




QTP : object is Visible OR Not on Web Page

Hi All,
Some times we have to  check that a object(WebElement) is  exist on page or not. For this we use object exist = False  property but when we run the script it gets failed While object is not showing in the Page. We think that there is  something  wrong.
The reason behind why QTP  is giving this because object is present in the page but not visible means it not displaying while it exist in HTML code.
So for this we have to be understand the object property( object.currentstyle.display) there will be case some time object inherit the property from its parent or another parent element property to display in page. First we have to identify that object when it not showing/displaying in page.We have to check its display property
Display property value we can get through like this 

rem disvalue

disvalue =Browser(“Google”).Page(“Google”).Image(“Happy Holidays from Google!”).Object.currentStyle.display
if disvalue =”block” then
print ” object not displaying”
else
print ” object displaying”
end if
like this(incase if object using display property from its  parent object )  we have to check by which element my object showing on page

Friday, 2 December 2011

Selenium disable add-ons pop-up for Custom firefox profile

Here is the way to disable add-ons window which appears every time when selenium scripts are run on Custom Firefox Profile.


Close all instances of Firefox browser and delete the following files from the Custom Profile folder, this should reset Extension Manager and disable add-ons pop-up:
  • extensions.cache
  • extensions.ini
  • extensions.rdf
  • compatibility.ini
This Add-ons pop-up will not displayed the next time you run selenium scripts.

To find the Firefox profile,  type in cmd run prompt "%APPDATA%\Mozilla\Firefox\Profiles\"  press enter

Thursday, 1 December 2011

Tips to Decide What Test Cases to Automate

It is impossible to automate all testing; the first step to successful automation is to determine what test cases should be automated first.

The benefit of automated testing is correlated with how many times a given test can be repeated. Tests that are only performed a few times are better left for manual testing. Good test cases for automation are those that are run frequently and require large amounts of data to perform the same action.


You can get the most benefit out of your automated testing efforts by automating:

  •       Repetitive tests that run for multiple builds
  •    Tests that are highly subject to human error
  •      Tests that require multiple data sets
  •        Frequently-used functionality that introduces high risk conditions
  •        Tests that run on several different hardware or software platforms and configurations
  •        Tests that take a lot of effort and time when doing manual testing

Saturday, 15 October 2011

Vi - Linux Editor Commands

Common vi Commands
Have a look at this list of common vi commands (there are many more, but these will at least allow you to get some basic work done). Then we'll do one more exercise before moving on.
Note: As with all of Linux, vi commands are case sensitive.
Positioning the Cursor
� Move cursor one space right.
� Move cursor one space left.
� Move cursor up one line.
� Move cursor down one line.
ctrl-F Move forward one screen.
ctrl-B Move backward one screen.
$ Move cursor to end of line.
^ Move cursor to beginning of line.
:1 Move to first line of file
:$ Move to last line of file
/ Search for a character string.
? Reverse search for a character string.
x Delete the character at the cursor position.
dd Delete the current line.
p Paste data that was cut with x or dd commands.
u Undo.

Basic UNIX Commands

Directory
::
Show current directory
pwd
Show content of directory
ls -al
Changing directory
cd <newdir>
Creating directory
mkdir <dir>
Deleting directory if empty
rmdir <dir>
Deleting directory if full
rm -r <dir>
Moving directory
mv <olddir> <newdir>
Copy directory
cp -r <olddir> <newdir>
Files
::
Show file entry
ls -al <file>
Delete file
rm -i <file>
Move file
mv <file> <path>
Copy file
cp <file> <newfile>
Rename file
mv <oldfile> <newfile>
Show file content at once
cat <file>
Show file content page wise
more <file>
Show file with long lines
cat <file> | fold
Show first 20 lines of file
head -20 <file>
Show last 20 lines of file
tail -20 <file>
Edit file
<editorname> <file>
Edit file with vi
vi <file>
Give all file permissions to yourself
chmod 700 <file>
The above even into subdirectories
chmod -R 700 <dir>
Open file for reading and executing for all
chmod 644 <file>
Starting file as program
<filneame> <arguments>
Find word in file
grep <word> <file>
Find all files which contain a word
grep -l <word> *
Find abstract pattern: ab 2 digits cd
grep 'ab[0-9][0-9]cd' <file>
Comparing two files
diff <file1> <file2>
Updating the date of a file
touch <file>
Giving a specific date to a file
touch 0101010199 <file>
Help
::
Getting help about a command
man <command>
Find command related to a term
man -k <term>
Where is a particular program if it is in the path
which <commandname>
Is a <name> a unix command or an alias in ksh
whence <commandname>
Aliases
::
Making an alias in csh/tcsh
alias <aliasname> '<long_command>'
Making an alias where the arguments go in the middle
alias <aliasneme> '<command> \!* <other>'
Making an alias in sh/bash/ksh
alias <aliasname>='<long_command>'
Using an alias
<aliasname> <arguments>
Use command instead of it's alias
\<command>
Showing all aliases
alias
Remove an alias
unalias <aliasname>
Adjustments
::
See environment variables
env
Setting the term variable if vi doesn't work
setenv term vt100
Opening the X-server for X-clients
xhost +
Setting the display for X-clients
setenv display <computer>:0.0
Internet
::
Telnet to another computer
telnet <computername>
Rlogin to another computer
rlogin -l <username_there> <computername>
Browsing the net with netscape
netscape
Check whether someone is logged in somwhere
finger user@host.domain
Check for all people on another computer
finger @host.domain
Talk to another person on another computer
talk user@host.domain
Ftp building up connection
ftp <computername>
Ftp adjusting for binary transfer
>bin
Ftp showing directory
>dir
Ftp changing directory
>cd /<path>/<path>
Ftp getting a file
>get <file>
Ftp getting multiple files
>mget <filenamecommon>*
Ftp searching for a file
>quote site find <filename>
Get the ip number of a computer
nslookup <computername>
Check whether another computer is up
ping <computername>
Check the pathway to another computer
traceroute <computername>
Info about Unix System
::
See who is logged on
who ... w ... what
Get the date
date
See who logged in lately
last -20
See what operating system is there
uname -a
See who you are
whoami
Get the name of your computer
hostname
See the disk space used
df -k
See you quota usage
quota -v
See how much space all your files need
du -k
Mail
::
Check for mail
from
Read mail
Mail
Compose mail
Mail -s <subject> <mailaddress>
Mail a whole file ( one "<" is real )
Mail -s <subject> <mailaddr> < <file>
Compressing Files
::
Compress 50%
compress <file>
Uncomress the above file.Z
uncompress <file>.Z
Compress 70%
gzip <file>
Uncompress the above file.gz
gzip -d <file>.gz

Translate







Tweet