> I am curious about this as well. Do the controls in LabVIEW such as
> sliders, knobs, text boxes, etc. respond to the Rational Visual Test
> product as "windows" controls? If not, this means we cannot automate
> testing of our GUI for regression tests of our LabVIEW app. Visual
> Test does provide for a rough X/Y type of interaction (i.e. click the
> mouse at point (10,35)) but this is error prone and forces updates to
> the test script if the interface look and feel is changed for some
> reason. What is the difference, say, between a native Windows text box
> and a LabVIEW text box? If the LabVIEW control behaves like an ActiveX
> control we might be able to get a handle to its properties and
> methods. If the LabVIEW control is a d
ifferent animal altogether then
> we are stuck. Anybody got an answer to this one?
The answer is that LV controls are indeed internal custom controls.
They do not have child windows and they can be automated using the lower
level points and keys, but not via windows windows.
If you want to, you can use ActiveX controls instead of LV controls. In
my opinion, the programming is way more complicated, but it allows you
to make the tradeoff between the editing and the testing.
Greg McKaskle
