QTP Simply

What is default object synchronization timeout in QTP

2013-12-02T15:30:00.002-08:00

What is default object synchronization timeout in QTP

In QTP, object synchronization is required to ensure that objects are available before you perform any operation on them. In QTP default synchronization timeout is 20 seconds.

Example -

Suppose you have to click on a search button and after that application will display search results. In this scenario, you don't know how long it will take for application to populate the results.

So we must include synchronization in QTP script to ensure that we wait for enough amount of time so that we will have all result records available on the application.

To handle this situation, You can include below statement to wait for fixed amount of time.

wait 10 ' wait for 20 seconds.
Even if you don't mention this statement, QTP will wait for default synchronization time of 20 seconds.

Versions of QTP

2013-05-05T06:10:00.002-07:00

Versions of QTP

QTP 6.5:

To successfully install and run QTP6.5, following minimum system requirements are required :

Computer/Processor:	IBM-PC or compatible with a Pentium® II 266 MHz microprocessor (366 MHz recommended).
Operating System:	Windows^® 98 Second Edition, Windows^® 2000—Service Pack 3, Windows NT^® 4.0—Service Pack 6a, Windows^® Me, or Windows^® XP—Service Pack 1.
Memory:	128 MB of RAM (256 MB recommended)
Free Hard Disk Space:	150 MB of free disk space for a compact installation or 200 MB for a typical or complete installation
Browser:	Microsoft Internet Explorer 5.0–6.0.

Supported Environments

QuickTest Professional supports creating, recording, and running tests in the environments described below.

Ø Standard Windows Applications

1. Win32 API

2. MFC

Ø Visual Basic Applications

Visual Basic 6.0

Ø Browsers

Microsoft Internet Explorer 5.01–6.0 (required)
Netscape Navigator 4.06–4.7x (optional)
Netscape 6.1, Netscape 6.22, and Netscape 6.23 (optional)
AOL 5.0 and 6.0 (optional)

ActiveX Grid Controls

In addition to basic support of ActiveX properties and methods, QuickTest Professional supports context-sensitive recording and verification on the following ActiveX Grid controls:

Name	ProgId
FarPoint Spreadsheet 2.5	FPSpread.Spread.1
FarPoint Spreadsheet 3.0	FPSpread.Spread.2
FarPoint Spreadsheet 3.5	FPSpread.Spread.3
FarPoint Spreadsheet 6.0	FPSpread.Spread.4
FarPoint Spreadsheet 3.0 (OLEDB)	FPSpreadADO.fpSpread.2
FarPoint Spreadsheet 3.5 (OLEDB)	FPSpreadADO.fpSpread.3
FarPoint Spreadsheet 6 (OLEDB)	FPSpreadADO.fpSpread.4
Microsoft Grid 1.0	MSGrid.Grid
Microsoft DataBound Grid 5.0	MSDBGrid.DBGrid
Microsoft Flex Grid 6.0	MSFlexGridLib.MSFlexGrid.1
Sheridan Data Grid 2.0	SSDataWidgets.SSDBGridCtrlApt.1
Sheridan Data Grid 3.1	SSDataWidgets.SSDBGridCtrlApt.3
Apex True DataBound Grid 5.0	TrueDBGrid50.TDBGrid
Apex True DataBound Grid 6.0	TrueDBGrid60.TDBGrid
Apex True OLE DB Grid 6.0	TrueOleDBGrid60.TDBGrid

ActiveX Calendar Controls

In addition to basic support of ActiveX properties and methods, QuickTest Professional supports context-sensitive recording and verification on the following ActiveX Calendar controls:

Name	ProgId
Microsoft Date and Time Picker Control 6.0 (SP4)	MSComCtl2.DTPicker.2
Microsoft MonthView Control 6.0 (SP4)	MSComCtl2.MonthView.2

Multimedia Applications

QTP6.5 supports testing on the following multimedia applications:

