0% found this document useful (0 votes)
153 views

Quick Test Professional

QuickTest Professional 9.5 was released in January and is an HP product used for testing various types of applications. It allows automating test cases to check functionality, validations, calculations, and error handling in a more efficient manner than manual testing. Key features include synchronization, checkpoints, data-driven testing, actions, and object identification.

Uploaded by

Reema Kumari
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
153 views

Quick Test Professional

QuickTest Professional 9.5 was released in January and is an HP product used for testing various types of applications. It allows automating test cases to check functionality, validations, calculations, and error handling in a more efficient manner than manual testing. Key features include synchronization, checkpoints, data-driven testing, actions, and object identification.

Uploaded by

Reema Kumari
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 37

Quick Test Professional

9.5 was released in Jan


Till 9.2 Mercury product
9.5 is HP Product.
Uses
Testing all kinds of Windows applications,web applications and visual basic applications.
1.To check the basic functionality s of any application
 Sanity testing or Built Verification Test(BVT)

i.e. for checking the stability of the application


2.Check for Validations
 Equivalence class partision(ECP) – Check for valid and invalid conditions.
 Bounadary Value Analysis(BVA) - Check for minimum ,maximum values.

Ex: 6 to 16(6-16)
n-1,n,n+1
6-1,6,6+1

N-1 = 6-1=5 <6 =test fail


N=6=n=test pass
N+1=6+1=7>6=test pass.

,
Diff b/w Manual & Automation

Manual Testing
 Cannot be repeated

 More Time Consuming

Automation Testing
 Script recorded once can be re –used

many times
 Less time consuming
Example
Verify login for 5 different accounts
Instead of recording the script for 5times
for 5 different users, can record once the
script for one particular account the play
back the same script for other four
accounts which saves time
Diff b/w regression testing & Re-
testing
Ex: There are 4 actions like,
login, compose, save, send.

Consider the above 3 actions(login,compose,save) are working and send is not working.
We find the defect n send it to development team. Once they fix n send it back for testing , We
test same action send again is called Re-testing.

And also we test the other 3 actions to ensure no side effects is called as Regression testing

Testing same function along with other functions to ensure no side effects is called regression
testing.

Testing same function is called as re testing


Introduction
 It is an automated functional Graphical
User Interface (GUI) testing tool created
by the subsidiary Mercury Interactive that
allows the automation of user actions on a
web or client based and desktop computer
application. It is primarily used for
functional regression test automation
Regression Testing
 Regression testing is any type of
software testing which seeks to uncover
software regressions. Such regressions
occur whenever software functionality that
was previously working correctly, stops
working as intended. Typically regressions
occur as an unintended consequence of
program changes.
Types of Recording
 Normal Recording – Used for Business
transactions. It is called as Default Recording.

 Analog Recording - Gives exact mouse


movements of any action recorded.
Mainly used for testing digital signatures

 Low-level Recording - For recording non-standard


objects not recognized by tool such as images.
Functionality - Techniques
 Object Properties:
It is used to test properties of an object ,is
the buttons are enabled, disabled,focused.
 Input Domain
(a) Equivalence class partition – check for Valid&
Invalid conditions
(b) Boundary Value Analysis - Check for
maximum and minimum values.
Continuation
 Calculations - for testing calculations such as
addition, multiplication (salary calculations).
 Error Handling or Negative testing

For testing negative values.


Ex: Password length (4-14)
Test by giving less than 4 no of characters
 Database testing – Test front end w.r.t back

end by using sql statements.


Continuation
 Uniform Resource Locator (URL) – Testing
for web address, links.
 Overall functionality – testing all above
properties is called Overall functionality
Check points

 QTP is a functional testing tool used for testing.


Testing all the above techniques is called as Check
points

 A checkpoint verifies that expected information


is displayed in a Application while the test is
running
Types
Types
 Standard Check point
 Text Check point
 Bit Map Check point
 Accessibility Check Point
 Data Base Check point
 XML Check Point Additional Check points for Web application
 Text Area Check point
 Table Check points
 Image Check Point
 Page Check point -
Checkpoints
 Standard Check Points
It is used for testing the properties of an
object like enable, disable, focused

 Text Check Points


It is used for testing the text of the
applications
Checkpoints
 Bit map Check Points

Used for 2 types of bit map validations.


 Company logos
 Digital Signatures
 Windows Media player
 Mp3 players.
Checkpoints
 Accessibility check points
Used for checking URLs ,links
 Data base Check points

To validate the front data w.r.t back end


we use database check points. In other
terms changes or data updations on front
end should reflect on back end also
Checkpoints
 XML check points
