Why to have Programming Statements in Tests in QTP?

We add steps, which contain programming logic to the recorded
framework just to increase the power and flexibility of the testing
process.

Programming statements usually contain:

1) Recordable test object methods: These are operations that a user can perform on an application.

2) Non-recordable test object methods: These are operations that
users cannot perform on an application. We use these methods to
retrieve or set information, or to perform operations triggered by an
event.

3) Run-time methods of the object being tested.

4) Various VBScript programming commands that affect the way the
test runs, such as conditions and loops. These are often used to
control the logical flow of a test.

5) Supplemental statements, such as comments, to make our test
easier to read, and messages that appear in the test results, to alert
us to a specified condition.

GaneshKB

qtp, softwaretesting, vbscript, programming, test, application, conditional loop, ganeshkb, dexter, laboratory

Powered by ScribeFire.

Mercury Quick Test Professional

Hi,
I would love to Share some of the useful tips on QTP. This is a useful blog that will share information about QTP. Here it is easy to access about SQAFORUMS, You can even subscribe using the EMAIL address. Please click the link to know more...

GaneshKB

Powered by ScribeFire.

Superb site for QTP

Hi Folks,
I have a good site to share with you all. This is a tutorial for sure as it says, it covers QTP all ends.For any reference, please make use of this link...

GaneshKB

Powered by ScribeFire.

Difference between QTP and WinRunner functions? Might be handy for an interview

Hi All,
         Few difference between them, would be helpful for interviews:

qtp:To compare static and dynamic images through qtp

win runner: to conduct testing on static images only.

qtp: In this three types recording is possible
they are 1)GENERAL RECORDING 2)ANALOG RECORDING 3)LOW LEVEL
RECORDING

WIN RUNNER: In this two types of recording is possible

1.QTP supports different technologies like SAP
applications, Macro media applications, People Soft etc which
is not supported by Win Runner


In win runner 2 types of TSL test script ie.
1.Main test
2.Compiled module
But in QTP,
only one type of test script ie.Main test.It doesn't
support compiled module.


-->Win Runner uses Test Script Language which has limited
resources and QTP uses VB Script which is very powerful
language.
-->Parametrization is easier with QTP than Win Runner and
any thing in QTP can be parametrized.
-->Data driven testing is easier with more options in QTP
than Win Runner.
-->Win Runner uses GUI Map File and QTP uses Object
Repository.
-->Win Runner-GUI Map per test and Global GUI Map File
QTP- Object Repository Per Action and Shared.
-->There are more point and click options in QTP than
Win Runner.

GaneshKB

Advantages of QTP

Hi All,
Dexter is back with some information about QTP:

1.QTP allows even novice testers to be productive in
minutes. You can create a test script by simply pressing a
Record button and using an application to perform a typical
business process. Each step in the business process is
automated documented with a plain-English sentence and
screen shot. Users can easily modify, remove, or rearrange
test steps in the Keyword View.

2.QTP can automatically introduce checkpoints to verify
application properties and functionality, for example to
validate output or check link validity. For each step in
the Keyword View, there is an ActiveScreen showing exactly
how the application under test looked at that step. You can
also add several types of checkpoints for any object to
verify that components behave as expected, simply by
clicking on that object in the ActiveScreen.

3.You can then enter test data into the Data Table, an
integrated spreadsheet with the full functionality of
Excel, to manipulate data sets and create multiple test
iterations, without programming, to expand test case
coverage. Data can be typed in or imported from databases,
spreadsheets, or text files.

4.Advanced testers can view and edit their test scripts in
the Expert View, which reveals the underlying industry-
standard VBScript that QuickTest Professional automatically
generates. Any changes made in the Expert View are
automatically synchronized with the Keyword View.

5.Once a tester has run a script, a TestFusion report
displays all aspects of the test run: a high-level results
overview, an expandable Tree View of the test script
specifying exactly where application failures occurred, the
test data used, application screen shots for every step
that highlight any discrepancies, and detailed explanations
of each checkpoint pass and failure. By combining
TestFusion reports with Mercury Quality Management, you can
share reports across an entire QA and development team.

6.QTP also facilitates the update process. As an
application under test changes, such as when a ?Login?
button is renamed ?Sign In,? you can make one update to the
Shared Object Repository, and the update will propagate to
all scripts that reference this object. You can publish
test scripts to Mercury Quality Management, enabling other
QA team members to reuse your test scripts, eliminating
duplicative work.

7.QuickTest Professional supports functional testing of all
popular environments, including Windows, Web, .Net, Visual
Basic, ActiveX, Java, SAP, Siebel, Oracle, PeopleSoft,
terminal emulators, and Web services.

GaneshKB

What is difference between WinRunner and QTP?

Hi Lab Folks,
Cool information about WinRunner and QTP to share with you all.....

1.Winrunner uses TSL language where as QTP uses VB script & Java script

2.Winrunner doesn’t supports the OOPS concept where QTP supports the OOPS concept

3. Winrunner doesn’t supports to multimedia. QTP supports to multimedia , media player , photo shop. (6.5 version ).

