...
There are two ways you can test your forms/workflows. Both methods display the test mode popup which includes the Test Mode Views discussed below.
Method 1: Click the 
save and test icon from within the forms designer to save the changes to your form and automatically display the test popup window. Complete the form in the popup window to test it. When your testing is completed and the test mode screen is closed you will be returned to page in the forms/workflow designers where you clicked the save and test icon if you need form/workflow designer. This makes it easy to make additional changes.
Method 2: Click the 
save and close icon on the Forms Form/Workflow Designer toolbar to save the your changes to your form and exit the form designer. Then click the 
Test icon for the form/workflow on the Forms and Workflows Home Page to enter Test Mode. Complete the form in the popup window to test it.
Both methods display the test mode popup which includes the Test Mode Views discussed below.
The Save and Test feature is not available for frevvo customers integrating with Confluence. The icon can be hidden with a configuration parameter.
Method 1 - Save And Test
The save and test feature reduces form/workflow development time by allowing designers to test forms/workflows, business rules and mapped PDFs without leaving the form designer. Modifications needed after testing can be quickly addressed since you will still be in the form/workflow designer once you close the popup window. This is particularly helpful when building, troubleshooting, and testing forms, business rules and mapped PDFs.
When the save and test is clicked, the form/workflow is saved in the background, and the Test popup window displays reflecting the newly saved version of your form/workflow. The form/workflow will behave exactly as it will when users access it. To test the form/workflow, just complete it as your users would and click Submit. Refer to Test Mode Views for information about the features that are available when the test popup displays.
When you close the Test popup, you will be on whatever designer page you were on when the save and test icon was clicked. This allows the designer to go right back to making changes after closing the Test popup.
- 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.
- If rule validation errors are detected, the designer is notified and given the option to correct before the Test popup is displayed.
- The form/workflow version (visible in the upper right area of the designer) 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.
If you use the Save and Test feature to save the latest versions when developing your form, simply click the Cancel icon when you are ready to leave the designer.Refer to Test Mode Views for information about the features that are available when the test popup displays.
Browser Popup Blocker Message
...
If your browser is configured to block popups, you may see this message the first time you click the save and test icon. If so, clock ok to open the test window then check your browser settings to allow pop-ups.
Method 2 - Save then Test
Of course, you can always click the save and close icon to save the changes to your form but you will be returned to the Forms and Workflows home page after the changes are stored. The test popup is accessed by clicking the Test icon. To continue making modifications to your form you must click the form name or select
Edit from the
Action Menu to return to the form designer for subsequent modifications.
Refer to Test Mode Views for information about the features that are available when the test popup displays.
Test Mode Views
| Excerpt | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
There are three icons in Test mode that you can use to see what your form will look like and how it will work on an iPhone or an iPad. Theses icons appear at the top of the screen - desktop, tablet and smart phone. The default view is desktop.
Clicking on the the tablet and smart phone icons gives you an approximate view of the form on the tablet or phone. You can enter data in the Phone and Tablet views just like you can in the Desktop view to test your form. This is very helpful when designing forms for mobile devices.
|
Testing Your Form
Before you share your new form or 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.
...
The designer can also display a message instructing the user what to do. This method is very helpful to users when trying to determine why a form does not submit. Refer to this topic for the details.
Troubleshooting Hidden Required Fields
Sometimes you'll test your form and see that the form will not submit even when all required fields appear to be filled with valid data. The cause is always a hidden required field with no data or a hidden field with invalid data. Since the field is hidden your users won't be able to enter a value into that required field nor to correct an invalid value in that field and will therefore never be able to submit your form. In a simple form it won't be hard for you to open it in the form designer, find the hidden required field and fix the problem. In a large form or one that has dynamic business logic that makes fields hidden/visible or required/optional or sets values in business rules, you'll need to debug this problem while testing the form.
Step 1
The first step to solving this issue is to understand which control(s) are causing this issue. There are two ways to find the invalid controls, both of which involve using your browser's developer tool. This tool is a great way to find hidden controls which are invalid or required and empty. You can access it by right clicking on a page and selecting Inspect, or by using the keyboard shortcuts indicated for your OS/Browser. The following links point to documentation on developer tools for several supported browsers.
...
- Test your form and enable the developer tool.
- Click on the Console tab.
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/workflow.
Note This JavaScript function will only work in test mode. To execute on a step mid-workflow or even after submission, copy and paste the task or submission URL into a new browser tab, and append the URL parameter ?_test=true to the end of the URL. Now follow the steps above to see the list of controls that are invalid.
Step 2
Once you know which control(s) are causing the problem, you can resolve it.
...
Re-test the form to determine if your changes resolved the issue.
Testing Form/Workflow Customizations
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)