Test an Interview

After you have defined your interview in Policy Modeling, you should test it to ensure that your screens are effective and work as expected. You can use the Debugger to test your interview rules and screens. To start debugging an interview:

1. Launch the Policy Modeling Debugger. The Debugger opens to the Interview tab. The first screen in the interview will be shown.
   
2. Starting on this screen, work your way through the interview screens in the right hand pane, providing answers and:
   • checking screen and control appearance and behavior
   • checking screen and control text. This involves checking that:
     • question text makes sense
     • any substituted attributes are appearing where you had anticipated
     • there are no spelling errors

   You can choose to have your answers used in the inferencing even when they haven't yet been submitted. For more information, see Debug Unsubmitted Interview Values. Note that you must answer questions in the format specified by the project region for your policy model.

3. Continue moving through the interview until no more question screens are presented to you. You can then:
   • Review the Data Collected
   • Review the Reason for a Decision
   • Review a Form Generated From an Interview
   • Review the Attachment of Generated Files

Other tests you might like to perform if appropriate include:

• Testing the interview in a browser. To do this, in Policy Modeling, click Ctrl+F5 to open the interview in your default browser. Alternatively, you can hold down the Ctrl key while clicking on the Debug button in Policy Modeling to test the interview in a browser. (Note that if you are using a computer where the keyboard function keys have secondary functions (for example, F5 may also be used to change the brightness of the screen), you may need to use Ctrl+Fn+F5.)
• Debugging custom controls, interview extensions, custom CSS styles and so on using Chrome DevTools with the Debugger. The Console tab in DevTools is also where any errors on the web page are shown. To access DevTools from the Debugger, click F12. Alternatively, you can use the Developer tools menu option in the Debugger to open the DevTools browser window. For more information on using DevTools, see the Chrome for Developers DevTools documentation. Tip: You can place breakpoints in your custom JavaScript file in the project and then DevTools will stop on the breakpoint and the Debugger will indicate that it paused on a breakpoint.
• Testing an interview with mapped data. When using the Debugger, no data from the connected application will be loaded or saved. In order to test your data mappings, the policy model needs to be deployed to your Intelligent Advisor Hub. For more information, see Test an Activated Interview.
• Testing interview session data when authoring and testing an interview in an integrated environment
• Testing a policy model containing decision service references
• Testing the interview in different languages
• Testing the interview in different screen sizes
• Testing custom controls through a proxy server (August 2016 version interviews)