Using Rational Visual Test DLL with Robot
User (Nigel_Mason@cls.canon.co.uk.nospam) posted:
I am pretty new to Robot, but have extensive experience with Rational
Visual Test (VT). To me it seems like Robot has a lot less user friendly
functionality than that of VT.
I would like to know if anybody has successfully used the VT dll
"VTest60.dll" to access functions and subroutines such as WMenuCount,
WViewItemClk ... you should be able to guess what the routines do from
the names, and there are a great many useful ones which would seriously
enhance the use of Robot, especially where localisation testing is
I have used the declare function / sub ... to successfully access the
routines from the robot scripts, but the expected actions do not happen
and function return values are generally -1 or a Robot Crash.
If anybody has any advice, suggestions or examples (excluding the
CWPHooker stuff), please let us know
Re: Using Rational Visual Test DLL with Robot
User (email@example.com) posted:
Please see my comments below.
That's funny, because I would say the opposite is true. VT 4.0 seems
clunky and non-intuitive, though I imagine it has improved in more recent
versions (has it???). The main drawbacks I noticed with VT 4.0 were it's
inability to record actions at a "high" level, and dependency on mouse
coordinates, which seemed to fail a lot on playback.
I'm not familiar with this particular DLL, but have used Windows API
extensively. A small percentage of the WIN API functions I've used did
not work for me (even though Appleman's VB 5 Programmer's Guide to the
WIN32 API book claims they work with Visual Basic), but the vast majority
Same with most VB Subs/Funs, though SQA Basic does not support all of the
VB data types.
I put my declarations in an SQA Basic header file (.sbh), but you can also
declare them from a script (.rec).
How can you say you successfully accessed the routines??? This is
obviously not the case. Possible reasons are many. Here are a few things
to look into:
1. The declaration is incorrect in one or more ways.
2. Values passed in the function call do not meet requirements of the
function. They may be the wrong data type, length, reference type (by
Value or Reference).
3. The function calls VT-specific code that cannot execute properly
outside of the VT environment.