Can robot cope with graphical interface implemernted using a package called ILOG
User Era (firstname.lastname@example.org) posted:
I am about to start a project that is going to use a graphical interface
(LIMS, the Inventory Mngt System) It will be implemernted using a package
The ILOG JViews Component Suite allows Java developers to create highly
customised and visually rich GUIs that go far beyond what the simple
components provided by HTML, Swing, and AWT allow. Add a broad range of
advanced displays to Java GUIs, including smart maps, data-aware custom
graphics, workflow and network diagrams, and scheduling charts. Allow your
end-users to view and interact with their business data in the most
intuitive way! Features, performance and flexibility: The ILOG JViews
Component Suite is designed to help build the most demanding Java GUIs
I wanted to know if anyone has experience of driving ILOG-derived dialogs
with Rational Robot.
Re: Can robot cope with graphical interface implemernted using a package called ILOG
User (email@example.com) posted:
The best way to evaluate Robot's ability to test applications built using
a particular development tool and control set(s) is:
1. Identify which controls your company would use in their GUI (this
includes the 'native' controls that come with the IDE, and any third-party
control sets such as Sheridan's 'Threed Grid'). Make these controls the
top priority for the evaluation. Also, for any controls that have a wide
range of 'configurability', e.g., property settings that affect how they
appear and operate, try to get specifics on how your development team
would use them!
2. Identify any controls that are "painted on" (do not have window
handles), and any alternative controls that perform the same function. Do
everything in your power to convince your development team to use the
testable controls instead of the non-testable ones.
3. If your development team has not already built the application, get
them to build you a sample application that has all of the high priority
controls (or better yet, ALL of the controls).
4. Using the sample app or the real thing, verify that you can
successfully record and playback representative actions against all of the
high priority controls, and that you can see and capture all relevant
properties using SQABasic functions and "verification points" (at LEAST
SQAGetProperty() and the Object Properties VP).