For checking the content of xml files.

 Text area check points.


Check for area within which text is places.
Ex.
Note
 When we execute a script with check
points, if the check point fails then the
expected value along with the actual value
is captured with the image of that object.
having many check points in a script will
reduce the speed of execution.
Output Values
 Output Value – Checkpoints – To view
object properties in data table during time
.

 To view the results during the runtime, we


use standard output values.
Data Driven Test
 Executing the test script by parametrizing
the data or with multiple sets of data is
called as Data Driven Test.
Step Generator
 We use step generator to add additional steps or
extra steps .It will add object s in object
repository.
Category Types
(a)Test Object – To the recorded script you can
add extra steps.
Ex : Suppose in case if have forget to close Flight reservation window
during recording session and you want to close once you have
stopped recording then you can add the object to reporistory using
of Test objects
Step Generator

(b) Utility Objects -Instead of keeping the


application open while running you can
go Utility object s ,select the path of
application required and set same in Utility
objects.
(c) Functions – To display msg boxes.
Ex : Input box and msg box
Actions & Test
Actions– set of statements or set of scripts is called as
Actions.
To run the test Systematically , we make use of actions.
Re-Usable Actions – Cannot make changes where we are
calling , but can make changes on the original script.
Can be used multiple times.
Non – Re-Usable Actions – Can be modified wherever we
are calling.

Test- Set of actions is called as Tests


Actions
 Nested Actions – Action within an action
 Independent Action – Individual or
separate action
Synchronization or Wait
 Wait() is used when you want QTP to wait
for specified time whereas synchronization
is used when you want QTP to wait till
certain process is completed or event has
occured.
 Synchronization is used when we are not
sure how much time the process may
take.
Synchronization
 waiting time in the sense that if you have an application in which
you have 3 steps for example. Let's say you are recording the
steps where the first step is to enter the information, second
step is clicking submit button and third step is printing the
summary page. Now when you click submit button it may take
few seconds to several minutes depending on the application or
internet speed. After your summary page has loaded you click
print. But when you play this in Qtp it does it very fast,it does
not wait for processing of information after you click submit
button and may try to print summary page which will give error.
So, to overcome such problems we insert synchronization
point.By inserting synchronization point we are asking QTP to
wait till Summary page is loaded and then click Print button.
Conditional statements
 If Condition)
………..
……….
………..
End if
Ex: Dim x
X=input box(“enter a number”)
If x<=20
Msgbox(“x is less than 20”)
Else
Msgbox(“x is more than 20”)
End if
Loop Statements
(A) While
--------
-------
-----
Wend
Ex: Dim x
X=1
While x<=5
Msgbox x
X=x+1 0r X=x+2
Wend
Loop Statements
(B) For
------
------
-----
Next
Ex: dim a
For a=1 to 5
Msgbox a
Next
Loop Statement
(C) Select case
-------
-------
------
End select
Dim x
X=inputbox(“enter a character”)
Select case x
Case ‘a’, ‘e’, ‘i’ , ‘o’, ‘u’
Msgbox (“its an vowel”)
Case else
Msgbox (“its not an vowel”)
End select
Object Repository
 Multiple test using the same repository is
called as Shared Repository
 Use Object Repository Manager to merge
different files into one.
 Cannot merge all three files at a time.
Regular Expressions
When window name is changing dynamically or when value is
unique during each run time we make us of Regular expressions.

Ex:
1-step: insert order, fax order ,run.
2-step: Go to object repository, click on fax order no and configure
value
3-step:Replace the fax order no with * right after the period(.)
4-step : check the box regular expressions.
5-step :no to add back slash
6-step : run.
Recovery Scenario
 When Some exceptions are raised during
execution of script, which interrupts the
test run , we introduce recovery scenario.
Object Identification
 To identify the objects
 To convert custom object s into standard objetcs.

How does tool identify the recorded objects,


1.Check for mandatory field in Object repository
2.Check for mandatory properties, assistive properties
in Object identification.
3.Check for Index and Location.
4. Enable Smart identification on Object identification so
that it will capture the object id or session id
Descriptive Programming
Without using repository , executing the script
Ex:
Dialog(“text:=login”). Activate
Dialog(“text:=login”). Winedit (“x:=20”, “y:=66”).
set “Bhavya”
Dialog(“text:=login”). Winedit (“x:=20”, “y:=66”).
set “mercury”
Dialog(“text:=login”). Winbutton (“text:=ok”). click
Debug
 Debug – To check whether the script is
running smooth without any interruption of
errors.
 Step into - Line by line
 Step over - For functions without viewing
script
 Step out - For functions with viewing script

You might also like