Microsoft Windows MediaPlayer controls, version 6.0 and higher
RealPlayer controls supported for Internet Explorer browsers (the controls within applications containing browser controls are not supported)
Macromedia Flash 4 or 5 objects that are ActiveX controls in Internet Explorer. You can also test Macromedia Flash 6 clips containing only Flash 4 or 5 commands.

Additional Environments

QuickTest Professional add-ins support other environments such as Java, .NET Windows and Web Forms, SAP solutions, Oracle, Siebel, PeopleSoft, Web Services, and terminal emulator applications. For more information about QuickTest Professional add-ins, contact your sales representative or Mercury Interactive Customer Support.

Note for QuickTest Professional 6.0 and earlier:

Java support and Oracle support are now available as separate add-ins to QuickTest Professional 6.5 and are no longer part of the core product.

QTP 8.0:

System Requirements

To successfully install and run QTP8.0, you need the following minimum system requirements:

Computer/Processor:	IBM-PC or compatible with a Pentium II 266 MHz microprocessor (366 MHz recommended).
Operating System:	Windows 2000-Service Pack 3 or Service Pack 4, Windows XP-Service Pack 1, or Windows 2003 Server.
Memory:	128 MB of RAM (256 MB recommended).
Free Hard Disk Space:	250 MB of free disk space for application files and folders, and an additional 120 MB of free disk space on the system disk (the disk on which the operating system is installed). After Quick Test Professional is installed, it is recommended to have at least 150 MB free disk space on the system disk for the operating system and Quick Test Professional to run correctly.
Browser:	Microsoft Internet Explorer 5.5 Service Pack 2-6.0.

Supported Add-ins

The following external QuickTest 6.5.x add-ins are supported for use with QuickTest Professional 8.0:

Java Add-in 6.5
Oracle Add-in 6.5
PeopleSoft Add-in 6.5
Terminal Emulator Add-in 6.5
.NET Add-in 6.5.1
SAP solutions Add-in 6.5.1

Note: Siebel Add-in 6.5, the .NET Add-in 6.5, the Add-in for SAP solutions 6.5, or any 6.0 add-ins,cannot be used with QuickTest Professional 8.0.1

Supported Environments and Programs

QuickTest Professional 8.0 supports creating, recording, and running tests or components using the environments and programs described below.

Ø Standard Windows Applications

1.Win32 API

2.MFC

Ø Visual Basic Applications

Visual Basic 6.0

Note: Visual Basic .NET applications are supported by the QuickTest Professional .NET Add-in.

Ø Browsers

Microsoft Internet Explorer 5.5 Service Pack 2-6.0 (required)
Netscape 6.1, Netscape 6.22, Netscape 6.23, Netscape 7.02, and Netscape 7.1 (optional)
AOL 8.0 and 9.0 (optional)

ActiveX Grid Controls

In addition to basic support of ActiveX properties and methods, QuickTest Professional supports context-sensitive recording and verification on the following ActiveX Grid controls:

Name	ProgId
FarPoint Spreadsheet 2.5	FPSpread.Spread.1
FarPoint Spreadsheet 3.0	FPSpread.Spread.2
FarPoint Spreadsheet 3.5	FPSpread.Spread.3
FarPoint Spreadsheet 6.0	FPSpread.Spread.4
FarPoint Spreadsheet 3.0 (OLEDB)	FPSpreadADO.fpSpread.2
FarPoint Spreadsheet 3.5 (OLEDB)	FPSpreadADO.fpSpread.3
FarPoint Spreadsheet 6 (OLEDB)	FPSpreadADO.fpSpread.4
Microsoft Grid 1.0	MSGrid.Grid
Microsoft DataBound Grid 5.0	MSDBGrid.DBGrid
Microsoft Flex Grid 6.0	MSFlexGridLib.MSFlexGrid.1
Sheridan Data Grid 2.0	SSDataWidgets.SSDBGridCtrlApt.1
Sheridan Data Grid 3.1	SSDataWidgets.SSDBGridCtrlApt.3
Apex True DataBound Grid 5.0	TrueDBGrid50.TDBGrid
Apex True DataBound Grid 6.0	TrueDBGrid60.TDBGrid
Apex True OLE DB Grid 6.0	TrueOleDBGrid60.TDBGrid

