Associating Libraries
|
LoadFunctionLibrary
|
ExecuteFile
|
User needs to specify the path of
library in File->Setings->Resources
|
Way for loading Libraries in runtime.
User needs to use "LoadFunctionLibrary" statement
|
Way for loading Libraries in runtime.
User needs to use "ExecuteFile" statement
|
Associated Libraries will be loaded
in QTP rightaway.
|
Library will be loaded when QTP
executes perticular statement
|
Library will be loaded when QTP
executes perticular statement
|
If library not available in specified
path, that will be displayed in missing resources
|
Library will not be displayed in
Missing Resources Tab. But displays an error when executing the statement if
not available
|
Library will not be displayed in
Missing Resources Tab. But displays an error when executing the statement if
not available
|
The functions which are there in
library will be displayed in QTP Intellisence
|
QTP intellisence doesn't display the
function or variable names after using of the "LoadFunctionLibrary"
Statement
|
QTP intellisence doesn't display the
function or variable names after using of the "ExecuteFile"
Statement
|
Library will be displayed in Resources
TAB
|
Library File doesn't display in
Resources TAB
|
Library File doesn't display in
Resources TAB
|
Functions which are there in the
library will be displayed in Keywords Tab
|
Functions which are there in the
library will not be displayed in Keywords Tab
|
Functions which are there in the
library will not be displayed in Keywords Tab
|
QTP doesn't understand user defined
classes from an associated library
|
QTP doesn't understand user defined
classes from the library which got loaded using "LoadFunctionLibrary"
statement
|
Only way to use classes in QTP. QTP
understands userdefined classes when the library got loaded using
"ExecuteFile" Statement
|
Associated Libraries will be opened
on pressing of F11(Step InTo) at any functiona call
|
Associated Libraries will be opened
on pressing of F11(Step InTo) at any functiona call
|
Library will not be opened in debug
mode.
|
Associated libraries are global to
the test. All actions can use the functions or variables of associated
libraries
|
It has local scope. Only the action
in which this statement got executed can use this.
|
It has local scope. Only the action
in which this statement got executed can use this.
|
Accepts Relative and absolute Paths
|
Accepts Relative and absolute Paths
|
Accepts Relative and absolute Paths
|
Please send your Suggestions and Doubts to my yahoo group http://in.groups.yahoo.com/group/qtpsudhakar
Thanks lot.
ReplyDeleteJeet
Your grid was helpful in many ways. I especially appreciate knowing that QTP will not recognize classes in the .vbs file.
DeleteThanks,
Kevin
Good one
ReplyDeleteKevin.. QTP will recognize classes in .VBS file only, not from function libraries..
ReplyDeleteKevin... QTP will recognize classes from VBS file only ..not from function libraries.
ReplyDeleteNice Info.. :)
ReplyDeleteExcellent blog
ReplyDeleteExcelleng blog.
ReplyDeleteI want to know will it makes a difference in terms of resource utilization. Usually we associate library to a test because of which it takes almost 30 secs for any test to start execution. Will it make a difference in terms of time if we use LoadFunctionLibrary ?
No difference. LoadFunctionLibrary is just to load libraries in run time. The delay depends on the code in library.
DeleteQTP will recognize classes in both .vbs and .qfl files. But we need to use the executefile statement to load the libraries
ReplyDeleteWe can use .vbs, .txt, .qfl files as libraries. QTP will find classes only when you load above files using executefile statement.
ReplyDelete