The application is a small ERP (like Quickbooks) written in VFP8, for small businesses. I'm not in charge of the tests, but here is roughly what we use TestComplete for:

- Data input (recorded and script based)
- Produce output and collect results to be compared with expected results
- Regression testing
- Unit tests for VFP COM components

The app is quite large and a full test runs in about 2 hours. The test project was divided in 6 sub-projects and hundreds of sub-sub-projects in order to be able to test parts of the application.

We need to work very close with the test guy. Every change in the UI (menus, forms, etc.) requires to modify the specific test script. We have a full time tester and 2 PCs dedicated to that job. We run at least 1 test every day. We catch 20 to 30% of the bugs with TestComplete. I wish it'd be more, but we'd have to code (in test complete) a lot more to reach 40%.

I remember we had sometimes to fine tweak TestComplete to detect VFP menus or forms. Sometimes we had to add delays and special tricks to get back connexion with the tested app. Nevertheless, TestComplete has all the tools we needed to get the job done and I can't imagine producing commercial software without such a tool.