>Can anyone recommend a suitable Testing Tools for re-Testing of VFP applications after they have been modified?

I wouldn't focus on a FoxPro specific product when it comes to testing your application. We use Rational Robot but there are others of a similar nature available too. Basically, before we release anything we do manual testing of new features first. And from prior manual testing we have our baseline 'working' set of functionality recorded in Rational as a collection of 'scripts'. So after the new functionality clears testing we then use Rational to run the baseline 'scripts' to make sure everything else still works the same. And once everything clears we alter the baseline scripts again ready for next time.

What the scripts do is record processes similar to how a macro recorder would do it but with the ability to also record actual values, specify what we would call 'fields', and save the data and graphics for later comparison. And the extensive reporting when you run it later does just that, report discrepancies visually - on screen - in the application as you rerun the script. And it's programmable - Rational uses a version of basic for the scripts. Others products use other languages but the results, how they work, are basically the same. So you can start a script with a recording of moving through your program to a specific screen and then augment it to include specific code to enter different values (keyboard it as if someone was really there and let it run unattended) and simply record the results for later reporting or stop on certain conditions. But basically, it lets you create reiterative testing, conditional testing, any kind of functionality testing.. and just let it run with an end report or set it up to be interactive. It's just flexible.

It's great for things that shouldn't have changed. And even where we know some things have changed (say, on a specific form where we have added a new control but the rest of the form is the same) we can either just ignore the warnings about the new control (as it needs that first line testing anyway) and pay attention to the warnings about changes in our non-altered elements. And for the predominant functionality that "should not have changed after that one feature was added on that other screen in that other module" it's perfect to just run a script on the other functionality and read a report/see the visual 'differences' to know that the rest hasn't changed - at least to the extent that our scripts were done well.

This isn't 'Unit Testing' in any way. It's application level testing. Unit testing is something that every programmer(or team of programmers) working on a 'unit' would also write a unit test and deliver the unit test along with the unit itself. Some would argue the unit test gets started first and the unit gets created out of the test. And, in reality, very few FoxPro houses are doing real unit testing. But everyone does some form of application testing. And products like Rational Robot are a big help in that kind of testing.

Hope this helps!