--- Paolo Amoroso amoroso@mclink.it wrote:
By the what, what does a GUI test suite look like?
Hmm, interesting question actually! The only ones I can recall seeing usually seem to test if something is displayed properly by running through a bunch of "test" applications and watching for errors reported, or don't do anything automatically but consist of demo programs which are intended to exercise parts of the code.
More interesting might be to store pixmaps or vector descriptions of correctly rendered test windows/apps, compare internally an internally rendered bitmap to the stored "correct" version, and see if there is any difference. Advantages: doesn't need to display anything onscreen, and thus doesn't need a graphical desktop to do "real" testing. Disadvantages: space intensive and rather difficult to code.
Much of the code could probably use ordinary unit testing, the challenge would be ones where the output of interest is graphical. Nifty to think about.
Cheers, CY
____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs