Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Quik! provides two different ways to test forms:

  1. Test forms before they're published, while in FINAL status.
  2. Prefill forms with test data

Testing Forms In Final Status

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. 

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 this test mode in your production environment!

TestFinalFormsMode

To test a form, set the Quik! Forms Engine property "TestFinalFormsMode" property to TRUE.
This setting will 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.

TestDataMode

To test a form with test data set the TestDataMode to 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.

EXCEPTIONS:

  • This test data mode cannot populate checkboxes with data, but they can be tested by manually clicking the field.
  • Formatted fields (such as SSN) will also not prefill test data.

REST Example for Testing Final Forms

{
	"HostFormOnQuik": true, 
	"QuikFormID": "12",
	"TestFinalFormsMode": true, 	// Set this property to true to test recent forms changes in Final status
	"TestDataMode": true,		    // Set this property to true to prefill test data 
	"FormFields": [
		{
			"FieldName": "1own.FName",
			"FieldValue": "John"
		},
		{
			"FieldName": "1own.LName",
			"FieldValue": "Smith"
		}
	]
}

Test How Forms Affect Your Application

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

While testing a form for being complete or accurate is generally a good idea, it isn't always necessary. Every form within Quik! goes through a rigorous build process that includes testing by multiple people. While it is your responsibility to ensure forms are built properly, they generally are built well and many customers rely upon Efficient Technology Inc to publish forms automatically. If an error is found, it is fixed immediately.


  • No labels