QuickTest Pro Fundas

Framework 5: Hybrid Test Automation Framework

2009-01-25T01:04:00.001-08:00

The most commonly implemented framework is a combination of all of the above techniques, pulling from their strengths and trying to mitigate their weaknesses. This hybrid test automation framework is what most frameworks evolve into over time and multiple projects. The most successful automation frameworks generally accommodate both Keyword-Driven testing as well as Data-Driven scripts.

This allows data driven scripts to take advantage of the powerful libraries and utilities that usually accompany a keyword driven architecture. The framework utilities can make the data driven scripts more compact and less prone to failure than they otherwise would have been.

The utilities can also facilitate the gradual and manageable conversion of existing scripts to keyword driven equivalents when and where that appears desirable. On the other hand, the framework can use scripts to perform some tasks that might be too difficult to re-implement in a pure keyword driven approach, or where the keyword driven capabilities are not yet in place.

Framework 4: Keyword-Driven Testing

2009-01-15T01:01:00.000-08:00

This requires the development of data tables and keywords, independent of the test automation tool used to execute them and the test script code that "drives" the application-under-test and the data. Keyword-driven tests look very similar to manual test cases. In a keyword-driven test, the functionality of the application-under-test is documented in a table as well as in step-by-step instructions for each test. In this method, the entire process is data-driven, including functionality.

Example

In order to open a window, the following table is devised, and it can be used for any other application, just it requires just changing the window name.

Test Table for Opening a Window

Window	Control	Action	Arguments
Window Name	Menu	Click	File, Open
Window Name	Menu	Click	Close
Window Name	Pushbutton	Click	Folder Name
Window Name		Verify	Results

Once creating the test tables, a driver script or a set of scripts is written that reads in each step executes the step based on the keyword contained the Action field, performs error checking, and logs any relevant information.

Merits of keyword driven testing

The merits of the Keyword Driven Testing are as follows,

Ø The Detail Test Plan can be written in Spreadsheet format containing all input and verification data.

Ø If "utility" scripts can be created by someone proficient in the automated tool’s Scripting language prior to the Detail Test Plan being written, then the tester can use the Automated Test Tool immediately via the "spreadsheet-input" method, without needing to learn the Scripting language.

Ø The tester need only learn the "Key Words" required, and the specific format to use within the Test Plan. This allows the tester to be productive with the test tool very quickly, and allows more extensive training in the test tool to be scheduled at a more convenient time.

Demerits of keyword driven testing

The demerits of the Keyword Driven Testing are as follows,

Ø Development of "customized" (Application-Specific) Functions and Utilities requires proficiency in the tool’s Scripting language. (Note that this is also true for any method)

Ø If application requires more than a few "customized" Utilities, this will require the tester to learn a number of "Key Words" and special formats. This can be time-consuming, and may have an initial impact on Test Plan Development. Once the testers get used to this, however, the time required to produce a test case is greatly improved.

Framework 3: Data-Driven Testing

2009-01-11T00:58:00.000-08:00

A data-driven framework is where test input and output values are read from data files (ODBC sources, CVS files, Excel files, DAO objects, ADO objects, and such) and are loaded into variables in captured or manually coded scripts. In this framework, variables are used for both input values and output verification values.

Navigation through the program, reading of the data files, and logging of test status and information are all coded in the test script. This is similar to table-driven testing (which is discussed shortly) in that the test case is contained in the data file and not in the script; the script is just a "driver," or delivery mechanism, for the data. In data-driven testing, only test data is contained in the data files.

Merits of data-driven testing

The merits of the Data-Driven test automation framework are as follows,

Ø Scripts may be developed while application development is still in progress

Ø Utilizing a modular design, and using files or records to both input and verify data, reduces redundancy and duplication of effort in creating automated test scripts

Ø If functionality changes, only the specific "Business Function" script needs to be updated

Ø Data input/output and expected results are stored as easily maintainable text records.

Ø Functions return "TRUE" or "FALSE" values to the calling script, rather than aborting, allowing for more effective error handling, and increasing the robustness of the test scripts. This, along with a well-designed "recovery" routine, enables "unattended" execution of test scripts.

Demerits of data-driven testing

The demerits of the Data-Driven test automation framework are as follows,

Ø Requires proficiency in the Scripting language used by the tool (technical personnel)

Ø Multiple data-files are required for each Test Case. There may be any number of data-inputs and verifications required, depending on how many different screens are accessed. This usually requires data-files to be kept in separate directories by Test Case

Ø Tester must not only maintain the Detail Test Plan with specific data, but must also re-enter this data in the various required data-files

Ø If a simple "text editor" such as Notepad is used to create and maintain the data-files, careful attention must be paid to the format required by the scripts/functions that process the files, or script-processing errors will occur due to data-file format and/or content being incorrect

Framework 2 : Test Library Architecture

2009-01-02T00:55:00.000-08:00

The test library architecture framework is very similar to the test script modularity framework and offers the same advantages, but it divides the application-under-test into procedures and functions (or objects and methods depending on the implementation language) instead of scripts.
This framework requires the creation of library files (SQABasic libraries, APIs, DLLs, and such) that represent modules, sections, and functions of the application-under-test. These library files are then called directly from the test case script.

Much like script modularization this framework also yields a high degree of modularization and adds to the overall maintainability of the tests.

Framework 1: Test Script Modularity

2009-01-01T00:53:00.000-08:00

   The test script modularity framework is the most basic of the frameworks. It's a well-known programming strategy to build an abstraction layer in front of a component to hide the component from the rest of the application.
   This insulates the application from modifications in the component and provides modularity in the application design. When working with test scripts (in any language or proprietary environment) this can be achieved by creating small, independent scripts that represent modules, sections, and functions of the application-under-test.
   Then these small scripts are taken and combined them in a hierarchical fashion to construct larger tests. The use of this framework will yield a higher degree of modularization and add to the overall maintainability of the test scripts.

Record /Playback Myth

2008-12-25T00:39:00.000-08:00

The test automation tool vendors market their product as the main feature of the tool is the ability to capture the user actions and later to playback them. Here is the basic paradigm for GUI-based automated regression testing – the so called Record/Playback method (also called as Capture/Replay approach)

1. Design a test case in the test management tool.

