Impact testing warnings and recommendations

Impact testing is designed to work in a test environment on a copy of production data. Impact testing is accessible only when the server is in development or test mode. Because impact testing affects system performance and creates test policy periods that persist in the database, impact testing is not accessible in production mode.

When you run impact testing, impact testing creates test policy periods in the database. In the test environment, observe the following warnings and recommendations:

• The work of users can interfere with impact testing results. During impact testing, Guidewire recommends that only the single user performing impact testing be logged into PolicyCenter.
• Disable integrations to other systems. If you run impact testing with integrations enabled, the integration can send test data to these production systems. For example, disable the free-text search integration that uses the search engine Solr. The same applies to other integrations such as an integration with a billing system. To avoid unnecessary costs, disable integrations to systems that charge access fees.
• While running impact testing batch processes, do not make changes in PolicyCenter that impact rating such as doing a policy change, canceling, or changing rate books. For example, the baseline creation batch process or the test period quote batch process is running. During this time, quoting test periods fails if a user changes or cancels a policy which has a baseline.
• Do not include expired policies in the impact testing dataset. Specify an In Force On date to filter out expired policies.
• Impact testing excludes archived policies.
• Stop the Job Expire batch process to prevent PolicyCenter from unexpectedly expiring policies during or between impact testing runs. To manage batch processes on a test server, press ALT + SHIFT + T to display the Server Tools page, then select Batch Process Info from the Server Tools tab.