Quik! provides two different ways to test forms:

...

Before every form is published it reaches the "FINAL" status of the Quik! Forms Build Cycle. This status is to allow form owners the opportunity to review and test their forms before publishing them for end users to access. The Quik! Forms Engine is the primary method for testing a form before it is published, however the test is only intended for the owner of the form. In other words, you won't have the opportunity to test another company's forms made available to you – only your company's forms.
CAUTION: Do not use this test mode in your production environment!

TestFinalFormsMode

To test a form, set the Quik! Forms Engine software "TestFinalFormsMode" property to TRUE: objQFE

 objQFE.TestFinalFormsMode = True

This setting will instruct the Quik! software to pull the form from the FINAL status. For those forms that have been published already, the form that is in FINAL status will be identical to the published form.

...

If your application is built with custom rules for one or more forms, then it is recommended that you set up a copy of your production environment (or a demo account) that turns on the TestFinalFormsMode within Quik!. This will allow you to test a form and your application's integration with Quik! before the form is published to your production environment. This is your opportunity to ensure the form fully functions as expected, especially if the form design changed significantly.

Testing For Form Accuracy

...

To test a form with test data set the TestDataMode to TRUE. objQFE

 objQFE.TestDataMode = True

Running the Quik! Forms Engine in this mode will cause test data to be entered into each text field. The test data is the Quik! Field Name (e.g. "1own.FName" will appear in the the Owner 1 First Name field on the form). This is a nice way to determine what fields appear on a given form.

EXCEPTION: This test data mode cannot populate checkboxes with data, but they can be tested by manually clicking the field.