2. Using the capture feature of the automation testing tool record the user actions. The result is a macro-like script where each user action is presented.

3. Enhance the recorded script with verification points, where some property or data is verified against an existing baseline. Add delay and wait states points where the different actions are synchronized.

4. Playback the scripts and observe the results in the log of the test management tool.

The basic drawback in this method is the scripts resulting from this method contain hard-coded values which must change if anything at all changes in our AUT. The costs associated with maintaining such scripts are astronomical, and unacceptable. These scripts are not reliable, even if the application has not changed, and often fail on replay (pop-up windows, messages, and other things can happen that did not happen when the test was recorded).
If the tester makes an error entering data, etc., the test must be re-recorded. If the application changes the test must be re-recorded. All that is being tested are things that already work. Areas that have errors are encountered in the recording process (which is manual testing, after all). These bugs are reported, but a script cannot be recorded until the software is corrected. So logically nothing is tested by this approach.

So, avoid using "Record/Playback" as a method of automating testing. This method is fraught with problems, and is the most costly (time consuming) of all methods over the long term. The record/playback feature of the test tool is useful for determining how the tool is trying to process or interact with the application under test, and can give us some ideas about how to develop your test scripts, but beyond that, its usefulness ends quickly.

Types of Test Automation Frameworks

2008-12-05T00:49:00.000-08:00

There are several test automation frameworks available, among these the selection is made based on the factors such as reusability of both the scripts and the test assets. The different test automation frameworks available are as follows,
 Test Script Modularity
 Test Library Architecture
 Data-Driven Testing
 Keyword-Driven or Table-Driven Testing
 Hybrid Test Automation

Difference between Function and Sub

2008-11-27T23:20:00.000-08:00

In VBScript, there are two types of procedures:

Sub Procedures
Function Procedures
Sub Procedures

A sub procedure is a series of VBScript statements, enclosed by Sub and End Sub statements which perform actions but do not return a value. A sub procedure can take arguments. If a sub procedure doesn’t receive any arguments, its Sub statement must include an empty parenthesis().

The following Sub procedure uses two intrinsic, or built-in, VBScript functions, MsgBox and InputBox , to prompt a user for information. It then displays the results of a calculation based on that information. The calculation is performed in a Function procedure created using VBScript. The Function procedure is shown after the following discussion.

Sub ConvertTemp()

temp = InputBox("Please enter the temperature in degrees F.", 1)

MsgBox "The temperature is " & Celsius(temp) & " degrees C."
End Sub

Function Procedures

A function procedure is a series of VBScript statements enclosed by the Function and End Function statements. A function procedure is similar to a sub procedure but it can return value to the calling function. A function procedure can take arguments (constants, variables or expressions that are passed to it by a calling procedure). If a function procedure has no arguments, it Function statement must include an empty set of parenthesis. A function returns a value by assigning a value to its name in one or more statements of the procedure. Since VBScript has only one base data type, a function always returns a variant.

In the following example, the Celsius function calculates degrees Celsius from degrees Fahrenheit. When the function is called from the ConvertTemp Sub procedure, a variable containing the argument value is passed to the function. The result of the calculation is returned to the calling procedure and displayed in a message box.

Sub ConvertTemp()
temp = InputBox("Please enter the temperature in degrees F.", 1)
MsgBox "The temperature is " & Celsius(temp) & " degrees C."
End Sub

Function Celsius(fDegrees)
Celsius = (fDegrees - 32) * 5 / 9
End Function
Tips:
To get data out of a procedure, you must use a Function. Remember, a Function procedure can return a value; a Sub procedure can't.
A Function in your code must always be used on the right side of a variable assignment or in an expression.
To call a Sub procedure from another procedure, type the name of the procedure along with values for any required arguments, each separated by a comma. The Call statement is not required, but if you do use it, you must enclose any arguments in parentheses.
The following example shows two calls to the MyProc procedure. One uses the Call statement in the code; the other doesn't. Both do exactly the same thing.
Call MyProc(firstarg, secondarg)

MyProc firstarg, secondarg

Notice that the parentheses are omitted in the call when the Call statement isn't used.

Data driven testing using excel in QTP

2008-07-21T01:40:00.000-07:00

This is script for data driven using excel sheet.
In this script we are not importing excel sheet to datatable. Directly values are supplied to application from excel sheet.

set ex= CreateObject("Excel.Application")
Set a=ex.Workbooks.open("D:\excel.xls")
Set b=a.worksheets("Sheet1")

dim login, pwd

for i=1 to 3

login=b.Cells(i,"A").value
pwd=b.Cells(i,"B").value
msgbox login
msgbox pwd

next

"D:\excel.xls" is path of excel sheet.
"sheet1" indicates sheet name in which values are present.
A,B are column names in excel sheet.

we have excel sheet with values as shown below in d drive.
A B
1 2
3 4
5 6

Count & Close all browsers

2008-06-21T01:32:00.000-07:00

QTP Script to get total count, names of all open browsers and to close them using descriptive programming..

Set ab=Description.Create
ab("micclass").value="Browser"
Set obj=Desktop.ChildObjects(ab)
msgbox obj.count
For i=0 to obj.count-1
c=obj(i).getroproperty("name")
msgbox(c)
obj(i).Close
Next

Descriptive programming example

2008-05-21T01:35:00.000-07:00

This is an example for descriptive programming in QTP for a checkbox.
In this script we will check whether yahoologinpage(www.yahoomail.com) checkbox is checked or not

Set g=Browser("name:=Yahoo.*").Page("title:=Yahoo.*")
Set obj=Description.Create
obj("htmltag").value="Input"
obj("ClassName").value="webcheckbox"
obj("type").value="checkbox"
Set a=g.childobjects(obj)
c=a(0).getroproperty("checked")
msgbox(c)
If c=0 Then
msgbox "checkbox is not checked"
else
msgbox"checkbox is checked"
End If

Data Driven Testing using Notepad in QTP

2008-04-20T23:48:00.000-07:00

Set
f=createobject("scripting.filesystemobject")
Set f1=f.createtextfile("d://file1.txt")
f1.writeline"aaa bbb"
f1.writeline"ccc ddd"
f1.writeline"eee fff"
f1.writeline"ggg hhh"
f1.writeline"iii jjj"

