Showing posts with label QTP. Show all posts
Showing posts with label QTP. Show all posts

Sunday, 23 September 2012

QTP-Parameterization in QTP using DataTable


Data driven means that we run same QTP script using different data.
For example you can create Login script and then use data driven methods to run that script multiple times with multiple sets of userid and passwords.
Using QTP data tables
Using Excel sheets
Using Access database
You can use ADODB object to get data from Excel and Access and put that data in Arrays or Dictionary object and then can use that data in different scripts.
Parameterization in QTP using Data Table :
Invoke Application "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.exe"
Dialog("Login").WinEdit("Agent Name:").Set Data Table.Value("A","Global")
Dialog("Login").WinEdit("Password:").Set Data Table.Value("B","Global")
Dialog("Login").WinButton("OK").Click
Window("Flight Reservation").Close
Example :
Data Driven Testing in QTP by passing different values thru external data files such as excel.
SystemUtil.Run "C:\Program Files\Internet Explorer\IEXPLORE.EXE","","C:\Documents and Settings\ahamad","open"
Datatable.Import("D:\data.xls")
Datatable.AddSheet(1)
row_cnt=datatable.getrowcount
Msgbox row_cnt
For i=1 to row_cnt
Uid=Datatable.Value("Uid",1)
msgbox Uid
Password=Datatable.Value("Password",1)
msgbox Password
Browser("Browser").Page("gmail.email").Link("Mail").Click
Browser("Browser").Page("gmail.email").WebEdit("login").Set DataTable("Uid")
Browser("Browser").Page("gmail.email").WebEdit("passwd").SetSecure DataTable("Password")
Browser("Browser").Page("gmail.email").WebButton("Sign In").Click
Browser("Browser").Page("gmail.email (ahamadqtp)").WebElement("Sign Out").Click
Browser("Browser").Page("Page").Sync
Browser("Browser").Close
Next
datatable.setnextrow

Read more »

QTP-Recovery Scenarios -QTP



Recovery Scenarios
What is a recovery scenario:
Recovery scenario - a definition of an unexpected event or error or application crash and the operation(s) necessary to recover the run session
A recovery scenario consists of the following
Trigger Event—The event that interrupts your run session.
Recovery Operation(s)—The operation(s) that need to be performed in order to continue running the test or component
Post-Recovery Test Run Option—The instructions on how Quick Test should proceed once the recovery operations have been performed, and from which point in the test or component Quick Test should continue, if at all.
Recommendations for using Recovery Scenarios
If you can predict that a certain event may happen at a specific point in your component, it is highly recommended to handle that event directly within your component by adding steps such as If statements or “Optional Steps” in user-defined functions, rather than depending on a recovery scenario.
You should use recovery scenarios only for unpredictable events, or events that you cannot synchronize with a specific step in your component.
Handling an event directly within your component enables you to handle errors more specifically than recovery scenarios. It also enables you to control the timing of the corrective operation with minimal resource usage and maximum performance.
Different Recovery Operations:
Keyboard or mouse operation—QuickTest simulates a click on a button in a window or a press of a keyboard key.
Close application process—QuickTest closes specified processes.
Restart Microsoft Windows—QuickTest restarts Microsoft Windows.
Function call—QuickTest calls a VBScript function.
Different Post-Recovery Test Run Options:
Repeat current step and continue
The current step is the step that QuickTest was running when the recovery scenario was triggered.
Proceed to next step
Skips the step that Quick Test was running when the recovery scenario was triggered.
Restart current test run
Stops performing steps and re-runs the component from the beginning.
Stop the test run
Stops running the component.
Associating Recovery Scenarios with the test:
While associating the recovery with your test, you need to specify when you want to activate recovery scenarios i.e. only on errors or on every steps.
If you select On errors option then keep in mind that by default, recovery operations will be activated only when a step returns an error, which can potentially occur several steps after the one that actually caused the error. So you may get the advantages of using recovery scenarios
If you select on every steps then keep in mind that checking for trigger events after every step, may slow performance. 

Read more »

QTP -AOM Scripts


'Script To open QTP and run Test

Dim app
set app=CreateObject("QuickTest.Application")
app.launch
app.visible=True
app.open "E:\ahamad\Test1"

