FWIW there is a Test Harness that ships with VFP. A flawed tool at best - especially problematic with XP (though works better under 2000) and useless if your app is launched from an application object based on an activedoc baseclass. There is a 3rd party tool - I think it is called FoxRunner - available though I have not worked with it.
In any case, I would agree a non-intrusive automated testing harness of some kind would certainly be an asset.
>Testing is an expense. Many developers perform rigorous developer tests and use tools like the coverage profiler and debugger and assertions but the problem with these tools is that they are intrusive. How many times have you stepped through problem code in the debugger only to have it work and the have the exact same code fail when the debugger is not open. Basically the debugger, or assertions does not test an application in the same environment that a user running the software (or a third party tool) will test the software. Usually the testing done by developers is sufficient and simply being aware of the fact that enterprise wide automated testing tools don't exist for VFP our developer testing is far more comprehensive than in other languages. That said, the points you raise are valid in my opinion and I too would have hoped for more feedback from others on this topic.
Charles Hankey
Though a good deal is too strange to be believed, nothing is too strange to have happened.
- Thomas Hardy
Half the harm that is done in this world is due to people who want to feel important. They don't mean to do harm-- but the harm does not interest them. Or they do not see it, or they justify it because they are absorbed in the endless struggle to think well of themselves.
-- T. S. Eliot
Democracy is two wolves and a sheep voting on what to have for lunch.
Liberty is a well-armed sheep contesting the vote.
- Ben Franklin
Pardon him, Theodotus. He is a barbarian, and thinks that the customs of his tribe and island are the laws of nature.
