I called the Visual Test guys. They told me to forget about using their product with VFP. They said it had to do with the way Foxpro's controls are "painted." They said they were not "true" controls. Apparently, when you use Vis. Test with VB, you can actually test the value in different controls and branch based on that. They said their tool would allow for "blind" macro-like scripts in VFP, but they wouldn't have any idea what they were looking for error wise. They do allow for screen shots to be taken of each screen and saved in a database. Then, when the test script runs, they take another screen shot and compare that, pixel by pixel, with what was saved. I was turned off enough by the idea of so much disk space being eaten up and the problems of screen-resolution that I told them no. They forwarded me to a company that sell a $12,000 box that connects to your keyboard. That will sit and simulate beating on the keyboard of your application too. It cannot read FoxPro controls though, and uses the pixel by pixel tests like Visual Test.

Ultimately, we decided we'd have to build the tool ourselves. That is where we left it. We're looking at having flag in our base classes which will allow for us to hook in a test tool. I intend to write it up if it does/doesn't work.

Marty