The above script creates a notepad in "d" drive with name file1

aaa bbb
ccc ddd
eee fff
ggg hhh
iii jjj

values are stored in file1.txt.

Set f2=f.opentextfile("d://file1.txt")

While f2.atendofstream<>true
f3=f2.readline
x=split(f3," ")
msgbox x(0)
msgbox x(1)

Wend

The above script is used for data driven using notepad directly.here we are not importing data to excel sheet.

directly values are retreived from notepad.

we are using while loop and reading each line till the end.

split function splits the line where space(" ")occurs.

line is divided to 2 parts.one before space and other after space

for example we have 1st line in notepad as aaa bbb

here aaa is 1st part and bbb is 2nd part

x(0)=aaa

x(1)=bbb

all values are read this way using while loop.
One point to note here is if any line is empty in notepad datadriven testing is stopped before that line.

It will not proceed further.so we have to give values without any empty lines in notepad.

To make u more clear,
suppose u have

aaa bbb

ccc ddd

Datadriven is stopped at aaa and bbb only because next line is empty.datadriven is stopped after 1st line.

Some common QTP functions

2008-03-30T23:24:00.000-07:00

In this article I captured some functions which are captured from various sources.

How to check for the broken links (both textlinks and image links) on the page with VB script and not the checkpoints.
---------------------------------------------------------
set
obj=Browser("name:=Blackboard.*").Page("title:=Blackboard.*").Frame("name:=main.*").object.all.tags("IMG")

msgbox obj.length

For each element in obj
s1=element.nameProp

