>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!
>

I recently purchased MS VT in an attempt to improve testing of a large scale VFP app. I spent approximately 8 hours trying to develop test scripts without success. The problem with painted controls seems to be correct. I have not spent time to investigate the reason for my problems. I read an article in Info-Week, I think, which discussed several win95 based automated testing tools. And guess what, MS VT scored the lowest of those discussed. I am looking for information on RoboTest 95 and perhaps some of the other test tools mentioned in the article. I need to run a pilot test on using automated test tools by December. I will post my findings if I ever get to it. The statement about testing the test scripts is correct. It could take alot of time and effort to develop testing tools for your VFP app. Make sure your client is aware of these factors. Not to mention adding time to the development cycle. HtwH.