ActiveX Calendar Controls

In addition to built-in support for ActiveX properties and methods, QuickTest Professional supports context-sensitive recording and verification on the following ActiveX Calendar controls:

Name	ProgId
Microsoft Date and Time Picker Control 6.0 (SP4)	MSComCtl2.DTPicker.2
Microsoft MonthView Control 6.0 (SP4)	MSComCtl2.MonthView.2

Microsoft Excel

When using Microsoft Excel files with QuickTest Professional 8.0(for example, to import or export data to or from the Data Table), you can work with Microsoft Excel 2000, 2002, 2003, and XP.

Microsoft Query

When using Microsoft Query with QuickTest Professional 8.0 (for example, for Database checkpoints), you can work with Microsoft Query 2000, 2002, 2003, and XP.

Additional Environments

QuickTest Professional add-ins support other environments such as Java, .NET Windows and Web Forms, SAP Solutions, Oracle, Siebel, PeopleSoft, Web Services, and terminal emulator applications. For more information on QuickTest Professional add-ins, contact your sales representative or Mercury Interactive Customer Support.

function to check for time in hh:mm

2013-05-05T06:09:00.002-07:00

'*****************************************
'function to check for time in hh:mm
'****************************************
Function fnTimeFormat(strTime)
'arrTime(0)="hh:mm"
' arrTime(1)="AM" or "PM"
'arrTime(2)="TZ"
' arrSplit(0)="HH"
' arrSplit(1)="MM"
arrTime=split(strTime," ")
arrSplit=split(arrTime(0),":")

if((arrSplit(0)>=0 and arrSplit(0)<=12) and (arrSplit(1)>=0 and arrSplit(1)<=60) and (arrTime(1)="AM" or arrTime(1)="PM") and (LEN(arrTime(2))=3)) then
retVal=1
else
retVal=0
end if
fnTimeFormat=retVal
End Function

Naming conventions

2013-05-05T06:08:00.003-07:00

Naming conventions

The Conventions for Naming for test cases, Scripts and Actions vary from Project to Project depending upon the Client.

4.1 Test Case Naming Conventions:

Test cases should be named in a manner that enables easy identification of the corresponding Use case (or the Scenario) for which the Test Case is written. The Onlooker should be able to trace the test case back to the use cane name or Scenario name by the name of the Test Case. Consistency should be maintained in following the hierarchy of naming.

Example 1: Considering that Each Use case is associated with one Test case. If the name of the Use Case were UC_001 then the Test case name would be TC_001.

Example 2: In the Unilever Automation Project, SAP transactions are divided into different modules, in those modules different transactions are grouped together as a scenario, so for writing the test case for a particular scenario naming convention used is module name followed by scenario name.

For Module IMWM, if S014_01 is the scenario name, so name of the test case for the S014_01 scenario was given as IMWM_S014_01.

4.2 Script and Action Naming Conventions:

Similar to the Test case naming, Script naming should be done consistently with clarity and traceability. Typically each Test Script is prepared corresponding to each Test Case. Every Test Case contains one or more Conditions. Each Condition can be represented by an action in the script.

Therefore for a Test Script corresponding to a Test Case named TC_001 would be QTS_001.The hierarchy should be maintained in case the use cases or test cases are nested.

E.g.: TC_01_014 would have a QTP Test Script as QTS_01_014.

Action Naming:

Each Test Script can contain one or more Actions, with one or more actions representing a test Condition.

Actions can be named in 2 ways:

Functionality of the Action
Hierarchy of the Action in the Test Script.

Functionality of the Action:

Typically Actions are segregated by their functionality in the Test Script. Therefore it would be easier to understand the Action if the name of the action represents the Functionality.

For E.g.: An Action written or recorded for logging the user should be named as Login orAuthentication for easy understandability.

