QTP Interview Questions 4

1. How many ways we can parameterize data in QTP?
There are four types of parameters
1. Test Action or Component Parameters enable you to use values passed from your test or component or values from other actions in your test.
2. Data Table parameters enable you to create a data driven test or an act.
That runs several times using the data you supply.In each repeation or iteration quick test uses a Different value from the data table.
3. Environment variable parameters enable you to use variable values from other sources during the run sessions. these may be values you supply, or values that QTP generates for you based on conditions and options you choose.
4. Random number parameters enable you to insert random numbers as values in your test or component.
For example, to check how your application handles small and large ticked orders, you can have QTP generate a random number and insert it in a number of tickets edit field.

2. How do you do Batch testing Winrunner and is it possible to do in QTP? If So, Explain?
Batch testing in Winrunner is nothing but running the whole test set by selecting “Run Test Set” from the “Execution Grid”. The same is possible with QTP also. If our test cases are automated then by selecting ” Run test Set” all the test scripts can be executed.
With this process the scripts get executed one by one keeping all the remaining scripts in “Waiting Mode”.

3. If I give some 1000 tests to execute in 2days what do you do?
Adhoc Testing is done. It covers the least basic functionalities to verify that the system is working fine.

4. What does it mean when a checkpoint is in red color? What do you do?
Red color indicates failure. Here we analyze the cause for the failure whether it is a script issue or environmental issue or a application issue.

5. What do you call the Window Testing Director test lab?
“Execution grid” it is placed from where we run all the manual/automated scripts.

6. How do you create new test sets in test director?
Login to TD.
Click on “Test Lab” Tab.
Select the desired folder under which we need to create the test set.(Test sets can be grouped as per module).
Click on “New test set or Control N” Icon to create a test set.

7. How to import data from a “.XLS” file to data table during run time?
Data table .Import “…XLS filename…”
Datatable .Import sheet (FileName, SheetSource, SheetDest)
Datatable>Importsheet “C:\name.Xls”, 1, “name”

8. How to export data present in Database to an “.XLS” file?
Datatable .Export “…xls filename…”

9. How to get traceability matrix from TD?

10. How to import a test case present in “.XLS” file to TD under a test set?

11. How to attach a file to Test director?

12. What do you do to script when objects or removed from application?

13. Syntax for how to call one script from another? and syntax to call one action in another?

Run Action Action Name,[IterationMode, IterationRange, Parameters] here the actions becomes reusable on making this call to any action.
IterationRange string not always required. Indicates the rows for which action iterations will be performed. Valid only when the iterationMode is rnfinteration. Enter the row range (i.e “1.7″): or enter rngAll to run iterations on all rows.
If the actions called by the RunAction statement includes an ExitAction statement, the Run Action
Statement can return the value of the ExitActions Ret Val arguement.

14. How to export QTP results to an “.xls” file?
By default it creates an “XML” file and displays the results.

15. What are the Differences between QTP and Winrunner?
QTP is Object based scripting (VB) where as WR is TSL ( C based language) Scripting.
QTP supports “.Net” application automation not available in WR
QTP has “Active Screen” support which captures the application not available in WR.
QTP has “Data Table to store script values, variables which WR does not have.
Using a “point and click” capability you can easily interface with objects, their.
Definitions and create checkpoints after having record script without having.
To navigate back to that location in your application like you have to with WinRunner.
This greatly speeds up script development