GUI automation tool (windows)

[Ben Finney]

Lawrence D'Oliveiro <ldo at geek-central.gen.new_zealand> writes:

> In message <i3t449$7cg$1 at reader1.panix.com>, Grant Edwards wrote:
>
> > Automated GUI intended to uncover problems in the underlying program
> > functionality ...
>
> That “underlying” functionality has nothing to do with the GUI, then. Why 
> not test it directly, rather than go through the GUI?

Because that behaviour can be different when tested in a way that
doesn't involve using the actual program's interface.

The GUI is part of the program's behaviour, remember, and just about any
non-trivial GUI program will have quite complex behaviour specifically
in its GUI. Is the concept of testing the actual program behaviour
really foreign to you? If not, what part of this concept is causing you
difficulty?

-- 
 \         “Two paradoxes are better than one; they may even suggest a |
  `\                                         solution.” —Edward Teller |
_o__)                                                                  |
Ben Finney