An Action for booking tickets should be named as Book_Tickets

An Action for exiting the application named as Exit.

This also adds a huge advantage when the Actions are made reusable. Reusable Actions can be used between various scripts. When an Action is to be made reusable the action should be named as REUSE_(Action name).

Example: REUSE_Login.

2. Hierarchy of the Action in the Script:

Since Actions are a part of the Test Script, for purpose of Clarity and tracking, Actions can be named as per Hierarchy.

For e.g.: Test Case Name à TC_01

QTP Test Script Name à QTS_01

Name of 1^st action in the Script à QTS_01_01

Similarly Name of 9^th Action in the ScriptàQTS_01_09

4.3 Variables and Constants:

QTP Scripts are in VB Script. Therefore, the naming conventions for variables can be followed alike VB Script Naming Conventions.

General Conventions followed in VBScript are:

Data Type Prefixes:

By using data type prefixes, your variables always indicate what they are designed for. I’m using just six prefixes:

Prefix	Data Types	Example
b	Boolean (true or false)	bChecked = True
d	Date/time	dStartTime = Now
i	All numeric data types (Byte, Integer, Currency, Long, Single, Double)	iTax = iPrice * 0.076
o	Objects	Set oFile = Nothing
s	Strings	sTitle = “Welcome!”
u	User interface elements	uPara.style.display = “block”

Constants Prefix:

Usually there are only a handful of constants in any scripts. Indicating the data type therefore is less important for constants. Prefix letter c for all constants can be used.

e.g. Const cTitle = “Welcome!”

UDocument.title = cTitle

4.4 DataSheet Naming and Parameter Naming Conventions:

Every QTP Test Script contains 2 types of sheets.

Global data sheet
Local data sheets

àThe Global data sheet, which is a common sheet for all the actions of the script, is named by default as dt_globalsheet. This can be renamed as Global for all the Scripts for consistency.

àTypically, Each Action in the Script contains one data sheet, which is local to the Action. This is by default, named after the Action to which it belongs. Therefore the name of the datasheet follows directly the name of the Action, which when named following its naming conventions, can be used efficiently for the data sheet too.

Parameter Naming:

Various Types of Parameters used in QTP are:

1) Test Parameters

a) Test Input Parameters: These should be named as IN_(relevant variable name). ‘In’ denoting that it’s an input parameter for the Test in whole. The name following IN should be a relevant name for the variable, denoting the purpose of its use. This should also comply with the standard variable naming conventions.

Example: IN_bFlag, IN_iIncrement etc.,

b) Test Output Parameters: On the similar lines of Input Parameters, these should be named as OUT_(relevant variable name). OUT representing that it’s an output parameter.

Example: OUT_sStatus.

2) Action Parameters

a) Action Input Parameters: These are local to Action of a Test. These can be named asACTIN_(variable name). ACTIN denoting that it’s an Action Input Parameter.

Example: ACTIN_iResult

b) Action Output Parameters: These could be named as ACTOUT_(var name).

Example: ACTOUT_bFlag

3) Environment Variables:

Environment variables are either built-in or User defined. Built-in variables cannot be declared named by the user, so their naming convention is not discussed.

User Defined Environment Variables are either Internal or External.

Internal Variables: ENV_INT_(variable name)

External Variables: ENV_EXT_(Variable name)

4.5 Function Naming Conventions

Functions should be named as Func_(name). This can provide clarity and difference between a Reusable Action and a Function that can be used within Actions.

Example: Func_Save , Func_Add

function to check for date format in mm/dd/yyyy

2013-05-05T06:06:00.001-07:00

********************************************************
'function to check for date format in mm/dd/yyyy
'*******************************************************
Function fnDateFormat(strdate)
Set regEx = New RegExp
datePattern = "((0[1-9]|1[0-2])0[1-9]|[12][0-9]|3[0-1])/([0-9]{4})"
'Set pattern.
regEx.Pattern = datePattern
'Ignore case
regEx.IgnoreCase = True
'Match complete string or not
regEx.Global = MatchCompleteString

