Testing a LabVIEW application

[Nitrof]

I'm creating an application with LabVIEW. I would like to do some automated test with my GUI. All the user action are detected using Event Structure, which is the best way to build the code... But now I would like to generate user events and do some controls manipulation automatically. I have tried to change the value of controls of my GUI by using references. But it is not considered has a value change from the Event Structure. I also tried the DataSocket but I have the same results. No event...

An other avenue might be the TestStand tool from NI. But my understanding of this tool is that it is able to test SubVI by using it's Inputs and Output connector. Maybe I'm wrong...

If someone as some experience in theses tests. I wou
ld appreciate some good advices in GUI testing.

best regards,

Nitrof

[Mads]

There are two types of the value property, one of them is signaling ("Value (Signaling)"). Use that to generate events when you change the value programmatically.

[DD]

Try changing your control values by reference using the "Value (Signaling)"
property. The difference between this and the standard Value property is
that it generates a change value event. Look for it at the bottom of the
properties list.

"Nitrof" wrote in message
news:5065000000080000007AAB0000-1066448259000@exchange.ni.com...
> I'm creating an application with LabVIEW. I would like to do some
> automated test with my GUI. All the user action are detected using
> Event Structure, which is the best way to build the code... But now I
> would like to generate user events and do some controls manipulation
> automatically. I have tried to change the value of controls of my GUI
> by using references. But it is not considered has a value change from
> the E
vent Structure. I also tried the DataSocket but I have the same
> results. No event...
>
> An other avenue might be the TestStand tool from NI. But my
> understanding of this tool is that it is able to test SubVI by using
> it's Inputs and Output connector. Maybe I'm wrong...
>
> If someone as some experience in theses tests. I would appreciate
> some good advices in GUI testing.
>
> best regards,
>
> Nitrof