RSS
 

Posts Tagged ‘Quick Test Professional (QTP)’

#27: How to modify script in QTP debug mode

25 Nov

The only thing that I do not like in QTP is scripts are read only in debug mode: if an error pop up during a playback in QTP, and I choose to “Debug”, then I can not modify anything since the script is read only.

However, TestPartner is much more convenient in this particular area, since its scripts can be modified during debug mode: once you choose to debug, the playback is paused, and you can modify your script, and drag the current step indicator (i.e., the yellow arrow) to the line where you want the script to resume.

The only work around in QTP debug mode is to use the Command tab in the Debug Viewer:

Using the Debug Viewer
You use the Debug Viewer pane to view, set, or modify the current value of objects or variables in your function library, when it stops at a breakpoint, or when a step fails and you select the Debug option. The Debug Viewer is useful for debugging operations (functions) in a business component, but is not intended for use with other types of component steps.

To open the Debug Viewer pane:

Choose View > Debug Viewer. The Debug Viewer pane opens.

The Debug Viewer tabs are used to display the values of variables and objects in the main script of the selected subroutine.

Command Tab
Use the Command tab to execute a line of script in order to set or modify the current value of a variable or VBScript object in your function library. When the run continues, QuickTest uses the value that you set.

A detailed example about how to use the Debug Viewer and its Watch Tab, Variables Tab, and Command Tab can be viewed from here.

 
No Comments

Posted by Jia Qi in Quick Test Professional (QTP), TestPartner (TP)

 

#26: Error handling in VBScript (QTP)

24 Nov

In post#13 and post#23, we talked about how to do error handling in Visual Basic of Application (VBA), which is the scripting language for TestPartner. In today’s post, we will discuss how to handle errors in VBScript, which is the scripting language for QTP.