'Test the regular expression
IsRegEqual = regEx.Test(strdate)
Set regEx = Nothing
fnDateFormat=IsRegEqual
End Function

Automating Word Document- 1

2012-12-17T02:54:00.005-08:00

How to print all words in a word document?
Dim oWord, Doc, currentDocument
Doc = "C:\Desktop\Test.doc" 'contains 200 words
Set oWord = CreateObject("Word.Application")
oWord.DisplayAlerts = 0
oWord.Documents.Open Doc
Set currentDocument = oWord.Documents(1)
Dim nWords, n
nWords = currentDocument.Words.count
Print "Number of Words: " & nWords
For n = 1 to nWords
Print currentDocument.Words(n)
Next
currentDocument.Close
Set currentDocument = Nothing
oWord.Quit
Set oWord = Nothing
********************************************
How to count number of pages in a word document?
Below lines of code shows how to find total number of pages in a word document:
SystemUtil.CloseProcessByName("WINWORD.exe")
Dim oWord, Doc
Doc = "C:\Desktop\Test.doc" 'contains 20 pages
Set oWord = CreateObject("Word.Application")
oWord.Documents.Open doc
Dim nPages
nPages=oWord.ActiveDocument.BuiltInDocumentProperties("Number of pages")
msgbox nPages ' will display total number of pages
ActiveDocument.Close
Set ActiveDocument = Nothing
oWord.Quit
Set oWord = Nothing

Killing a Process

2012-12-17T02:54:00.002-08:00

Below is the function that is used to kill any process:
Public Function fnProcessKill (ByVal strProcess)
Dim FunctionName: FunctionName = UCase ("fnProcessKill")
Dim strPreFix: strPreFix = "In " & pcThisLib & " - " & FunctionName & ","
Set objSWbemServices = GetObject("winmgmts:")
Set colSWbemObjectSet = objSWbemServices.ExecQuery("SELECT * FROM Win32_Process Where Name = '"& strProcess &"'")
If colSWbemObjectSet.Count > 0 Then
For i = 1 to colSWbemObjectSet.Count
SystemUtil.CloseProcessByName(strProcess)
Next
Else
fnProcessKill = micFail ' Did not find the process.
End If
Set objSWbemServices = Nothing ' Clear object from memory.
Set colSWbemObjectSet = Nothing ' Clear object from memory.
End Function

Function to close All Browsers except ALM

2012-12-17T02:53:00.006-08:00

'Name: platform_web_CloseAllBrowsersExceptALM ()
'Desc: Closes all browsers except ALM

'Date Created:
'Author:
'Input Parameters: i

Public Sub platform_web_CloseAllBrowsersExceptALM ()
Call CloseAllBrowsersExceptALM ()
End Sub

Public Sub CloseAllBrowsersExceptALM ()
'Clean up the open browser windows from previous test
Dim vcol_Handles, vCtr, vHwnd, Flag, vLastHWnd,sCompare
vCtr = 0
Flag = 1

Set vcol_Handles = CreateObject("Scripting.Dictionary")
While (Window("regexpwndclass:=IEFrame","index:=" & vCtr).Exist(0) And Flag)
'wait 1
vHwnd = Window("regexpwndclass:=IEFrame","index:=" & vCtr).getroproperty("Hwnd")
If (vLastHWnd=vHwnd) Then
Flag = 0
Else
vcol_Handles.Add CStr(vcol_Handles.Count),vHwnd
vCtr = vCtr+1
End If
vLastHWnd = vHwnd
Wend

'Use reverse order in this for loop so that the text and Hwnd remain in correct order after each is closed
For vCtr = vcol_Handles.Count-1 to 0 step -1
vHwnd = vcol_Handles.Item(CStr(vCtr))

' Determine if the browser window has the word ALM in the caption bar
sALMCompareString = "HP Application Lifecycle Management"