''Script to connect to Quality Center From QTP
Set app=CreateObject("QuickTest.Application")
app.Launch
app.Visible = True
app.TDConnection.Connect "QCURL","DOMAIN","PROJECT","USERNAME","PASSWORD",False
''Example : app.TDConnection.Connect "http://192.168.1.1:8080/qcbin","Default","proj1","ahamad",,false

'''Script to Connect to QC and Add a new Defect in QC from QTP
Dim qccon
Set qccon=CreateObject("TDApiOle.TDConnection")
qccon.InitConnection "http://qcserverurl:8080/qcbin"
qccon.ConnectProject "proj1","ahamad",""
If qccon.Connected Then
    Msgbox "Connected to QC Server
Else
   MsgBox "Not Connected"
End If

Set BugFactory = qccon.BugFactory
Set Bug = BugFactory.AddItem(Nothing)
Bug.Status = "New"
Bug.Summary = "Error in login"
Bug.Priority = "4-Very High"
Bug.AssignedTo ="user1"
Bug.DetectedBy = "ahamad"
Bug.Post

' Close QTP After execution of the Test
set wm=GetObject("winmgmts:\\.\root\CIMV2")
Set pros=wmi.ExecQuery("Select * from Win32_Process Where Name = 'QTPro.exe'")
For Each p in pros
   p.Terminate()
Next
Set wmi=Nothing
Set pros=Nothing

Read more »

QTP-Real Time Descriptive Programming


Descriptive Programming
Let’s get on with a simple program to understand this concept.
On Performing a Record function using QTP on a program (Assumption – Program static in Nature), The Quick test recognizes the appropriate object used and adds them to the repository.  On executing the quick test program, the application would execute without any errors because the QTP would use the Mandatory\Assistive properties to recognize the objects used in the program.
Assume a new Textbox object is displayed with Properties which are dynamically generated. For e.g. name property is generated dynamically based on the current date like ‘TextB_2007_01_01”. Now when this object is added to the repository, the possibility of QTP program working is very less.
The ideal solution is set to set the name property at runtime i.e. write a code and set the property of the variable.
 Assumption it is a webedit box
Dim curr_date
Curr_date = year (now) &”_”& Month (now) &"_"& Day (now)
‘Curr_date would contain the current date. For e.g. Curr_date = “2007_01_01”
 Browser (“…”).Page (“….”).Webedit (“Name: = TextB_” & Curr_date).Set “Hello”
You can describe an object directly in a statement by specifying property:=value pairs describing the object instead of specifying an object's name.
The syntax is:
TestObject("PropertyName1:=PropertyValue1","...","PropertyNameX:=PropertyValueX")
Why and when do we need Descriptive Programming
Possible reasons to use Descriptive Programming are
When the object properties used in the application are dynamic in nature i.e. to be more precise the properties used to recognize are not constant and requires special handling.
To restrict the object repository to a limited size to avoid performance execution issues.
When the application to tested is not developed completely for testing and designing of Automation scripts need to commence.
Also some certain scenarios, where the Object or the control cannot be recognized. This will be dealt in the forthcoming sections.
Things to do to understand Descriptive Programming
In order to exercise the benefits of descriptive programming, the user has to follow at least the minimum guidelines give below           
Understand the Object or control which requires descriptive programming.
This would revolve around understanding various properties of object and should answer questions such as what is the Class \ MICLASS property of the object? This property holds values such as whether it is Webedit or IMAGE or WEBLIST.
Can the Object be uniquely recognized with available properties such as Name, ID, HTML TAG?
Is the Object just required to recognize sub elements within object?
Assume a Web application named “DEMO” needs to be tested. The Application is designed such that browser title keeps changing based on the module.
Always the title has “DEMO:” as a Constant string followed by the module name.
Now in an Object Repository, instead of storing multiple Browser objects in the repository. The user can use regular expression to such as “DEMO : .*”.
This would help in recognizing the sub elements provided the user Checks the regular expression property.

If these are .NET custom controls, Refer the QTP Help.
What’s a Description Object?
This is a generic object which can be used to mould (i.e. programmatically configured) itself as an object in the application.
Assume a Webedit object needs to use to set data.
‘ Create a Generic description using the below syntax
Set EditDesc = Description.Create()
EditDesc("Name").Value = "userName"
EditDesc("Index").Value = "1"
Browser("…").Page("….").WebEdit(EditDesc).Set "MyName"
Let’s take this above example to a different level.
Various methods of using Description Object
Now you want to count the number of webedit objects in a Web table.
Here are going to use CHILDOBJECTS property of web table to solve.
‘Define you Webedit object using the properties you require.
Set editdesc=Description.create()
Edit(“micclass”).value=”Webedit”
Set ctr=Browser(“…”).Page(“…”).Webtable(“TABLE1”).Childobjects(editdesc)
‘Ctr object here is an array of objects where each object is similar to ‘description object
Msgbox ctr.count
To print the name of each element in this array we can do the following
For i = 0 to ubound(ctr)
            Msgbox Ctr(i).Name
Next
To skim through the properties of each webedit object in the array
Set editdesc=Description.create()
Edit(“micclass”).value=”Webedit”
Set wbtab_arr =Browser(“…”).Page(“…”).Webtable(“TABLE1”).Childobjects(editdesc)
For each obj1 in wbtab_arr
Temp_name = Obj1.Name
Temp_value = obj1.value
Next
To scan the properties of web object.
Let’s take webtable and proceed
Set wbtab_prop =Browser(“…”).Page(“…”).Webtable(“TABLE1”). GetTOProperties
            For k= 0 to wbtab_prop.count – 1
                        Msgbox Wbtab_prop(i).name
                        Msgbox wbtab_prop(i).value
            Next

Note: For Regular expression, use the wbtab_prop(i).regularexpression.
Tips and Tricks which can be used in a Description Programming
Navigating through each Cell in a Web table.
Webtabobj= Browser(…).Page(“….”).Webtable(“table1”).object
Rowcnt= Webtabobj.Rowcount
For i = 1 to Rowcnt
            For j = 1 to Webtabobj. ColumnCount(i)
                                    Msgbox Webtabobj.getcelldata (i,j)
            Next
Next

Setting value “TEST1” in all the webedit controls in a webtable
            Webtabobj= Browser(…).Page(“….”).Webtable(“table1”).object
Rowcnt= Webtabobj.Rowcount
For i = 1 to Rowcnt
                        For j = 1 to Webtabobj. ColumnCount(i)
                                                Set tempwebedit= webtabobj.chilitem(i,j,”Webedit”,0)
                                                Tempwebedit.set “TEST1”
                        Next
Next
Setting up property of object dynamically
We can use either use an environment variable or Set to property to perform this .
You can declare a environment variable in the QTP script.
            Environment(“Demotitle”)= “DEMO:.*”
            ‘Check the Regular expression Check Box if necessary
Using “Set to property” also we achieve this task.
            Syntax : object.SetTOProperty Property, Value

Removing property of an object dynamically
Syntax : object.Remove “Property”
e.g:
                                    ‘to delete the html tag property from the collection
                                     object.remove “html tag”

The following points will also be covered
Get all elements in HTML tag
Active element in webpage

 
 

Read more »

QTP-Descriptive programming in QTP


Descriptive programming in QTP

Introduction:

This document demonstrates the usage of Descriptive programming in QTP. It also discusses situations where Descriptive programming can be used. Using Descriptive Programming automation scripts can be created even if the application has not been developed.

Descriptive Programming:

Whenever QTP records any action on any object of an application, it adds some description on how to recognize that object to a repository of objects called object repository. QTP cannot take action on an object until unless its object description is in the Object Repository. But descriptive programming provides a way to perform action on objects which are not in Object repository

Object Identification:

To identify an object during the play back of the scripts QTP stores some properties which helps QTP to uniquely identify the object on a page. Below screen shots shows an example Object repository:

Now to recognize a radio button on a page QTP had added 2 properties the name of the radio button and the html tag for it. The name the left tree view is the logical name given by QTP for the object. This can be changed as per the convenience of the person writing the test case. QTP only allows UNIQUE logical name under same level of hierarchy. As we see in the snapshot the two objects in Browser->Page node are “WebTable” and “testPath”, they cannot have the same logical name. But an object under some other node can have the same name. Now with the current repository that we have, we can only write operation on objects which are in the repository. Some of the example operations are given below

Browser("Browser").Page("Page").WebRadioGroup ("testPath").Select "2"

cellData = Browser("Browser").Page("Page").WebTable ("WebTable").GetCellData (1,1)

Browser("Example2").Page("Page").WebEdit("testPath").Set "Test text"

When and Why to use Descriptive programming?

Below are some of the situations when Descriptive Programming can be considered useful:

The objects in the application are dynamic in nature and need special handling to identify the object. The best example would be of clicking a link which changes according to the user of the application, Ex. “Logout <<UserName>>”.

When object repository is getting huge due to the no. of objects being added. If the size of Object repository increases too much then it decreases the performance of QTP while recognizing a object.

When you don’t want to use object repository at all. Well the first question would be why not Object repository? Consider the following scenario which would help understand why not Object repository

Scenario 1: Suppose we have a web application that has not been developed yet. Now QTP for recording the script and adding the objects to repository needs the application to be up, that would mean waiting for the application to be deployed before we can start of with making QTP scripts. But if we know the descriptions of the objects that will be created then we can still start off with the script writing for testing

Scenario 2: Suppose an application has 3 navigation buttons on each and every page. Let the buttons be “Cancel”, “Back” and “Next”. Now recording action on these buttons would add 3 objects per page in the repository. For a 10 page flow this would mean 30 objects which could have been represented just by using 3 objects. So instead of adding these 30 objects to the repository we can just write 3 descriptions for the object and use it on any page.

Modification to a test case is needed but the Object repository for the same is Read only or in shared mode i.e. changes may affect other scripts as well.

When you want to take action on similar type of object i.e. suppose we have 20 textboxes on the page and there names are in the form txt_1, txt_2, txt_3 and so on. Now adding all 20 the Object repository would not be a good programming approach.

How to use Descriptive programming?

There are two ways in which descriptive programming can be used

By creating properties collection object for the description.

By giving the description in form of the string arguments.

By creating properties collection object for the description.

To use this method you need first to create an empty description

Dim obj_Desc ‘Not necessary to declare

Set obj_Desc = Description.Create

Now we have a blank description in “obj_Desc”. Each description has 3 properties “Name”, “Value” and “Regular Expression”.

obj_Desc(“html tag”).value= “INPUT”

When you use a property name for the first time the property is added to the collection and when you use it again the property is modified. By default each property that is defined is a regular expression. Suppose if we have the following description

obj_Desc(“html tag”).value= “INPUT”

obj_Desc(“name”).value= “txt.*”

This would mean an object with html tag as INPUT and name starting with txt. Now actually that “.*” was considered as regular expression. So, if you want the property “name” not to be recognized as a regular expression then you need to set the “regularexpression” property as FALSE

obj_Desc(“html tag”).value= “INPUT”

obj_Desc(“name”).value= “txt.*”

obj_Desc(“name”).regularexpression= “txt.*”

This is how of we create a description. Now below is the way we can use it

Browser(“Browser”).Page(“Page”).WebEdit(obj_Desc).set “Test”

When we say .WebEdit(obj_Desc) we define one more property for our description that was not earlier defined that is it’s a text box (because QTPs WebEdit boxes map to text boxes in a web page).

If we know that we have more than 1 element with same description on the page then we must define “index” property for the that description

Consider the HTML code given below

<INPUT type=”textbox” name=”txt_Name”>

<INPUT type=”textbox” name=”txt_Name”>

Now the html code has two objects with same description. So distinguish between these 2 objects we will use the “index” property. Here is the description for both the object

For 1st textbox:

                obj_Desc(“html tag”).value= “INPUT”

obj_Desc(“name”).value= “txt_Name”

obj_Desc(“index”).value= “0”

For 2nd textbox:

                obj_Desc(“html tag”).value= “INPUT”

obj_Desc(“name”).value= “txt_Name”

obj_Desc(“index”).value= “1”

Consider the HTML Code given below:

<INPUT type=”textbox” name=”txt_Name”>

<INPUT type=”radio” name=”txt_Name”>

We can use the same description for both the objects and still distinguish between both of them

obj_Desc(“html tag”).value= “INPUT”

obj_Desc(“name”).value= “txt_Name”

When I want to refer to the textbox then I will use the inside a WebEdit object and to refer to the radio button I will use the description object with the WebRadioGroup object.

Browser(“Browser”).Page(“Page”).WebEdit(obj_Desc).set “Test” ‘Refers to the text box

Browser(“Browser”).Page(“Page”).WebRadioGroup(obj_Desc).set “Test” ‘Refers to the radio button

But if we use WebElement object for the description then we must define the “index” property because for a webelement the current description would return two objects.

Hierarchy of test description:

When using programmatic descriptions from a specific point within a test object hierarchy, you must continue to use programmatic descriptions

from that point onward within the same statement. If you specify a test object by its object repository name after other objects in the hierarchy have

been described using programmatic descriptions, QuickTest cannot identify the object.

For example, you can use Browser(Desc1).Page(Desc1).Link(desc3), since it uses programmatic descriptions throughout the entire test object hierarchy.

You can also use Browser("Index").Page(Desc1).Link(desc3), since it uses programmatic descriptions from a certain point in the description (starting

from the Page object description).

However, you cannot use Browser(Desc1).Page(Desc1).Link("Example1"), since it uses programmatic descriptions for the Browser and Page objects but

then attempts to use an object repository name for the Link test object (QuickTest tries to locate the Link object based on its name, but cannot

locate it in the repository because the parent objects were specified using programmatic descriptions).

Getting Child Object:

We can use description object to get all the objects on the page that matches that specific description. Suppose we have to check all the checkboxes present on a web page. So we will first create an object description for a checkboxe and then get all the checkboxes from the page

Dim obj_ChkDesc

Set obj_ChkDesc=Description.Create

obj_ChkDesc(“html tag”).value = “INPUT”

obj_ChkDesc(“type”).value = “checkbox”

Dim allCheckboxes, singleCheckBox

Set  allCheckboxes = Browse(“Browser”).Page(“Page”).ChildObjects(obj_ChkDesc)

For each singleCheckBox in allCheckboxes

singleCheckBox.Set “ON”

Next

The above code will check all the check boxes present on the page. To get all the child objects we need to specify an object description i.e. we can’t use the string arguments that will be discussed later in the 2nd way of using the programming description.

Possible Operation on Description Object

Consider the below code for all the solutions

Dim obj_ChkDesc

Set obj_ChkDesc=Description.Create

obj_ChkDesc(“html tag”).value = “INPUT”

obj_ChkDesc(“type”).value = “checkbox”

Q: How to get the no. of description defined in a collection

A: obj_ChkDesc.Count ‘Will return 2 in our case

Q: How to remove a description from the collection

A: obj_ChkDesc.remove “html tag” ‘would delete the html tag property from the collection

Q: How do I check if property exists or not in the collection?

A: The answer is that it’s not possible. Because whenever we try to access a property which is not defined its automatically added to the collection. The only    way to determine is to check its value that is use a if statement “if obj_ChkDesc(“html tag”).value = empty then”.

Q: How to browse through all the properties of a properties collection?

A: Two ways  1st:

                 For each desc in obj_ChkDesc

                                                Name=desc.Name

                                                Value=desc.Value

                                                RE = desc.regularexpression

                                Next

                2nd:

                              For i=0 to obj_ChkDesc.count - 1

                                                Name= obj_ChkDesc(i).Name

                                                Value= obj_ChkDesc(i).Value

                                                RE = obj_ChkDesc(i).regularexpression

                                Next

By giving the description in form of the string arguments.

You can describe an object directly in a statement by specifying property:=value pairs describing the object instead of specifying an object’s

name. The general syntax is:

TestObject("PropertyName1:=PropertyValue1", "..." , "PropertyNameX:=PropertyValueX")

TestObject—the test object class could be WebEdit, WebRadioGroup etc….

PropertyName:=PropertyValue—the test object property and its value. Each property:=value pair should be separated by commas and quotation

marks. Note that you can enter a variable name as the property value if you want to find an object based on property values you retrieve during a run session.

Consider the HTML Code given below:

<INPUT type=”textbox” name=”txt_Name”>

<INPUT type=”radio” name=”txt_Name”>

Now to refer to the textbox the statement would be as given below

Browser(“Browser”).Page(“Page”).WebEdit(“Name:=txt_Name”,”html tag:=INPUT”).set “Test”

And to refer to the radio button the statement would be as given below

Browser(“Browser”).Page(“Page”).WebRadioGroup(“Name:=txt_Name”,”html tag:=INPUT”).set “Test”

If we refer to them as a web element then we will have to distinguish between the 2 using the index property

Browser(“Browser”).Page(“Page”).WebElement(“Name:=txt_Name”,”html tag:=INPUT”,”Index:=0”).set “Test” ‘ Refers to the textbox

Browser(“Browser”).Page(“Page”).WebElement(“Name:=txt_Name”,”html tag:=INPUT”,”Index:=1”).set “Test” ‘ Refers to the radio button

Examples

'Script for Login
Systemutil.Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.exe"
with Dialog("text:=Login")
.WinEdit("attached text:=Agent Name:").set "abcd"
.WinEdit("attached text:=Password:").set "mercury"
.WinButton("text:=OK").click
End with

'Script for Insert new Record

 With Window("text:=Flight Reservation")
.WinMenu("menuobjtype:=2").Select "File;New Order"
.ActiveX("acx_name:=MaskEdBox").Type "062610"
.WinCombobox("attached text:=Fly From:").Select "Denver"
.WinComboBox("attached text:=Fly To:").Select "Paris"
.WinButton("text:=FLIGHT").Click
.Dialog("text:=Flights Table").WinList("attached text:=From","nativeclass:=ListBox").Select 1
.Dialog("text:=Flights Table").WinButton("text:=OK").Click
.WinEdit("attached text:=Name:","nativeclass:=Edit").Set "james"
.WinButton("text:=&Insert Order").click
End With
'

Script for open Record
With window("text:=Flight Reservation")
.WinMenu("menuobjtype:=2").Select "File;Open Order..."
with .Dialog("text:=Open Order")
.WinCheckBox("text:=&Order No.").Set "ON"
.WinEdit("window id:=1016").Set "1"
.WinButton("text:=OK").Click
End With
End With

Read more »

QTP-QC API and QTP AOM Scripts


Connect to QC and Add a New Defect
----------------------------------------------------
Dim qccon
Set qccon=CreateObject("TDApiOle80.TDConnection")
qccon.InitConnectionEx "http://qcserverurl:8080/qcbin"
qccon.login "username","password"
qccon.Connect "DEFAULT","QualityCenter_Demo"
Set BugFactory = qccon.BugFactory
Set Bug = BugFactory.AddItem(Nothing)
Bug.Status = "New"
Bug.Summary = "Error in login"
Bug.Priority = "4-Very High"
Bug.AssignedTo ="user1"
Bug.DetectedBy = "venkat"
Bug.Post
------------------------------------------------
Connect to QC and Read all the Defects and Write in Excel
-------------------------------------------------
Dim qc,bgf,bglist,xl,ws,b,r
Set qc=CreateObject("TDApiOle80.TDConnection")
qc.InitConnectionEx "http://localhost:8080/qcbin"
qc.login "admin", "mindq"
qc.Connect "DEFAULT","QualityCenter_Demo"
Set bgf = qc.BugFactory
Set bglist = bgf.NewList("")
Set xl=CreateObject("Excel.Application")
xl.WorkBooks.Add()
Set ws=xl.ActiveSheet
r=1
For Each b In bglist
ws.Cells(r, 1).Value =b.Field("BG_BUG_ID")
ws.Cells(r, 2).Value = b.Summary
ws.Cells(r, 3).Value = b.DetectedBy
ws.Cells(r, 4).Value = b.Priority
ws.Cells(r, 5).Value = b.Status
ws.Cells(r, 6).Value = b.AssignedTo
r=r+1
Next
xl.ActiveWorkbook.SaveAs("C:\QC_Demo_defects.xls")
xl.Quit
===========================================
 To open QTP Test and count the number of repositories associated
----------------------------------------------------------------
Dim app
set app=CreateObject("QuickTest.Application")
app.launch
app.visible=True
app.open "c:\test1",False
set r=app.Test.Actions("Action1").ObjectRepositories
msgbox "Total ORs :"&r.count
for i=1 to r.count
msgbox "Path of OR :"&r.item(i)
next
app.quit
set r=nothing
set app=nothing
------------------------------------------------------------------
To count the recovery scenarios associated to the test
-------------------------------------------------------------------
dim app
set app=CreateObject("QuickTest.Application")
app.launch
app.open "c:\test1",false
app.visible=True
set rs=app.Test.settings.Recovery
if rs.count>0 then
redim a(rs.count)
for i=0 to rs.count
a(i)=rs.item(i+1).name
i=i+1
next
end if
print "The recovery scenarios associated to the test are"
for i=0 to ubound(a)
print a(i)
next
----------------------------------------------------------
script to display the list of actions and their details
----------------------------------------------------------
Dim app
set app=CreateObject("QuickTest.Application")
app.launch
app.visible=True
app.open "c:\test1"
redim a(app.Test.Actions.count)
for i=1 to app.Test.Actions.count
a(i-1)=app.Test.Actions.item(i).name&" "&app.Test.Actions.item(i).type&" "&app.Test.Actions.item(i).location
next
for i=0 to ubount(a)
print a(i)
next
=========================================

Read more »