Overview

Quik! provides two primary ways to test forms before they are made available to end users:

Test forms before they’re published, while they are in FINAL status
Prefill forms with test data (HTML only)

Testing Forms in FINAL Status

Before every form is published, it reaches the FINAL status in the Quik! Forms Build Cycle. This status allows form owners to review and test their forms before publishing them.

The Quik! Forms Engine is the primary method for testing a form while it is in FINAL status. This testing capability is intended only for the owner of the form. You cannot test another company’s forms, only forms owned by your organization.

Note: If you plan to test forms before they go live, please notify our Forms Team at forms@quikforms.com when submitting your forms. This will allow us to keep the forms in Final status until you have completed your testing.

CAUTION: Do not use test modes in your production environment.

TestFinalFormsMode

To test a form in FINAL status, set the Quik! Forms Engine property:

"TestFinalFormsMode": true

This setting pulls the form from FINAL status instead of the published version. For forms that have already been published, the FINAL version will be identical to the live version.

TestDataMode (HTML Forms Only)

To test a form with automatically generated test data, set:

"TestDataMode": true

When enabled, the Quik! Forms Engine inserts test data into each text field. The test data is the Quik! Field Name itself (for example, 1own.FName will appear in the Owner 1 First Name field).

This is a useful way to quickly identify which fields appear on a form.

Exceptions

Checkboxes are not populated automatically, but can be tested by manually selecting them.
Formatted fields (such as SSN) do not prefill test data.

Important:

TestDataMode is available only when generating HTML forms (Execute HTML).
This property is not supported when using the Execute PDF endpoint.

REST Example (Execute HTML)

The following example demonstrates testing a form in FINAL status using Execute HTML, with optional test data enabled:

{
  "HostFormOnQuik": true,
  "QuikFormID": "12",
  "TestFinalFormsMode": true,
  "TestDataMode": true,
  "FormFields": [
    {
      "FieldName": "1own.FName",
      "FieldValue": "John"
    },
    {
      "FieldName": "1own.LName",
      "FieldValue": "Smith"
    }
  ]
}

Testing with Execute PDF

When testing forms using the Execute PDF endpoint:

TestFinalFormsMode is supported and can be used to pull forms from FINAL status
TestDataMode is not available
Any test data must be supplied explicitly using FormFields

Testing How Forms Affect Your Application

If your application includes custom logic or rules tied to specific forms, it is recommended that you set up a non-production environment (such as a demo or staging environment) with TestFinalFormsMode enabled.

This allows you to test both the form and your application’s integration before the form is published to production, ensuring compatibility, especially when form designs change significantly.

Testing for Form Accuracy

While reviewing forms for completeness and accuracy is always recommended, it is not always required. Every Quik! form goes through a rigorous build and review process involving multiple reviewers.

Although you are responsible for validating forms for your use case, many customers rely on Efficient Technology Inc. to publish forms automatically. If an issue is identified, it is addressed immediately.

How Do I Test a Form?