title: Best way to test a Delphi application
body: <p>I have a Delphi application that has many dependencies, and it would be difficult to refactor it to use DUnit (it's huge), so I was thinking about using something like AutomatedQA's TestComplete to do the testing from the front-end UI.</p>
  
  <p>My main problem is that a bugfix or new feature sometimes breaks old code that was previously tested (manually), and used to work.</p>
  
  <p>I have setup the application to use command-line switches to open-up a specific form that could be tested, and I can create a set of values and clicks needed to be done.</p>
  
  <p>But I have a few questions before I do anything drastic... (and before purchasing anything)</p>
  
  <ol>
  <li>Is it worth it?</li>
  <li>Would this be a good way to test?</li>
  <li>The result of the test should in my database (Oracle), is there an easy way in testcomplete to check these values (multiple fields in multiple tables)?</li>
  <li>I would need to setup a test database to do all the automated testing, would there be an easy way to automate re-setting the test db? Other than drop user cascade, create user,..., impdp.</li>
  <li>Is there a way in testcomplete to specify command-line parameters for an exe?</li>
  <li>Does anybody have any similar experiences.</li>
  </ol>