In VBA, there are 3 error handling statements (for the meaning of these statements, please refer to post#13 or post#23.):

1, On Error GoTo line
This statement is NOT supported by VBScript, but you can use a subroutine to handle error output . See the script below.

Const adOpenDynamic = 2
Const adLockOptimistic = 3
Const adCmdTableDirect = 512

Set cn = CreateObject("ADODB.Connection")
Set rs = CreateObject("ADODB.Recordset")
Set errorObject = CreateObject("ADODB.Error")

On Error Resume Next
cn.Provider = "sas.localprovider.1"
cn.Properties("Data Source") = "c:\testdata"

cn.Open
rs.Open "lostDataset", cn, adOpenDynamic, adLockOptimistic, adCmdTableDirect
DisplayErrorInfo
rs.Close
cn.Close

sub DisplayErrorInfo()
  For Each errorObject In rs.ActiveConnection.Errors
    MsgBox "Description: " & errorObject.Description & Chr(10) & Chr(13) & _
           "Number:      " & Hex(errorObject.Number)
  Next
End Sub

2, On Error Resume Next
This statement is supported by VBScript.

3, On Error GoTo 0
This statement is supported by VBScript.

============================================

More reading material:
Error Handling in VBScript, Part One
Error Handling In VBScript, Part Two
Error Handling in VBScript, Part Three
To Err Is VBScript – Part 1
To Err Is VBScript – Part 2
Handling Error Objects

 
No Comments

Posted by Jia Qi in Quick Test Professional (QTP)

 

#25: Differences of Funtion that returns array in VBScript and VBA

17 Nov

To create and call a Function that returns array in VBScript and VBA are slightly different (QTP uses VBScript and TestPartner uses VBA):

In VBA,

Function GetExcelSheetData(FilePath As String, SheetName As String)
Dim CellArray() As String 'A dynamic array that is not sized in the Dim statement
... Calculate RowCount and ColumnCount
ReDim CellArray(RowCount, ColumnCount) As String
... Populate data in CellArray
GetExcelSheetData = CellArray()
End Function

Sub Main()
Dim SheetData() As String 'Dynamic array
.. Calculate RowCount and ColumnCount
ReDim SheetData(RowCount, ColumnCount) As String
SheetData() = Function_GetExcelSheetData.GetExcelSheetData(ExcelFilePath_MeasurementTab, "Package")

In VBScript,

Function Function_ImportExcelToArray(FilePath, SheetName)
Dim CellArray 'A dynamic array that is not sized in the Dim statement
... Calculate RowCount and ColumnCount
ReDim CellArray(RowCount, ColumnCount)
... Populate data in CellArray
Function_ImportExcelToArray = CellArray
'Note: if write "Function_ImportExcelToArray = CellArray()",
'then will get error "Subscript out of range: 'CellArray'".
End Function

Sub Sub_LoginRedirect()
Dim PageURL
'DO NOT write "PageURL()",
'otherwise, will get error "type mismatch".
.. Calculate RowCount and ColumnCount
ReDim PageURL(RowCount, ColumnCount)
PageURL = Function_ImportExcelToArray(InputExcel, "Sub_LoginRedirect")
'Note: if write "PageURL() = Function_ImportExcelToArray(InputExcel, "Sub_LoginRedirect")",
'then will get error "Subscript out of range: 'PageURL'".

Conclusion, in VBScript, do not use Array with empty brackets, such as Array(), but you can use not-empty brackets, such as Array(1, 2).

===========================================================

More information about Array in VBScript:

Much of the time, you only want to assign a single value to a variable you have declared. A variable containing a single value is a scalar variable. Other times, it is convenient to assign more than one related value to a single variable. Then you can create a variable that can contain a series of values. This is called an array variable. Array variables and scalar variables are declared in the same way, except that the declaration of an array variable uses parentheses ( ) following the variable name. In the following example, a single-dimension array containing 11 elements is declared:

Dim A(10)

Although the number shown in the parentheses is 10, all arrays in VBScript are zero-based, so this array actually contains 11 elements. In a zero-based array, the number of array elements is always the number shown in parentheses plus one. This kind of array is called a fixed-size array.

You assign data to each of the elements of the array using an index into the array. Beginning at zero and ending at 10, data can be assigned to the elements of an array as follows:

A(0) = 256
A(1) = 324
A(2) = 100
. . .
A(10) = 55

Similarly, the data can be retrieved from any element using an index into the particular array element you want. For example:

. . .
SomeVariable = A(8)
. . .

Arrays aren’t limited to a single dimension. You can have as many as 60 dimensions, although most people can’t comprehend more than three or four dimensions. You can declare multiple dimensions by separating an array’s size numbers in the parentheses with commas. In the following example, the MyTable variable is a two-dimensional array consisting of 6 rows and 11 columns:

Dim MyTable(5, 10)

In a two-dimensional array, the first number is always the number of rows; the second number is the number of columns.

You can also declare an array whose size changes during the time your script is running. This is called a dynamic array. The array is initially declared within a procedure using either the Dim statement or using the ReDim statement. However, for a dynamic array, no size or number of dimensions is placed inside the parentheses. For example:

Dim MyArray()
ReDim AnotherArray()

To use a dynamic array, you must subsequently use ReDim to determine the number of dimensions and the size of each dimension. In the following example, ReDim sets the initial size of the dynamic array to 25. A subsequent ReDim statement resizes the array to 30, but uses the Preserve keyword to preserve the contents of the array as the resizing takes place.

ReDim MyArray(25)
. . .
ReDim Preserve MyArray(30)

There is no limit to the number of times you can resize a dynamic array, although if you make an array smaller, you lose the data in the eliminated elements.

 
No Comments

Posted by Jia Qi in Quick Test Professional (QTP), TestPartner (TP)

 

#22: Decrease the disk space used by QTP

23 Oct

I am developing a set of automated test scripts for the YouPlayOff webset in QTP, and notice that the script files will take a lot of (may be too much) disk space eventually. I reviewed the default test folder structure in QTP, and found the following problems:

1, Script files in the Test folder can be big:
- An empty Object Repository file takes 192K space (if not empty, will take more space). Each Test folder contains at least 2 actions, i.e., Action0 and Action1, and each action has 1 Object Repository file. As a result, an empty Test folder costs 192K*2=384K space just because the Object Repositories. If there are more actions in the Test folder, the Object repository files will take more space.
- The Excel file, i.e., the Data Table, also takes too much space. Each action use one Excel sheet, and the actions that were called by the main action also has their own Excel sheets. In a complex test, Excel files may take up to 4MB space.

2, Script files in the Test folder are too many:
A simplest QTP test script contains 4 folders, 15 files, and the number of files increases as the number of Action increases.

Due to the above 2 problems, a finished QTP project may take 700-800MB space, and contain thousands of script files. This will make the scripts difficult to maintain and to do the version control, and if we want to transfer the scripts to other computers, it will take a long time.

However, if instead of
- Reuse actions (Action is saved in a folder contains multiple files)
- Use Local Object Repository for each action
- Use Local Excel Sheet (i.e., Data Table) for each action
We
- Reuse functions (Function is a single file)
- Use Shared Object Repository for multiple scripts (Reduce the number of Object Repository files)
- Use Shared Excel File with multiple sheets (Reduce the number of Excel files)
then the number of script files in the QTP project will decrease dramatically, and the size of the QTP project can be decreased to 10MB.

Now, I will explain how to do this in detail:
First, record and modify your script, then save it as “Action xyz”. Open the folder of “Actions xyz”, you will find an Excel file – “Default.xls” for the Data Table information, and there are 2 sub-folders: i.e., Action0 and Action1. Action0 is a default action created by QTP, and Action1 is the real action that created by you. if you are interested in understanding more about the difference between Action0 and Action1, please click here. Within the folder of Action1, you will see a file called as “ObjectRepository.bdb” which is the local ObjectRepository for this Action. Blow is an indication of the layout of the “Action xyz” folder.

  • folder “Action xyz”

    • folder Action0
    • folder Action1
      • ObjectRepository.bdb
      • other stuff
    • Default.xls
    • other stuff

 

Second, in QTP, choose File-New-Function Library, copy the code from “Action xyz” and paste it to this new Function Library, modify it to either Sub or Function. For how to write a Sub and Function, please see here. Save the Function Library as “Sub xyz” or “Function xyz”. Save them as *.qfl, *.vbs, or *.txt doesn’t matter, they will behave the same. Open the folder where “Sub xyz” or “Function xyz” is saved, you will find out, compare to “Action xyz” (which is a folder with multiple files and sub-folders), “Sub xyz” or “Function xyz” is just a single file!

Third, create a driver Action for your project. This action will be the only action for your project, and it will function as the entry point of your project. All the other scripts are saved as either Subs or Functions in the project, and these Subs and Functions will be executed by the driver Action. The driver Action is a normal Action, and it has same layout as “Action xyz”, i.e., 2 sub-folders and some files, but since all the other scripts are saved as single files (*.qfl, *.vbs, or *.txt), so the total disk space used will be decreased a lot! Now you know, one project actually only needs one Action folder! This is probably why we can only open a single Action in QTP.

The script of the Sub, Function, and driver Action may look like this:

“Function xyz.qfl”:

   Function function_xyz(inputs)
      some statements
      function_xyz = some value
      some statements
   End Function

“Sub xyz.qfl”:

   Sub sub_xyz()
      some statements
      Call function_xyz(inputs)
      some statements
   End Sub

“driver Action”:

   Call sub_xyz()

Forth, associate the Subs and Functions with the driver Action (open Subs, Functions and the driver Action in QTP, right click inside the editing area of the Sub or Function, click the last item in the pop-up menu to associate with the driver Action). Note: if the Subs and Functions are not in the same folder of the driver Action, or the Subs and Functions are in different folders, you should still be able to associate them with the driver Action.

Fifth, set up the Object Repository for the driver Action. Currently, the “ObjectRepository.bdb” file within the Action1 folder in the driver Action folder is 192Kb, i.e., it is empty. Since the Object Repository is empty, the driver Action can not be run. We can use existing Object Repositories from recorded actions to create Object Repository for the driver Action. For example, we recorded ActionX, ActionY, and ActionZ, and have transferred them to SubX, FunctionY, and SubZ. Say the Object Repositories for ActionX, ActionY, and ActionZ are “ObjectRepositoryX.bdb”, “ObjectRepositoryY.bdb” and “ObjectRepositoryZ.bdb”, respectively.

  • step1, open ActionX, and choose Resources-Object Repository. From the Object Repository window, choose File-Export Local objects. Export it to “ObjectRepositoryX.tsr”. *.bdb is local Object Repository file, and *.tsr is shared Object Repository file.
  • step2, repeat step1 for “ObjectRepositoryY.bdb” and “ObjectRepositoryZ.bdb”, export them to “ObjectRepositoryY.tsr” and “ObjectRepositoryZ.tsr”, respectively.
  • step3, open the driver Action, and choose Resources-Object Repository Manager. From the Object Repository Manager window, choose Tools-Object Repository Merge Tool. In the Object Repository – Merge Tool window, choose to merge “ObjectRepositoryX.tsr” and “ObjectRepositoryY.tsr”, and save the merge result as “ObjectRepositoryXY.tsr”.
  • step4, repeat step3 for “ObjectRepositoryXY.bdb” and “ObjectRepositoryZ.bdb”. Save the merge result as “ObjectRepositoryXYZ.tsr”.
  • step5, move “ObjectRepositoryXYZ.tsr” into the Action1 folder of the driver Action folder, and delete “ObjectRepository.bdb” inside the folder, and rename “ObjectRepositoryXYZ.tsr” as “ObjectRepository.bdb”.

 

Now, the driver Action can be run properly.

Sixth, combine “Default.xls” files from different recorded actions into one excel file (multiple sheets), and save it under the driver Action’s folder. Modify the scripts of Subs and Functions to cope with the excel file. If you want to import data from the excel file to an array, please see post#9. If you want to export data from array to an excel sheet, please refer to post#16.

Seventh, if there are checkpoints in the recorded Actions, you need to transfer them into normal VBScript, since QTP checkpoints won’t work for Subs nor Functions, i.e., checkpoints created by QTP won’t be recognized by *.qfl, *.vbs, nor *.txt file.

=========================================================

You can download an example folder structure and code by clicking here. In the “Tests_YouPlayOff” folder, the “YouPlayOff” folder is the driver action folder, which you can loaded in QTP as a test. In the Action1, there are only two lines of code:

Call Sub_LoginNonconfirmed()
Call Sub_LoginRedirect()

The “Sub_LoginNonconfirmed()” is saved as a *.qfl file, which can be opened from notepad, or opened in QTP as a function library. This “Sub_LoginNonconfirmed.qfl” is a substitution of the test/action mentioned in post#6, and in this sub, “Sub_Login.qfl” is called.

The “Sub_LoginRedirect()” is also saved as *.qfl file, and it is a substitution of the test/action mentioned in post#5. In the “Sub_LoginNonconfirmed.qfl” file, “Sub_Login.qfl” and 3 functions are called. The 3 functions are “Function_ExcelColumnCount.qfl”, “Function_ExcelRowCount.qfl”, and “Function_ExportArrayToExcel.qfl”, and they are used to import data from Excel “Input.xlsx” to the sub. The Excel is a substitution of the Data Table, and the location of the Excel is defined in “Constant.qfl” which is used in “Sub_LoginNonconfirmed.qfl”.

 
No Comments

Posted by Jia Qi in Quick Test Professional (QTP)

 

#20: Test Image View in Windows Application

09 Sep

When I started this blog, I said I will show how to use QTP to test a website, and how to use TestPartner (TP) to test a windows application. I also said the main focus will be QTP instead of TP, since there is place to download QTP for free but no place to download TP, and you will have access to the website but won’t have access to the windows application.

However, beside a few posts (post#4, post#5, post#6)about how to test the login function of the website by QTP, most of my posts (until now) are about TP and testing an image processing work station. Today, I decided to end the testing of the work station, and from tomorrow, I will switch back to use QTP to test the website.

I want to give a summary of the test architecture I designed for the workstation test before I move on to test the website:

The object and scope of the test is to test all the pre-defined measurements and annotations in the image processing workstation.

Compare to measurements, annotations are much easier, so I will only explain how to test the measurements, and you can adopt similar methods to test the annotations.

In the workstation, we organize pre-defined measurements in 3 layers. The top layer are 5 measurement packages, and under each package, there are 1-20 protocols, which is the second layer. Each protocol, includes 5-20 measurements, which is the bottom layer. There are about 1000 measurements in total.

All these 1000 measurements can be divided into 10 different categories, for example, there are linear measurements, area measurements, velocity measurements, and so on. They way to draw measurements from different categories are not the same, for example, linear measurement needs 2 clicks in the image area and area measurement needs 3 clicks.

Measurements under same protocol/package apply to different modes, for example, protocol A has measurement 1, 2, 3, …, 10. Measurement 1, 3, 7 apply to B-Mode, and the rest apply to M-Mode.

Since the workstation software is one of the product from my current company, we have acquired images during manual testing, and these images can be reused for automation testing too. These images are arranged in 3 layers too in order to cope with the 3 layers of the measurements. The top layer of the images is called study, which is named by package name, i.e., each package has 1 study, so there are 5 studies in total. Under each study, there are a few series, and each series is named by protocol name, so if there are 10 protocols in this package, then there will be 10 series in this study. Under each series, there are many images from different modes, and there won’t be any images from the same mode under 1 series. If the measurements under a protocol apply to 5 different modes, then there will be 5 images each from a different mode listed under the series.

As a summary, the data/images look like this:

  • Study A (named with Package A name) (expanded)
    • Series 1 (named with Protocol 1 name) (expanded)
      • image (B-Mode)
      • image (M-Mode)
      • image (other mode)
    • Series 2 (named with Protocol 2 name) (indented)
    • Series 3 (named with Protocol 3 name) (indented)
  • Study B (named with Package B name) (indented)
  • Study C (named with Package C name) (indented)
  • Study D (named with Package D name) (indented)
  • Study E (named with Package E name) (indented)

 

We also developed manual test cases for these packages. The documents contains these test cases are called system validation procedures (SVP). Each SVP covers 1 measurement package, so there are 5 SVPs. In each SVP, test cases are divided into different sections, and each section is for one protocol. In each section, there are sub-sections divided by modes. For example, in the SVP for package A, in section1 which is for protocol 1, there is a few sub-sections. One of the sub-section is to load a B-Mode image, and under this sub-section, there are many test cases to draw measurements, i.e., each test case will ask you to draw one of the measurement within the protocol.

We created the test cases in this way to make it easy for manual testers to execute the test cases, but it is not the right approach to develop automation test script, since there are about 1000 manual test cases to draw measurements, and we should not develop 1000 automation test scripts accordingly.

The way I want to write the scripts is to use an excel sheet as input, i.e., all the measurements are listed in the excel sheet, and they are stored in the following way:

Package A
Protocol 1
B-Mode
Measurement a Category a Unit a Link a
Measurement b Category b Unit b Link b
…

I will also concentrate all the repetitive test cases into one test case, so there will be in total about 10 test scripts:
test script 1: test all the packages are enabled in the preference – measurement panel; (post#10)
test script 2: test all the protocols are enabled in the preference – measurement panel; (post#12)
test script 3: test all the measurements are enabled in the preference – measurement panel; (post#14)
test script 4: draw all the measurements and output the measurements’ labels to excel sheet a; (this post#20)
test script 5: output all the measurements’ value from measurement panel to excel sheet b;
test script 6: output all the measurements’ value from analysis browser to excel sheet c;
test script 7: output all the measurements’ value to csv;
test script 8: rearrange the data in excel sheet a, b, c, and csv and compare the values are the same;
test script 9: use data from excel csv and measurement template (created during manual testing, an excel sheet has build in formulas) to check calculations results;
test script 10: draw all the annotations and out put the annotations’ label to excel sheet d, and check the values.

In the workstation, there are many objects, but they are no more than 4 types, i.e., Treeview, Listview, ImageView, and buttons. We talked about Treeview in post#10, #12, and #14, Listview in post#19, and ImageView in this post#20. Above mentioned scripts 5 to 10 are just reuse of the properties and methods of these objects, plus some logic (such as loops), so I don’t think there is need for me to post the scripts for them here (anyway you won’t have access to the workstation to understand my scripts).

Below is the script for above mentioned “test script 4″. Sub_MakeMeasurement is a test script, and inside Sub_MakeMeasurement, Function_MakeMeasurement is called, which is a module. For ImageView, there is one thing you need to know, that is how to capture the text on the ImageView: ImageView.CaptureText (startX, startY, width, depth)

Sub_MakeMeasurement

'Testing condition: If last "Link" column of the "ModeCategoryUnit" sheet is empty, then add a space in a cell of the column.

'$TPinclude "Declaration_GlobalConstants"
'$TPinclude "Function_MakeMeasurement"

Sub Main()

'Import data from Measurement.xlsx's ModeCategoryUnit sheet to array InputData()
Dim RowCount As Integer
Dim ColumnCount As Integer
Dim InputData() As String 'Dynamic array
Dim OutputData() As String 'Dynamic array

RowCount = Function_ExcelSheetRowCount.ExcelSheetRowCount(ExcelFilePath_Measurement, "ModeCategoryUnit")
ColumnCount = Function_ExcelSheetColumnCount.ExcelSheetColumnCount(ExcelFilePath_Measurement, "ModeCategoryUnit")

ReDim InputData(1 To RowCount, 1 To ColumnCount) As String    'Array is sized dynamically
ReDim OutputData(1 To RowCount, 1 To ColumnCount) As String    'Array is sized dynamically

InputData() = Function_GetExcelSheetData.GetExcelSheetData(ExcelFilePath_Measurement, "ModeCategoryUnit")

'From Study Browser, open Images from different Study and Series
Dim Study_Package As String 'Study names are the Package names
Dim Series_Protocol As String    'Series names are the Protocol names
Dim Image_Mode As String    'Image names are the Mode names
Dim j As Integer
Dim Count As Integer

'Open the workstation
    ProgramManagerWindow("Application=EXPLORER.EXE Caption='Program Manager'").Attach
        ListView("Index=1").Select "the workstation", tpMouseDoubleClick

'Attach to the workstation
    Window("the workstation").Attach
        For j = 1 To ColumnCount Step 4

            'Inside Study Browser, load the Image_Mode from the correct Study and Series
            Study_Package = InputData(1, j)
            Series_Protocol = InputData(2, j)
            Image_Mode = InputData(3, j)
            OutputData(1, j) = InputData(1, j)
            OutputData(2, j) = InputData(2, j)
            OutputData(3, j) = InputData(3, j)

            'If can not find the Series_Protocol, then the Study_Package needs to be expanded
            If ListView("Parent.Caption='Study Browser'").FindItem(Series_Protocol) = 0 Then
                ListView("Parent.Caption='Study Browser'").Select (Study_Package), tpMouseDoubleClick
            End If

            'If the mode column (i.e., the 6th column) of the row after Series_Protocol is empty
            'then the row is either a Series or a Study
            'the Series_Protocol needs to be expanded to see all the Image_Modes
            Count = ListView("Parent.Caption='Study Browser'").FindItem(Series_Protocol)
            If ListView("Parent.Caption='Study Browser'").GetItem(Count + 1, 6) = "" Then
                ListView("Parent.Caption='Study Browser'").Select (Series_Protocol), tpMouseDoubleClick
            End If

            'Search to load the Image_Mode in between the Series_Protocol and next Series/Study
            Do While ListView("Parent.Caption='Study Browser'").GetItem(Count + 1, 6) <> ""
                If ListView("Parent.Caption='Study Browser'").GetItem(Count + 1, 6) = Image_Mode Then
                    ListView("Parent.Caption='Study Browser'").SelectIndex (Count + 1), tpMouseDoubleClick
                    Exit Do
                Else
                    Count = Count + 1
                End If
            Loop

            'Inside the Mode Window, stop playback, then delete existing measurements and make new measurements
            Button("Caption=Forw").Click    'Stop PlayBack
            Button("Caption=Home").Click    'Display the first Frame
            Button("Caption=Msmnt").Click   'Open Measurement panel

            'Delete measurements
            'Do while the measurement side panel is not empty ("#NameValue" is the header of the ListView)
            Do While ListView("Label='Measured Values'").CaptureText <> "#NameValue"
            ListView("Label='Measured Values'").SelectIndex 1   'Select the top item to delete
            ListView("Label='Measured Values'").Type "{ExtDelete}"  'Press [Delete] key
            Loop

            'Draw new measurements
            'Select Measurement Pacakge
            ComboBox("Parent.Caption=ModeRootView").Select Study_Package

            Dim Measurement As String
            Dim Category As String
            Dim i As Integer

            For i = 4 To RowCount
                If InputData(i, j) <> "" And InputData(i, j) <> "(Note 1)" And InputData(i, j) <> "(Note1)" Then
                    If InputData(i, j + 1) <> "" Then
                        Measurement = InputData(i, j)
                        Category = InputData(i, j + 1)
                        OutputData(i, j) = InputData(i, j)
                        OutputData(i, j + 1) = InputData(i, j + 1)
                        OutputData(i, j + 2) = InputData(i, j + 2)
                    Else
                        Measurement = InputData(i, j)
                        Category = InputData(i + 1, j + 1)
                        OutputData(i, j) = InputData(i, j)
                    End If
                    'Call Function_MakeMeasurement to draw the measurement
                    Dim Label As String
                    Label = Function_MakeMeasurement.MakeMeasurement(Image_Mode, Series_Protocol, Measurement, Category)
                    OutputData(i, j + 3) = Label
                ElseIf InputData(i, j) <> "" And InputData(i, j) = "(Note 1)" Then
                    OutputData(i, j) = InputData(i, j)
                    OutputData(i, j + 1) = InputData(i, j + 1)
                    OutputData(i, j + 2) = InputData(i, j + 2)
                ElseIf InputData(i, j) <> "" And InputData(i, j) = "(Note1)" Then
                    OutputData(i, j) = InputData(i, j)
                    OutputData(i, j + 1) = InputData(i, j + 1)
                    OutputData(i, j + 2) = InputData(i, j + 2)
                Else: Exit For
                End If
            Next

            'Switch back to Study Browser
            Button("Caption=B").Click

        Next

'Close application to reset its original state
    Window.Close

'Use shared module "Function_SaveArrayAsExcelSheet" to write data from array OutputData() to Excel
a = Function_SaveArrayAsExcelSheet.SaveArrayAsExcelSheet(OutputData, RowCount, ColumnCount, ExcelFilePath_Measurement, "ImageArea")

'Erase arrays
Erase InputData
Erase OutputData

End Sub

Function_MakeMeasurement

Function MakeMeasurement(Mode As String, Protocol As String, Measurement As String, Category As String)

'Go to an empty frame/section of the loop
script not posted

'Select \Protocol\Measurement
TreeView("Parent.Caption=ModeRootView").SelectItem "\" & Protocol & "\" & Measurement

'Draw the measurement
Dim MeasurementLabel As String

script not posted

'MakeMeasurement Function returns MeasurementLabel
MakeMeasurement = MeasurementLabel

End Function
 
No Comments

Posted by Jia Qi in TestPartner (TP)

 

#16: Export data from Two-Dimensional Array (2D array) to an Excel Sheet

25 Jul

In Post#9, we talked about how to import data from Excel (with multiple sheets) to an Array.

In this post, we will discuss that how to export data from a Two-Dimensional Array (2D array) to an Excel sheet.

Function SaveArrayAsExcelSheet(ArrayData() As String, ArrayRowCount As Integer, ArrayColumnCount As Integer, ExcelFilePath As String, SheetName As String)

'On error jump to "Error Handler:" line
On Error GoTo ErrorHandler

'Variable declaration
Dim SheetCount As Integer

'Open the Excel file
Set ObjExcel = CreateObject("Excel.Application")
Set ObjWorkBook = ObjExcel.Workbooks.Open(ExcelFilePath)

'Count how many sheets in the Excel file
SheetCount = ObjWorkBook.WorkSheets.Count

'If the sheet named "SheetName" exists, delete it
For i = 1 To SheetCount
    If ObjWorkBook.WorkSheets(i).Name = SheetName Then
        ObjExcel.DisplayAlerts = False  'Disable the delete confirmation message
        ObjWorkBook.WorkSheets(i).Delete
        ObjExcel.DisplayAlerts = True   'Enable the delte confirmation message
        Exit For
    End If
Next

'Create a new sheet in the Excel file and name this sheet as "SheetName"
ObjWorkBook.WorkSheets.Add.Name = SheetName

'Transfer data from an array to a Excel sheet
Dim ObjRange As Excel.Range
For i = 1 To SheetCount
    If ObjWorkBook.WorkSheets(i).Name = SheetName Then
        Set ObjRange = ObjWorkBook.WorkSheets(i).Range(ObjWorkBook.WorkSheets(i).Cells(1, 1), ObjWorkBook.WorkSheets(i).Cells(ArrayRowCount, ArrayColumnCount))
        ObjRange.Value = ArrayData()
    End If
Next

'Save and Close the Excel file
ObjWorkBook.Save
ObjWorkBook.Close

Exit Function

ErrorHandler: ' This is a normal VBA line label
    MsgBox Err.Description
    ObjWorkBook.Close

End Function

The VBA script above solves the problem (it will add or overwrite a sheet in the Excel file to receive data). The script should be saved as an shared module in TestPartner. To make the script work, you need to go to Tools->Reference to check the reference for Microsoft Excel, otherwise, TestPartner will give you an error on line “Dim ObjRange As Excel.Range”. (see Chapter 8 page 96 of “TestPartner Advanced Training Guide.pdf for Test Partner 5.2” listed in post#8 for more details.)

If you want to apply the script in QTP which uses VBScript instead of VBA, you need to make some minor modifications:

A, The function script needs to be created in the QTP Function Library (File – New – Function Library);

B, In the function script, delete anything related to the ErrorHandler (2 paragraphs);

C, In the function script, delete any definition for variable type, e.g., modify “SheetName As String” to “SheetName”, and change “Dim SheetCount As Integer” to “Dim SheetCount”.

D, Create a Test/Action to execute the function script, and the test/action will look like this (compare to TestPartner test script, no “Sub” nor “End Sub”, no need to assign the function to a variable, and no function file name nor brackets, i.e.,
in Testpartner (In TestPartner, if the function does not have a return value, but it has more than 1 input values, then in order to execute the function, you still need to define a variable in your test script, and assign the function to the variable.):

Sub Main()
a = Function_SaveArrayAsExcelSheet.SaveArrayAsExcelSheet(ArrayName, 15, 60, "C:\...\MeasurementTab.xlsx", "Sheet2")
End Sub

in QTP:

SaveArrayAsExcelSheet ArrayName, 15, 60, "C:\...\MeasurementTab.xlsx", "Sheet2")

E, Associate the Function file with the Test/Action file (right click on the Function file script and choose “Associate…” on the pop up menu), then you can run the function by running the test/action.

The script above should be fast enough to handle 10,000 data, but if your data is more than 50,000, then you may experience some slowness (depends on your computer speed too). There are two ways to solve the speed problem:
1, export the data from array to csv, then convert csv to Excel.
2, use ExcelCreator.NET instead of Excel Object, which is more efficient.
For more details, please refer to this website (you need to understand Chinese) .

 
No Comments

Posted by Jia Qi in Quick Test Professional (QTP), TestPartner (TP)

 

#7: Relationship among VBScript, Visual Basic for Applications (VBA), Visual Basic (VB), Visual Basic .NET, and JavaScript

28 May

QTP uses the Visual Basic Scripting Edition (VBScript) scripting language, TestPartner is based on the Visual Basic for Applications (VBA), and RFT’s test script is produced as either a Java or Visual Basic.net application.

VBScript is a subset of the Visual Basic Programming language. The result of the slimming down process is a very small language that is easy to use. JavaScript can do all that VBScript can do and far more. So why use VBScript instead of JavaScript? Because VBScript is much easier to learn than JavaScript.

Visual Basic for Applications (VBA) is another subset of the Visual Basic Programming language for use with Microsoft Word, Excel, Access etc. While it contains a good many features not supported by VBScript, the basic syntax, or construction of the language, is very similar.

RFT is not the main focus for this blog, at least not yet, so for Java vs. VB.NET, you only need to know that Java is programming environment controlled by Sun, and VB.NET is developed by Microsoft.

As said above, both VBScript and VBA are subsets of Visual Basic (VB). The final release of VB was version 6 in 1998. Microsoft’s extended support ended in March 2008 and the designated successor was Visual Basic .NET (now known simply as Visual Basic)

After learning the history of the VB family and JavaScript, let us play a small game by writing the VBScript in a notepad. This is very useful if you do not want to bother to repeat the same thing over and over again.

Copy the following code into a notepad, and save it as kk.vbs, then double click on it, and see what it will do.

Dim fs, file, TSTnumber
set fs = createobject( "Scripting.FileSystemObject" )
set file = fs.OpenTextFile( "RF.BAT", 2, true )

For TSTnumber=613 to 616
file.write "VsiColorModeRAW.exe tst-18-0"
file.write TSTnumber
file.write "\tst-18-0"
file.write TSTnumber
file.write ".raw.bmode tst-18-0"
file.write TSTnumber
file.write "\tst-18-0"
file.write TSTnumber
file.write ".raw.color tst-18-0"
file.write TSTnumber
file.write "\tst-18-0"
file.write TSTnumber
file.write ".raw.xml tst-18-0"
file.write TSTnumber
file.writeline "\Color"
Next
file.close
set fs=nothing
 
No Comments

Posted by Jia Qi in Quick Test Professional (QTP), Rational Functional Tester (RFT), TestPartner (TP)

 

#0: What is this blog for?

06 Sep

This blog will show you real projects examples for you to learn the following Automation testing tools:
- Quick Test Professional (QTP),
- TestPartner (TP),
- Extensible Markup Language (XML),
- Selenium (Selenium-IDE),
- Rational Functional Tester (RFT).

QTP and TestPartner are similar GUI automation testing tools, and they are both easy to learn compare to RFT which I used before. RFT uses JavaScript or VB.NET, QTP uses VBScript, and TestPartner uses VBA (more details about VB family and JavaScript, please refer to post#7). Among the three, QTP has the biggest job market. As a QA person, we should master at least one of the automation testing tools and one of the scripting language.

Selenium is a portable software testing framework for web applications. Selenium provides a test domain specific language (DSL) to write tests in a number of popular programming languages, including C#, Java, Ruby, Groovy, Python, PHP, and Perl. In this blog, we will focus on Selenium IDE, which is a complete Integrated Development Environment (IDE) for Selenium tests. It is implemented as a Firefox extension, and allows recording, editing, and debugging tests.

The difference between Selenium and QTP/TestPartner/RFT is Selenium is an open source software, i.e., it is free! See more information at post#29.

If you decide to learn automation testing, then you can follow this blog. I will share detailed test cases/scripts with you while I am learning, and I am looking forward to learn from you too, so don’t be shy to comment on my posts.

My current company uses TestPartner 6.3 to test an Ultrasound work station (a Windows Application, i.e., software, can be installed on any computer). Our major focus is to automate measurement and export testing, since we have thousands measurement types and hundreds export combinations in the app., which make manual testing very very time consuming. We will also use XML scripts (embedded in Engineering mode) to test our real-time Ultrasound machines. The Ultrasound machine supports 10 different types of transducers, we need to repeat hundred test cases for each type of the transducers, so to automate the transducer tests will save us a huge amount of time.

I also test some websites at home, just for learning purpose. In this blog, I will show you how to test a website called YouPlayOff. I will use QTP and Selenium to test this website, and you can download QTP 9.0 from the pirate bay and Selenium-IDE from Selenium website.

After we get familiar with QTP, Selenium and TestPartner, then RFT should not be a problem anymore.

 
No Comments

Posted by Jia Qi in Extensible Markup Language (XML), Quick Test Professional (QTP), Rational Functional Tester (RFT), Selenium, TestPartner (TP)