sCompare=Instr(Window("hwnd:=" &vHwnd).getroproperty("title"),sALMCompareString)
'sCompare=Instr(Window("hwnd:=" &vHwnd).getroproperty("title"),"Quality Center")
' If it doesn't or the title bar is empty, close the window
If (sCompare=0) or (IsNull(sCompare)) then
Window("hwnd:=" &vHwnd).Close
End If
Next
End Sub

Function to sort Web table by COLUMN NAME in ASCending or DESCending order

2012-12-17T02:53:00.003-08:00

sColumn_Name="Type/"

'declaring variables

Dim arrDCol(1000)

Dim arrDSortCol(1000)

Dim arrCol(1000)

Dim arrSortCol(1000)

If Browser("").Page("").WebTable("").Exist(5) Then

intRowcnt = Browser("").Page("").WebTable("").RowCount

intColcnt = Browser("").Page("").WebTable("").ColumnCount(1)

' adding and comparing table headers

Set ColList = CreateObject("System.Collections.ArrayList")

j=0

For j = 3 to intColcnt

Set objCmp = Browser("").Page("").WebTable("")

strCol= trim(objCmp.GetCellData(1,j))

if(instr(strCol,sColumn_Name)) then

sFinColumn_Name=sColumn_Name

sFinColNo=j

Exit FOR

end if

‘clicking on table column header which you want to sort in ascending order

set oLink=Browser("").Page("").WebTable("").ChildItem(1,sFinColNo,"Link",0)

Browser("").Page("").Sync

Set AppDataList = CreateObject("System.Collections.ArrayList")

Set SortASCList = CreateObject("System.Collections.ArrayList")

Set SortDESCList = CreateObject("System.Collections.ArrayList")

i=0

If intRowcnt>1 Then

For i = 3 to intRowcnt

Set objCmp = Browser("").Page("").WebTable("")

AppDataList.Add trim(objCmp.GetCellData(i,sFinColNo))

AppDataList.remove("")

AppDataList.TrimToSize

SortASCList.Add trim(objCmp.GetCellData(i,sFinColNo))

SortASCList.remove("")

SortASCList.TrimToSize

SortASCList.Sort

n = 0

For each se in AppDataList

arrCol(n) = se

n = n +1

m = 0

For each ses in SortASCList

arrSortCol(m) = ses

m = m +1

i=0

For i = 0 to n

If trim(arrCol(i)) <> trim(arrSortCol(i)) then

sortFlag = sortFlag+1

strMatch = strMatch&"Unsorted : "&arrCol(i)& "- Sorted in ascending order : "&arrSortCol(i)&";"

Else

strMatch = strMatch&"sorted : "&arrCol(i)& "- Sorted in ascending order : "&arrSortCol(i)&";"

End If

If sortFlag>0 Then

Reporter.ReportEvent micFail, " Table data is not displayed in sorted order - Ascending","" &strMatch

Else

Reporter.ReportEvent micPass, " Table data is displayed in sorted order - Ascending ","" &strMatch

End If

'sortin in descending order

set oLink=Browser("").Page("").WebTable("").ChildItem(1,sFinColNo,"Link",0)

oLink.Click

Browser("").Page("").Sync

Set DESCList = CreateObject("System.Collections.ArrayList")

i=0

For i = 3 to intRowcnt

Set objCmp = Browser("").Page("").WebTable("")

DESCList.Add objCmp.GetCellData(i,sFinColNo)

DESCList.remove("")

DESCList.TrimToSize

SortDESCList.Add trim(objCmp.GetCellData(i,sFinColNo))

SortDESCList.remove("")

SortDESCList.TrimToSize

n = 0

For each se in DESCList

arrDCol(n) = se

n = n +1

SortDESCList.Sort

SortDESCList.Reverse

m = 0

For each ses in SortDESCList

arrDSortCol(m) = ses

m = m +1

strMatch=""

sortFlag=0

i=0

For i = 0 to n

If trim(arrDCol(i)) <> trim(arrDSortCol(i)) then

sortFlag = sortFlag+1

