...

• On the designer, rules and PDF mapping pages.
• An informational processing message as shown in the image is displayed after the icon is clicked until the test window opens.
  
  
  
  
• if your form contains business rules they will be validated before the test popup displays and you will see this message:
  
  
  
  
• If form/field validation errors are detected, closing the test popup returns you to the designer where you can quickly make corrections and retest. 
  
  
• Save and Test checks for Rule and pdf mapping errors before the test popup displays. This gives the designer the option to correct first before saving and testing.
  
  
  • If rule validation errors are detected, the designer is notified and given the option to correct before the Test popup is displayed.
    
    
    
    
  • If PDF mapping errors are detected, a warning message with information about the error displays.
    
    
    
    
• The form version increases by 1 every time you click on the save and test icon. It is reflected on the on the form edit page, when viewing/editing submissions and when you download/upload a form.

...

Before you share your new form or flow workflow with users you'll want to test it to make sure it looks and works the way you want. You will want to test that the form is properly validating data entered into each control, that all your rules are correctly causing the behaviors such as show/hide and calculations that you want.

...

1. Install your browser's developer tool. 
2. Test your form and enable the developer tool.
3. Click on the Console tab.
4. Execute this JavaScript function   _frevvo.api.forms.controls.getControlErrors(); Calling this function returns a collection of objects that describe any invalid controls including the control id, control label and the error description. In the image, you can see the reported errors for an Email, Money and Date field that contain invalid data. The controls are inside of a hidden section and are not visible to the user who is trying to Submit/Continue the form/flowworkflow.
   
   

Test your form to verify that all your business rules are working as expected. For instance if you have a radio field "Billing address same as Shipping?" and select "no", you would expect the hidden Shipping Address section to become visible and required. Test each form field that has dynamic business rules to verify that they are working as you want. Also remember to test the negative cases, for example if you then click "yes" to the billing address question, make sure the Shipping Address section control becomes hidden and optional again. Note it's very important that hidden controls are not required as discussed above.

...

You can test the translation files you create and upload into  by clicking the test  icon on the Internationalization screen or you can use the  &locale URL parameter  to initialize the form with other languages. See Multi Language Support for details on creating translations and testing locale translations .

Purging form/

...

workflow test data

Refer to this article for a quick easy way to purge your test data (tasks and submissions)

Internet Explorer Compatibility Mode

If your Forms and flows workflows do not look or work correctly in Internet Explorer, Compatibility View may be turned on. Refer to this article for more information.