Robot GUI map
User Carl Nagle (Carl.Nagle@sas.com.nospam) posted:
The RobotDDEUsers site where "the DDE" resides includes libraries and utilities that support creating and using an Application Map for Robot. You can use the Application Map features with pure keyword driven tests OR with normal Robot scripts. All the sourcecode and documentation is available.
The links of interest on the latter page are:
Re: Robot GUI map
User MArk B. (firstname.lastname@example.org) posted:
But Robot doesn't NEED a GUI map. Thank the QA gods that it was omitted.
Rick Crawford <email@example.com> wrote in message
Does anyone know of a 3rd party GUI map creation app for Robot, ala Segue
Silktest or Mercury WinRunner, where a library of objects is created after
inspecting a form? Not only does this seem like an obvious omission from
Robot but it seems like a great plug in.
Senior QA Analyst
Elite Information Systems
Re: Robot GUI map
User (firstname.lastname@example.org) posted:
Rick, here's how it works in the Robot world:
Robot requires the object class for each GUI object (control) you need to
test to be associated with one of their object types (e.g., "PushButton").
All of the standard Windows classes and many third-party ones (those that
are derived from a standard class) are already associated, or "mapped".
When recording actions against a GUI, if Robot encounters an unknown
object class, you get a dialog prompting you to specify which object type
to associate it with (press Esc key to abort).
Support for custom controls generally requires enabling special
"extensions" (recent versions of Robot have a dialog for selecting which
control sets you need it to support). Also note that in some cases (e.g.,
VBGrid), you have to map a control as type "Generic", then use OLE
automation to get and set property values.
If your application has a lot of unknown controls, Rational has a tool
that supposedly worms it's way through an application that you might be
able to use to automagically identify all unknown controls in one fell