strMatch = strMatch&"Unsorted : "&arrDCol(i)& "- Sorted in descending order : "&arrDSortCol(i)&";"

Else

strMatch = strMatch&"sorted : "&arrDCol(i)& "- Sorted in descending order : "&arrDSortCol(i)&";"

End If

If sortFlag>0 Then

Reporter.ReportEvent micFail, " Table data is not displayed in sorted order - Descending","" &strMatch

Else

Reporter.ReportEvent micPass, " Table data is displayed in sorted order - Descending ","" &strMatch

End If

else

Reporter.ReportEvent micWarning, " No data available to sort",""

End If

else

Reporter.ReportEvent micWarning, " No table exists",""

End If

Queries,Code Writing in QTP

2012-12-17T02:53:00.000-08:00

Hi Everyone,
If you have any queries in QTP or looking for assistance in code /logic Please do describe the issue in the comments section.Your queries will be resolved ASAP.
Ankur Jain

Function to create File shortcut

2012-12-17T02:52:00.002-08:00

Fn_FileShortcut()
Set WshShell=createobject(“WScript.shell”)
strDesktop=WshShell.SpecialFolders(“Desktop”)
set appConfigShortcut=WshShell.CreatShortcut(strDeskTop & “\AppConfig.lnk”)
appConfigShortcut.TargetPath=”D:\QTP\Test.txt”
appConfigShortcut.IconLocation=”notepad.exe”
appConfigShortcut.HotKey=”CTRL+ALT+C”
appConfigShortcut.WindowStyle=1
appConfigShortcut.Description=”Application config file”
appConfigShortcut.WorkingDirectory=strDesktop
appConfigShortcut.Save

Code Optimisation in QTP

2012-12-17T02:51:00.001-08:00

Hi Everyone,
I am looking for suggestions to optimisation in QTP.Please share if you have any :)

Clicking an item inside Table

2012-08-16T10:50:00.000-07:00

Here is the post that discusses how to click an item inside table.

It may be possible that when you are automating page containing web table it will contain objects such as links, images etc.We may require to click such objects and write code for it.

For such condition we can use below code:

Set otable=browser(“browser”).Page(“page”).WebTable(“table”)

table.ChildItemCount(1,1,”Link”)

If icount=1 Then

Set olink=otable.ChildItem(1,1,”link”,0)
olink.click
End If

Explanation of above code

‘setting object to table that contains links/images

Set otable=browser(“browser”).Page(“page”).WebTable(“table”)

‘using child item count inbuilt function

‘this function will count the number of objects in a cell

‘here (1,1) tells about 1st row and 1st column and value in double codes tells about type of “object” that we are looking for.

icount=otable.ChildItemCount(1,1,”Link”)

‘here we used child item inbuilt function.(1,1) signifies 1st row and column or any other cell that contains object that we want to click.”0″ specifies first link in cell to be clicked.

Set olink=otable.ChildItem(1,1,”link”,0)

if cell contains 2 links then we can use code line as below to click on second link.

Set olink=otable.ChildItem(1,1,”link”,1)

‘it will click on the link
olink.click

We can use “image instead of “link” to click on an image in cell( 1, 1) as shown below:

Set oImage=otable.ChildItem(1,1,”image”,0)

‘it will click on the image
oImage.click
Please feel free to ask any questions.I will resolve all queries within 24 hrs.

2012-04-29T23:14:00.001-07:00

New features in QTP 12(possibly)

Below are some new features than can possibly be added in next version of QTP.

We hope that this will make QTP better product and easy to create effective automated scripts.
* New improved IDE with IntelliSense for classes

This will help in writing code faster.

* Multiple Document Interface (MDI) features for opening multiple tests within QTP

QTP had limitation of working on one test at a time.This will eliminate that problem.

* Integration of BPT as well as Service Test into QTP (giving rise to the name, UFT)

* Insight — an innovative, new image-recognition feature for carrying out image-based automation

* New canvas for designing test flow

Details shared by Tarun Lalwani. Check his rendezvous with HP Israel team

I will update you soon with more details.