If Browser().Page().Frame().Image("file
name:="&s1,"index:=0").exist(0) then
If Browser().Page().Frame().Image("file
name:="&s1,"index:=0").Object.complete="True" then

msgbox "pass"

else
msgbox "fail"

end if
end if

Next
---------------------------------------------------------

Multiple Exit ways

It’s very easy to control the entry gate to an action or function - there’s only one way to enter them. However, the number of exit gates can vary widely from 1 to many according to the inner logic of the action/function. Today I’m going to address managing multiple exit gates in actions and functions.
When everything goes according to plan, an action flow tends to be very simple. There may be inner loops, If or Select switches, but for the most part, the flow just runs straight down to the last line. The problems usually appear when… well, problems appear. If an application error occurs, or even just an unexpected business logic behavior, there might be no escape from immediately exiting the action. There’s no point trying to input 20 data fields, if the form they’re in didn’t even open, is there?The function is something like the following:

‘.Action Code

If CritialCondition = False Then ExitAction

‘.Continue Action

But this is uninformative. So we add a reporter command:

If CritialCondition = False Then

Reporter.ReportEvent MicFail, "Something terrible has happened", "Aborting"
ExitAction
End If
And we probably got some objects to remove from memory:
If CritialCondition = False Then

Reporter.ReportEvent MicFail, "Something terrible has happened", "Aborting"

oFile.Close

Set oFile = Nothing

ExitAction

End If
============================================

Ho wait, we’ve gathered some data we need to report back:
If CritialCondition = False Then

Reporter.ReportEvent MicFail, "Something terrible has happened", "Aborting"

oFile.Close

Set oFile = Nothing

DataTable("out_EntityID", dtlocalsheet) = sEntityID

‘More here

ExitAction

End If

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

Well, you probably get the picture. Pretty soon we get massive amounts of code in all the exit gates. This means we have duplicate code to maintain. Duplicate code is the digital manifestation of pure evil – and it’s never a good idea to have pure evil in you actions. Seriously though, this is exactly the kind of things that produces untraceable bugs, and it must be avoided at all cost.
So, how can we deal with this situation? One way is to create an exit gate function. It’s the ONLY function I ever put within an action, and not in an external file. Here’s an example of my action template, with the function:
Dim sResult ‘I store result data and values to be reported up the

‘action-call chain

Dim sActionReport ‘Instead of flooding the log with inner-action messages,

‘I store them, and report all of them at the exit gate.

‘Errors are still reported on-the-fly

‘Action code goes here

‘All the exit gates execute only one command : ActionEnd.

‘It receives two parameters: Boolean for Pass/Fail,

’string for the exit reason

If CriticalCondition = False Then Call ActionEnd(False, "Reason for exiting")

‘Rest of action

‘Even the normal successful action exit is managed through ActionEnd,

’so the last line in every action is:

Call ActionEnd(True, "Action successful")

Sub ActionEnd(bStatus, sReason)

‘Report details

Reporter.ReportEvent MicGeneral, "Inner Action Logs", sActionReport

If bStatus = True Then

Reporter.ReportEvent MicFail, "An error has occurred", sReason

Else

Reporter.ReportEvent MicPass, "Action successful", "See inner logs"

End if

‘Plant datatable info for action-call chain

DataTable("out_Status", dtlocalsheet) = bStatus

DataTable("out_Result", dtlocalsheet) = sResult

‘More if needed

‘Close objects and set to nothing here

‘Other needed exit code

ExitActionIteration

End Sub

With this mechanism, maintaining the exit code becomes very simple, and the logs are much more readable. Ok, so this solves the problem for actions, but what about functions? Well, obviously we can write an inner function within a function, but there is an alternative solution. It’s less elegant than the ActionEnd solution by far, and is harder to maintain, so I recommend using it only in a small number of very complex functions.
The solution is based on the Execute command, so I recommend reading about it in QTP’s help file in case you’re not familiar with it. In a nutshell, the Execute command takes a string, and runs its contents as if it were VBScript code. So for instance the command Execute "msgbox(2)" will pop a message box with the number 2. Here’s an example for the solution, applied to the ComplexFunc function:
Function ComplexFunc

Dim sExitCode

Dim sResult

Dim oFile ‘will be FSO textstream

’separate code lines by vbcrlf or ":"

sExitCode = "oFile.Close" & vbcrlf & _

"Set oFile = Nothing" & vbcrlf & _

"ComplexFunc = sResult"

‘More exit code

‘Function code goes here

‘Exit Gate

If CriticalCondition = False then

sResult = "False, No Connection"

Execute sExitCode

Exit Function

End if

‘More function code

‘Successful exit

Execute sExitCode

End Function

Creating and Calling user define funtion

Test Conditons: Creating and Calling user define funtion

1. Crate small add function and make it compile module.

2. calling that function in other test (using user defined data values)

[ Pre Requesties : Nothing ]

1a. open win runner blank test and add this below data

public function add(in a, in b)
{
return a+b;
}

1b. Go to File menu --> Test Properties (Test Properties window will open)
in General Tab --> Test Type= Compile module and ok

1c.Save the test in some location (Ex c:/tt )

2a.Before writing code , you have to load the funtction in to your folder , globally available to all tests.

2b. Go to Tools menu --> General Options
--- Select Folder option in the left pan.
-- Search Path for called test below enter the path of compile module
(c:/tt) and press "+" button to add in to.

2c. Write down the bleow code in the new test

load("c:/tt");
l= create_input_dialog("Enter First value");
j=create_input_dialog("Enter Second Value");
k=add(l,j);
report_msg(k);
unload("c:/tt");

WinRunner End-of-support and Migration Webinar

2008-02-26T20:51:00.000-08:00

Make sure your HP emails always go straight to your inbox. Add sw-bulletins@info.hp.com to your address book! Need Help?
WinRunner End-of-Support Announcement
HP WinRunner Migration Webinar: A Case Study from Travelocity» Register NowLive date: Tuesday, March 11, 2008 Start time: 7:00 AM PT9:00 AM CT10:00 AM ET3:00 PM GMTSpeakers: Rachel Pilgrim, QA Manager,TravelocitySatish Atluri, HP QM Global Practices Roi Carmel, Functional Testing Product Manager, HP Software

Learn more

» WinRunner End-of-Support Announcement» WinRunner migration data sheet
Find out how to accelerate migration from WinRunner to QuickTest Professional »

IMPORTANT ANNOUNCEMENT FOR WINRUNNER USERSHP Software is announcing end-of-support for HP WinRunner software, all versions (7.5, 7.6, 8.0, 8.2, 9.2). This end-of-support is based on our decision to consolidate and focus our functional testing offerings (HP WinRunner and HP QuickTest Professional) to maximize value to our customers. For migration options, support end dates and a list of FAQs, read the entire announcement here.Migration WebinarTo assist you with the migration from HP WinRunner to HP QuickTest Professional, we are hosting a Webinar with HP Professional Services (PS) and Travelocity who pioneered the HP WinRunner to HP QuickTest Professional migration effort. In this Webinar, Travelocity will share how they leveraged Gallop Technologies’ WinQuick – an HP R&D validated and approved automated migration solution – to automatically migrate and re-architect their HP WinRunner code base to HP QuickTest Professional. You will learn:
• What options Travelocity evaluated before undertaking this migration
• How Travelocity was able to perform this migration within budget and in less time than expected while at the same time increasing adoption of HP QuickTest Professional across the enterprise
• How you can replicate Travelocity’s success in your own organization
Don’t miss this opportunity to get insights from a customer who had great success with this migration.

Technology for better business outcomes
» HP Software
» Sales
» Privacy Policy
» Unsubscribe

If you received this e-mail from a friend and/or would like to subscribe to our e-mail list to receive future promotions and special offers, please click here.HP respects your privacy. If you'd like to discontinue receiving e-mails from HP regarding special offers and information, please click here.For more information regarding HP's privacy policy or to obtain contact information please visit our privacy statement or write to us at: Privacy Mailbox, 20555 SH 249, Houston, Texas 77070, ATTN: HP Privacy MailboxHewlett-Packard website Sign-up for Driver and Support Alerts

Verify Broken Links using VBscript (without checkpoints)

2008-01-17T04:53:00.001-08:00

One of my friends just wanted to check for the broken links (both textlinks and image links) on the page with VB script and not the checkpoints.
So the answer for that was the following code
---------------------------------------------------------
set
obj=Browser("name:=Blackboard.*").Page("title:=Blackboard.*").Frame("name:=main.*").object.all.tags("IMG")

msgbox obj.length

For each element in obj
s1=element.nameProp

If Browser().Page().Frame().Image("file
name:="&s1,"index:=0").exist(0) then
If Browser().Page().Frame().Image("file
name:="&s1,"index:=0").Object.complete="True" then

msgbox "pass"

else
msgbox "fail"

end if
end if

Next
---------------------------------------------------------

Code provided by my friend Shiva

Multiple Exit ways

2008-01-14T09:18:00.000-08:00

It’s very easy to control the entry gate to an action or function - there’s only one way to enter them. However, the number of exit gates can vary widely from 1 to many according to the inner logic of the action/function. Today I’m going to address managing multiple exit gates in actions and functions.

When everything goes according to plan, an action flow tends to be very simple. There may be inner loops, If or Select switches, but for the most part, the flow just runs straight down to the last line. The problems usually appear when… well, problems appear. If an application error occurs, or even just an unexpected business logic behavior, there might be no escape from immediately exiting the action. There’s no point trying to input 20 data fields, if the form they’re in didn’t even open, is there?

Thankfully, the nice guys and gals at Mercury have taken this into account, and have provided us with the ExitAction and ExitActionIteration commands. So usually we’ve got something like the following:

‘.Action Code
If CritialCondition = False Then ExitAction
‘.Continue Action  
But this is uninformative. So we add a reporter command:
If CritialCondition = False Then

Reporter.ReportEvent MicFail, "Something terrible has happened", "Aborting"

ExitAction

End If

And we probably got some objects to remove from memory:

If CritialCondition = False Then 
  Reporter.ReportEvent MicFail, "Something terrible has happened", "Aborting"
  oFile.Close
  Set oFile = Nothing
  ExitAction
End If
============================================ 

Ho wait, we’ve gathered some data we need to report back:

If CritialCondition = False Then 
  Reporter.ReportEvent MicFail, "Something terrible has happened", "Aborting"
  oFile.Close
  Set oFile = Nothing
  DataTable("out_EntityID", dtlocalsheet) = sEntityID
  ‘More here
  ExitAction
End If
 

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

Well, you probably get the picture. Pretty soon we get massive amounts of code in all the exit gates. This means we have duplicate code to maintain. Duplicate code is the digital manifestation of pure evil – and it’s never a good idea to have pure evil in you actions. Seriously though, this is exactly the kind of things that produces untraceable bugs, and it must be avoided at all cost.

So, how can we deal with this situation? One way is to create an exit gate function. It’s the ONLY function I ever put within an action, and not in an external file. Here’s an example of my action template, with the function:

Dim sResult    ‘I store result data and values to be reported up the
               ‘action-call chain
Dim sActionReport     ‘Instead of flooding the log with inner-action messages,
                      ‘I store them, and report all of them at the exit gate.
                      ‘Errors are still reported on-the-fly
 
‘Action code goes here
 
‘All the exit gates execute only one command : ActionEnd.
‘It receives two parameters: Boolean for Pass/Fail, 
                            ’string for the exit reason
If CriticalCondition = False Then Call ActionEnd(False, "Reason for exiting")
 
‘Rest of action
 
‘Even the normal successful action exit is managed through ActionEnd, 
’so the last line in every action is:
 
Call ActionEnd(True, "Action successful")
 
Sub ActionEnd(bStatus, sReason)
  ‘Report details
  Reporter.ReportEvent MicGeneral, "Inner Action Logs", sActionReport
 
  If bStatus = True Then
    Reporter.ReportEvent MicFail, "An error has occurred", sReason
  Else
    Reporter.ReportEvent MicPass, "Action successful", "See inner logs"
  End if
 
  ‘Plant datatable info for action-call chain
  DataTable("out_Status", dtlocalsheet) = bStatus
  DataTable("out_Result", dtlocalsheet) = sResult
  ‘More if needed
 
  ‘Close objects and set to nothing here
 
  ‘Other needed exit code
 
  ExitActionIteration
End Sub
 

With this mechanism, maintaining the exit code becomes very simple, and the logs are much more readable. Ok, so this solves the problem for actions, but what about functions? Well, obviously we can write an inner function within a function, but there is an alternative solution. It’s less elegant than the ActionEnd solution by far, and is harder to maintain, so I recommend using it only in a small number of very complex functions.

The solution is based on the Execute command, so I recommend reading about it in QTP’s help file in case you’re not familiar with it. In a nutshell, the Execute command takes a string, and runs its contents as if it were VBScript code. So for instance the command Execute "msgbox(2)" will pop a message box with the number 2. Here’s an example for the solution, applied to the ComplexFunc function:

Function ComplexFunc
  Dim sExitCode
  Dim sResult
  Dim oFile        ‘will be FSO textstream
 
  ’separate code lines by vbcrlf or ":"
  sExitCode =    "oFile.Close" & vbcrlf & _
             "Set oFile = Nothing" & vbcrlf & _
             "ComplexFunc = sResult" 
             ‘More exit code 
 
  ‘Function code goes here
 
  ‘Exit Gate
  If CriticalCondition = False then 
    sResult = "False, No Connection"
    Execute sExitCode
    Exit Function
  End if
 
  ‘More function code
 
  ‘Successful exit
  Execute sExitCode
End Function
 

Creating and Calling user define funtion

2007-12-20T01:45:00.000-08:00

Test Conditons: Creating and Calling user define funtion

1. Crate small add function and make it compile module.

2. calling that function in other test (using user defined data values)

[ Pre Requesties : Nothing ]

1a. open win runner blank test and add this below data

public function add(in a, in b)
{
return a+b;
}

1b. Go to File menu --> Test Properties (Test Properties window will open)
in General Tab --> Test Type= Compile module and ok

1c.Save the test in some location (Ex c:/tt )

2a.Before writing code , you have to load the funtction in to your folder , globally available to all tests.

2b. Go to Tools menu --> General Options
--- Select Folder option in the left pan.
-- Search Path for called test below enter the path of compile module
(c:/tt) and press "+" button to add in to.

2c. Write down the bleow code in the new test

load("c:/tt");
l= create_input_dialog("Enter First value");
j=create_input_dialog("Enter Second Value");
k=add(l,j);
report_msg(k);
unload("c:/tt");

[ load( ) , unload ( ) - to lload and unload from the memory ]

[Same way You can use Winrunner TSL Script to User Defined function

Diff between Image & Bit map Check point

2007-12-19T01:06:00.001-08:00

Image checkpoints enable you to check the properties of a Web image. You can check an area of a Web page or application as a bitmap. While creating a test or component, you specify the area you want to check by selecting an object. You can check an entire object or any area within an object. QuickTest captures the specified object as a bitmap, and inserts a checkpoint in the test or component. You can also choose to save only the selected area of the object with your test or component in order to save disk Space For example, suppose you have a Web site that can display a map of a city the user specifies. The map has control keys for zooming. You can record the new map that is displayed after one click on the control key that zooms in the map. Using the bitmap checkpoint, you can check that the map zooms in correctly.

You can create bitmap checkpoints for all supported testing environments (as long as the appropriate add-ins are loaded).
Note: The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.

How many ways we can parameterize data in QTP?

2007-12-19T01:04:00.001-08:00

There are four types of parameters:
Test, action or component parameters enable you to use values passed from your test or component, or values from other actions in your test.

Data Table parameters enable you to create a data-driven test (or action) that runs several times using the data you supply. In each repetition, or iteration, QuickTest uses a different value from the Data Table.

Environment variable parameters enable you to use variable values from other sources during the run session. These may be values you supply, or values that QuickTest generates for you based on conditions and options you choose.

Random number parameters enable you to insert random numbers as values in your test or component. For example, to check how your application handles small and large ticket orders, you can have QuickTest generate a random number and insert it in a number of tickets edit field.

Choosing a test automation framework

2007-12-19T01:03:00.001-08:00

There are lot of resources on the internet explaining different types of automation frameworks and how to go about selecting one of them those suites your environment.

Below are few links which provide you solid understanding of the software test automation frameworks.

http://www.ibm.com/developerworks/rational/library/591.html

www.research.ibm.com/journal/sj/411/rankin.pdf

http://www.wilsonmar.com/WRSAFS/Docs/CHAPTER1.doc

http://en.wikipedia.org/wiki/Test_Automation_Framework

www.michaeldkelly.com/images/Choosing_a_Test_Automation_Framework.PDF

www.logigear.com/resources/articles_lg/Automation_Framework.pdf

QTP E-books

2007-11-23T03:22:00.000-08:00

You can download the QTP E-books and related material from here.
Just click on the links to download..

check more infomation about AUTOMATION FRAMEWORKS

Using Database Functions

2007-11-09T09:36:00.000-08:00

The code below contains a set of useful functions that can be used in QuickTest Professional.

'Example of how to use functions.

''******************************************************************************************

' Example of how to use DSN created for the database of sample Flight application.

''******************************************************************************************

SQL="SELECT * FROM ORDERS"

connection_string="QT_Flight32"

isConnected = db_connect ( curConnection ,connection_string )

If isConnected = 0 then

' Execute the basic SQL statement

set myrs=db_execute_query( curConnection , SQL )

' Report the query and the connection string

Reporter.ReportEvent micInfo ,"Executed query and created recordset ","Connection_string is ==> " & connection_string & " SQL query is ===> " & SQL

' Show the number of rows in the table using a record set

msgBox " Quantity of rows in queried DB ( db_get_rows_count )==> " & db_get_rows_count( myrs )

' Show the number of rows in the table using a new SQL statement

msgBox " Quantity of rows in queried DB (db_get_rows_count_SQL ) ==> " & db_get_rows_count_SQL( curConnection , "SELECT COUNT(*) FROM ORDERS" )

' Change a value of a field in an existing row

rc = db_set_field_value (curConnection, "ORDERS" , "Agents_Name" , "test", "Agents_Name", "AGENT_TESTER")

' Examples of how to retrieve values from the table

msgBox "val row 0 col 0: " & db_get_field_value( myrs , 0 , 0 )

msgBox "val row 0 col 1: " & db_get_field_value( myrs , 0 , 1 )

msgBox "val row 1 col Name: " & db_get_field_value( myrs , 1 , "Agents_Name" )

msgBox "val SQL row 1 col Name: " & db_get_field_value_SQL( curConnection , "ORDERS" , 1 , "Agents_Name" )

db_disconnect curConnection

End If

''******************************************************************************************

' Database Functions library

''******************************************************************************************

'db_connect

' ---------------

' The function creates a new connection session to a database.

' curSession - The session name (string)

' connection_string - A connection string

' for example the connection_string can be "DSN=SQLServer_Source;UID=SA;PWD=abc123"

''******************************************************************************************

Function db_connect( byRef curSession ,connection_string)

dim connection

on error Resume next

' Opening connection

set connection = CreateObject("ADODB.Connection")

If Err.Number <> 0 then

db_connect= "Error # " & CStr(Err.Number) & " " & Err.Description

err.clear

Exit Function

End If

connection.Open connection_string

If Err.Number <> 0 then

db_connect= "Error # " & CStr(Err.Number) & " " & Err.Description

err.clear

Exit Function

End If

set curSession=connection

db_connect=0

End Function

''******************************************************************************************

' db_disconnect

' ---------------------

' The function disconnects from the database and deletes the session.

' curSession - the session name (string)

''******************************************************************************************

Function db_disconnect( byRef curSession )

curSession.close

set curSession = Nothing

End Function

''******************************************************************************************

' db_execute_query

' ---------------------------

' The function executes an SQL statement.

' Note that a db_connect for (arg1) must be called before this function

' curSession - The session name (string)

' SQL - An SQL statement

''******************************************************************************************

Function db_execute_query ( byRef curSession , SQL)

set rs = curSession.Execute( SQL )

set db_execute_query = rs

End Function

''******************************************************************************************

' db_get_rows_count

' ----------------------------

' The function returns the number of rows in the record set

' curRS - Variable, containing a record set, that contains all values that retrieved from the database by query execution

''******************************************************************************************

Function db_get_rows_count( byRef curRS )

dim rows

rows = 0

curRS.MoveFirst

Do Until curRS.EOF

rows = rows+1

curRS.MoveNext

Loop

db_get_rows_count = rows

End Function

''******************************************************************************************

' db_get_rows_count_SQL

' ------------------------------------

' The function returns the number of rows that are the result of a given SQL statement

' curSession - The session name (string)

' CountSQL - SQL statement

''******************************************************************************************

Function db_get_rows_count_SQL( byRef curSession ,CountSQL )

dim cur_rs

set cur_rs = curSession.Execute( CountSQL )

db_get_rows_count_SQL = cur_rs.fields(0).value

End Function

''******************************************************************************************

' db_get_field_value_SQL

' -----------------------------------

' curSession - Variable that denotes the current active connection

' tableName - Name of the table, from which the value should be retrieved

' rowIndex - Row number

' colName - The column name

''******************************************************************************************

Function db_get_field_value_SQL( curSession , tableName , rowIndex , colName )

dim rs

SQL = " select " & colName & " from " & tableName

set rs = curSession.Execute( SQL )

rs.move rowIndex

db_get_field_value_SQL = rs.fields(colName).value

End Function

''******************************************************************************************

' db_get_field_value

' --------------------------

' The function returns the value of a single item of an executed query.

' Note that a db_execute_query for (arg1) must called before this function

' curRecordSet - Variable, containing a record set, that contains all values retrieved from the database by query execution

' rowIndex - The row index number (zero-based)

' colIndex - The column index number (zero-based) or the column name.

' returned values

' -1 - Requested field index more than exists more than once in record set

''******************************************************************************************

Function db_get_field_value( curRecordSet , rowIndex , colIndex )

dim curRow

curRecordSet.MoveFirst

count_fields = curRecordSet.fields.count-1

If ( TypeName(colIndex)<> "String" ) and ( count_fields < colIndex ) then

db_get_field_value = -1 'requested field index exists more than once in recordset

Else

curRecordSet.Move rowIndex

db_get_field_value = curRecordSet.fields(colIndex).Value

End If

End Function

''******************************************************************************************

' db_set_field_value

' ---------------------------

' The function changes the value of a field according to a search criteria.

' We search for a certain row according to a column name and the desired vale, then we change a value in that row according

' to a desired columns

' curConnection - The session name (string)

' tableName - Name of the table from which the value should be retrieved

' colFind - The column which to search for the criteria

' colFindValue - The value for which to search in the column

' colChange - The column in which we want to change the value

' colChangeValue - The new value

' returned values

' -1 - Requested field index that does not exist in the recordset

''******************************************************************************************

Function db_set_field_value(curConnection, tableName , colFind , colFindValue, colChange, colChangeValue)

dim curRow

dim updateSQL

dim checkSQL

checkSQL = "select * from Details"

set myrs1 = db_execute_query( curConnection , SQL )

myrs1.MoveFirst

count_fields = myrs1.fields.count

If ( TypeName(colFind)<> "String" ) or ( TypeName(colChange)<> "String" ) then

db_set_field_value = -1 'requested field index that does not exists in the record set

Else

updateSQL = "UPDATE " & tableName & " SET " & colChange & "='" & colChangeValue & "' WHERE " & colFind & "='" & colFindValue & "'"

set myrs1 = db_execute_query( curConnection , updateSQL )

db_set_field_value = 1 'operation suceeded

End If

End Function

''******************************************************************************************

' db_add_row

' -----------------

' The function adds a new row to the desired table

' curConnection - Variable, containing a recordset, that contains all the values to be retrieved from the database by query execution

' tableName - Name of the table, from which the value should be retrieved

' values - Array that contains values to be entered in a new row to the table

' Note: The function must receive values for all the columns in the table.

' returned value.

' -1 - The number of values to be entered to the table does not match the number of columns

' 1 - Execution of the query succeed and the data was entered to the table

''******************************************************************************************

Function db_add_row(curConnection, tableName , byRef values)

dim i

dim updateSQL

dim myrs1

updateSQL = "INSERT INTO " & tableName & " VALUES ("

arrLen = UBound (values) - LBound (values) + 1

set myrs1=db_execute_query( curConnection , SQL )

myrs1.MoveFirst

count_fields = myrs1.fields.count

' Check whether the number of values match the number of columns

If arrLen <> count_fields then

db_add_row = -1

Else

For i = 0 to arrLen-1

updateSQL = updateSQL & values (i)

If i <> arrLen-1 then

updateSQL = updateSQL & ","

End If

updateSQL = updateSQL & ")"

set myrs1 = db_execute_query( curConnection , updateSQL )

db_add_row = 1

End If

End Function

''******************************************************************************************

' represent_values_of_RecordSet

' ---------------------------------------------

' The function reports all the values of fields in a record set

' curRS - Variable, containing the recordset, that contains all the values that were retrieved from the database by the query execution

''******************************************************************************************

Function represent_values_of_RecordSet( myrs)

dim curRowString

myrs.MoveFirst

reporter.ReportEvent 4,"Fields quantity" , myrs.fields.count

count_fields = myrs.fields.count-1

curRow=0

Do Until myrs.EOF

curRowString= ""

curRow = curRow+1

For ii=0 to count_fields

curRowString = curRowString& "Field " &"==> " & myrs.fields(ii).Name &" : Value ==>" & myrs.fields(ii).Value & vbCrLf

myrs.MoveNext

reporter.ReportEvent 4,"Current row"& curRow , curRowString

Loop

End Function

Using the File System Object (FSO)

2007-11-09T09:24:00.001-08:00

The following code includes a set of complex and simple functions to serve as examples of the possible uses and applications of Microsoft FSO.

dim oFSO

' Create the file system object

set oFSO = CreateObject ("Scripting.FileSystemObject")

'Option Explicit

' *******************************************************************************************

' Create a new txt file

' Parameters:

' FilePath - location of the file and its name

' *******************************************************************************************

Function CreateFile (FilePath)

' Variable that will hold the new file object

dim NewFile

' Create the new text ile

set NewFile = oFSO.CreateTextFile(FilePath, True)

set CreateFile = NewFile

End Function

' *******************************************************************************************

' Check if a specific file exist

' Parameters:

' FilePath - Location of the file and its name

' *******************************************************************************************

Function CheckFileExists (FilePath)

' Check if the file exists

CheckFileExists = oFSO.FileExists(FilePath)

End Function

' *******************************************************************************************

' Write data to file

' Parameters:

' FileRef - Reference to the file

' str - Data to be written to the file

*******************************************************************************************

Function WriteToFile (byref FileRef,str)

' Write str to the text file

FileRef.WriteLine(str)

End Function

' *******************************************************************************************

' Read line from file

' Parameters:

' FileRef - reference to the file

' *******************************************************************************************

Function ReadLineFromFile (byref FileRef)

' Read line from text file

ReadLineFromFile = FileRef.ReadLine

End Function

' *******************************************************************************************

' Closes an open file.

' Parameters:

' FileRef - Reference to the file

' *******************************************************************************************

Function CloseFile (byref FileRef)

FileRef.close

End Function

'******************************************************************************************

' Opens a specified file and returns an object that can be used to

' read from, write to, or append to the file.

' Parameters:

' FilePath - Location of the file and its name

' mode options are:

' ForReading - 1

' ForWriting - 2

' ForAppending - 8

' *******************************************************************************************

Function OpenFile (FilePath,mode)

' Open the txt file and return the File object

set OpenFile = oFSO.OpenTextFile(FilePath, mode, True)

End Function

' *******************************************************************************************

' Closes an open file.

' Parameters:

' FilePathSource - Location of the source file and its name

' FilePathDest - Location of the destination file and its name

' *******************************************************************************************

Sub FileCopy ( FilePathSource,FilePathDest)

' copy source file to destination file

oFSO.CopyFile FilePathSource, FilePathDest

End Sub

' *******************************************************************************************

' Delete a file.

' Parameters:

' FilePath - Location of the file to be deleted

' *******************************************************************************************

Sub FileDelete ( FilePath)

' Copy source file to destination file

oFSO.DeleteFile ( FilePath)

End Sub

' *******************************************************************************************

' Compare two text files.

' Parameters:

' FilePath1 - Location of the first file to be compared

' FilePath2 - Location of the second file to be compared

' FilePathDiff - Location of the differences file

' ignoreWhiteSpace - Controls whether or ignore differences in white space characters

' true - Ignore differences in white space

' false - Do not ignore difference in white space

' Return Value: true if files are identical, false otherwise'

' *******************************************************************************************

Function FileCompare (byref FilePath1, byref FilePath2, byref FilePathDiff, ignoreWhiteSpace)

dim differentFiles

differentFiles = false

dim f1, f2, f_diff

' Open the files

set f1 = OpenFile(FilePath1,1)

set f2 = OpenFile(FilePath2,1)

set f_diff = OpenFile(FilePathDiff,8)

dim rowCountF1, rowCountF2

rowCountF1 = 0

rowCountF2 = 0

dim str

' Count how many lines there are in the first file

While not f1.AtEndOfStream

str = ReadLineFromFile(f1)

rowCountF1= rowCountF1 + 1

Wend

' Count how many lines there are in the second file

While not f2.AtEndOfStream

str = ReadLineFromFile(f2)

rowCountF2= rowCountF2 + 1

Wend

' Re-open the files to go back to the first line in the files

set f1 = OpenFile(FilePath1,1)

set f2 = OpenFile(FilePath2,1)

' compare the number of lines in the two files.

' assign biggerFile - The file that contain more lines

' assign smallerFile - The file that contain fewer lines

dim biggerFile, smallerFile

set biggerFile = f1

set smallerFile = f2

If ( rowCountF1 < rowCountF2) Then

set smallerFile = f1

set biggerFile = f2

End If

dim lineNum,str1, str2

lineNum = 1

str = "Line" & vbTab & "File1" & vbTab & vbTab & "File2"

WriteToFile f_diff,str

' Loop on all the lines in the smaller file

While not smallerFile.AtEndOfStream

' read line from both files

str1 = ReadLineFromFile(f1)

str2 = ReadLineFromFile(f2)

' Check if we need to ignore white spaces, if yes, trim the two lines

If Not ignoreWhiteSpace Then

Trim(str1)

Trim(str2)

End If

' If there is a difference between the two lines, write them to the differences file

If not (str1 = str2) Then

differentFiles = true

str = lineNum & vbTab & str1 & vbTab & vbTab & str2

WriteToFile f_diff,str

End If

lineNum = lineNum + 1

Wend

' Loop through the bigger lines, to write its line to the different file

While not biggerFile.AtEndOfStream

str1 = ReadLineFromFile(biggerFile)

str = lineNum & vbTab & "" & vbTab & vbTab & str2

WriteToFile f_diff,str

lineNum = lineNum + 1

Wend

FileCompare = Not differentFiles

End function

' ************** Example of using these functions **********************

FilePath1 = "D:\temp\FSO\txt1.txt"

FilePath2 = "D:\temp\FSO\txt2.txt"

FilePathDiff = "D:\temp\FSO\txt_diff.txt"

d = FileCompare(FilePath1,FilePath2,FilePathDiff,false)

FilePath = "D:\temp\FSO\txt.txt"

set fold = FolderCreate ( "D:\temp\FSO

set f = OpenFile(FilePath,8)

' = WriteToFile(f,"test line")

d = CloseFile(f)

set f = CreateFile(FilePath)

Fexist= CheckFileExists(FilePath)

d = WriteToFile(f,"first line")

d = WriteToFile(f,"second line")

d = CloseFile(f)

FileCopy "D:\temp\FSO\txt.txt","D:\temp\FSO\txt1.txt"

FileDelete "D:\temp\FSO\txt1.txt"

Using Microsoft Outlook to Send Email

2007-11-09T09:23:00.001-08:00

The code below illustrates two methods for sending email using the VBScript code in QuickTest Professional, and two different COM objects.

' Example 1

Function SendMail(SendTo, Subject, Body, Attachment)

Set ol=CreateObject("Outlook.Application")

Set Mail=ol.CreateItem(0)

Mail.to=SendTo

Mail.Subject=Subject

Mail.Body=Body

If (Attachment <> "") Then

Mail.Attachments.Add(Attachment)

End If

Mail.Send

ol.Quit

Set Mail = Nothing

Set ol = Nothing

End Function

' Example 2

Function SendMail(SendFrom, SendTo, Subject, Body)

Set objMail=CreateObject("CDONTS.Newmail")

ObjMail.From = SendFrom

ObjMail.To = SendTo

ObjMail.Subject = Subject

ObjMail.Body = Body

ObjMail.Send

Set objMail = Nothing

End Function

Using Microsoft Word Spell Check

2007-11-09T09:22:00.003-08:00

The following code shows a function for checking the number of spelling and grammar errors in a string.

Function NumberOfSpellErrors(strText)

Dim objMsWord

Set objMsWord = CreateObject("Word.Application")

objMsWord.WordBasic.FileNew

objMsWord.WordBasic.Insert strText

NumberOfSpellErrors = objMsWord.ActiveDocument.SpellingErrors.Count

objMsWord.Documents.Close (False)

objMsWord.Quit ' close the application

Set objMsWord = Nothing' Clear object memory

End Function

' The following function uses the Spell errors function to check a specific property

' of all the objects with a given description which are under a given parent

Sub CheckAllObjects(ParentObj, ObjDesc, PropName)

Dim ObjCol, idx, PropValue, OldReportMode

OldReportMode = Reporter.Filter

Reporter.Filter = 2 ' Report only errors

If (IsNull(ParentObj)) Then

Set ObjCol = Desktop.ChildObjects(ObjDesc)

Else

Set ObjCol = ParentObj.ChildObjects(ObjDesc)

End If

For idx=0 to ObjCol.count-1

PropValue = ObjCol.Item(idx).GetROProperty(PropName)

RetVal = NumberOfSpellErrors(PropValue) ' The actual spell check result

If (RetVal > 0) Then

ReportText = "Object #" & idx+1 & ": The '" & PropName & "' Property has " & RetVal & " spell errors (" & PropValue & ")"

Reporter.ReportEvent 1, "Spell Check", ReportText

End If

Reporter.Filter = OldReportMode

End Sub

'''''''''''''''''''''''''''''''''''''

' An example of usage:

' Go over all the static objects in the Login window of the Flight Application

' and for each object check the text for spelling and grammatical errors

'''''''''''''''''''''''''''''''''''''

' Go over all the links in the page and report all the ones that fail the spellcheck

Set Desc = Description.Create()

Desc("nativeclass").Value = "Static"

Set Obj = Dialog("nativeclass:=#32770", "text:=Login")

' Invoke the Flight Application before calling the function

CheckAllObjects Obj, Desc, "text"