4. Winrunner doesn’t supports to XML. QTP supports to XML

5. Winrunner doesn’t supports to .NET. QTP supports to .NET.

6. Winrunner supports only Interpreter ( Line by line execution ). QTP is compiler.

7. In Winrunner GUI spy is used to check the properties of object / window. In QTP,the name is Object spy

8. Winrunner: GUI Map editor is used to store the physical descriptions. QTP: Object Repository is used to store the physical descriptions of the objects

9. Winrunner has 3 modes of recoding :analog and context sensitive recording modes. QTP has only one recording mode i.e Standard recording mode. In this recording 2 types are (1) Analog (2) Low level

10. Winrunner has 4 types of checkpoints [ GUI checkpoint, Bitmap checkpoint, Database checkpoint, Text checkpoint ]. QTP has
9 types of checkpoints [ Standard check point, Bitmap checkpoint,
Database checkpoint, Text/Text area checkpoint, Image checkpoint, Table
checkpoint, Page checkpoint, Accessibility checkpoint, XML checkpoint ]

11. Winrunner: In GUI check point has 3 types
1. single object / single property
2. single object / multiple property
3. multiple object / multiple property
QTP has only One type i.e Single object / Multiple Property

12. Winrunner: In Bitmap checkpoint 2 types
1. for Object / Window
2. for Screen Area
QTP has only One i.e for Object / Window Bitmap using this above checkpoint we can check also Screen area

13. Winrunner: In Database check point there are 3 types
1. Default 2. Custom 3. Runtime
Here in QTP only One Type i.e Custom database checkpoint

14. 9 types of verifications in WR
1. Case Sensitive
2. Case Insensitive
3. Numeric Range
4. Numeric Content
5. Case Sensitive Ignore Space
6. Case Insensitive Ignore Space
7. Exact one match record
8. One or more match record
9. No match record

3 types of verifications in QTP
1. Numeric Range
2. Numeric Content
3. String Content

15. 3 types of Synchronizations in WR
1. for Object / Window Property
2. for Object / Window Bitmap
3. for Screen Area Bitmap
In QTP only One type i.e Object / Window Property

16. WR: Has 3 types of running modes i.e 1.Verify 2. Debug 3. Update. QTP has 2 types of running modes
i.e 1. Standard 2. Update

17. Exception Handling method used to avoid the runtime errors in WR 3 types [ 1. Popup 2. TSL 3. Object ] .In QTP name
is Recovery Scenario and here 4 types of exceptions [ 1. Pop-up Window
2. Object state 3. Test run error 4. Application Crash ]

18. In WR 4
types of result window [ 1. Test result window 2. GUI checkpoint window
3. DB checkpoint window 4. DB record checkpoint window ]. Here in QTP only One Window i.e Test Summary Result Window

19. In WR Test script is divided into 2 parts [ 1. Main Script 2. Compile Module ]. No such types using WR we can execute functions in QTP

20. Add-ins in WR are: 1. ActiveX 2. Power Builder 3. Visual Basic 4. Web 5. Java 6. C 7. C++ , etc Add-ins in QTP are: 1. ActiveX 2. Visual Basic 3. Java 4. Web 5. Multi-media ( 6.5 version )

21. In WR only One View i.e Normal Mode. Here in QTP 2 Views 1. Expert View 2. Keyword View

22.WR: Only One Sheet in data Table if we want to add another sheet then another new data table to be opened. In QTP 2 sheets in Data Table 1. Global 2. Action. In action sheet we can add number of sheets

23. WR: Virtual Object wizard only One type. QTP : 2 types of Virtual Object Wizards [ 1. Virtual Object 2. Virtual Object Manager ]

24. WR: Here after checking the checkpoints it gives mismatch error ( no snap Shots ). QTP: Checks the checkpoint but will not give mismatch error . If test is fail it shows snap shot

25. WR: support Rapid script wizard. QTP: no rapid script wizard

26. Function generator is present in WR. QTP: No Function Generator

27. WR: 2 types of GUI map editor [ 1. Global 2 Per test ]. QTP: only one type i.e Global

28. WR: Only One window I’e Form Window You want to open data table we have to call the function to open data table.
QTP : five types of Window [ 1. Tree View or Keyword view 2. Expert View 3. Data Table 4. Active Screen 5. Debug Viewer ]

29. WR: Running methods [ 1. Step, 2. Step into, 3. Step out ]. QTP : Running Methods [ 1. Step into 2. Step over 3. Step out ]

30. WR: Data type declaration is not necessary. QTP: data type declaration is must

Ganesh.KB


Technorati Tags: QTP, WinRunner, Difference, VBScript, TSL, XML, .NET, ganeshkb, dexter

VB Script for QTP

Hi All,
I have another site with loads of information about basic VB scripts and also how we have to use them in QTP. I found it when i was looking to learn more about VB script, as i am also a beginner in it. This stuff is really good, they come with two options one is the basic and the other for advanced on VB scripts. It might be useful do all the LAB folks. You can find the same from, when you click here...

Ganesh.KB


Technorati Tags: QTP, VB, SCript, GaneshKB, Dexter, Basic VB Script