>>Does anyone have any experiences with using automated testing tools with VFP?
>>
>>I took a quick look at Visual Test but found out that since VFP apparently uses painted controls instead of real Windows controls, Visual Test is basically useless.
>>
>>I am assuming that other standard Windows testing tools work similar to Visual Test in accessing controls so I am thinking that the best way to provide VFP control access is to have a test tool written in VFP.
>>
>>Any comments/suggestions would be welcome!
>>
>>TIA!
>>
>>-Doug-
>
>Are you sure about that 'painted controls...won't work'? According to what I read at MS (whom I'd trust with my life (ho-ho)), I thought it was only bitmaps added to apps that cause trouble. I have two copies of Visual Test that management (stupidly) was talked into ordering, but I can't say whether there is a graphics problem...because...
>
>Another reason to avoid this product is its complexity. You could spend a long time learning to use it productively. I gave up for that reason alone...

As I understand it, "painted controls" are bitmaps. As you stated, this is a problem.

As far as the complexity goes...with larger projects (as I am involved with), the added cost in implementing and continued development of a formalized test plan can pay for itself several times. Just the time saved in regression testing alone can make it worth it, not to mention the program errors that can be avoided in the first place. Once you know the process you want to follow, it gets easier and productive.

Thanks for your comments!

-Doug-