Test policies

Before you activate your Script Management policy in production, test it carefully in staging.

You can use Script Management's testing suggestions as a way to help find pages that might be affected, but be sure to test all types of pages on your site. In particular, check that any important functionality for your users is working correctly.

  1. Create a Script Management policy, and activate it in staging.

    Activation usually occurs very quickly, but allow up to 15 minutes. You can also download the Script Management Policy Tester from the Chrome web store to help you test.

👍

You'll receive an Account activity message in the Control Center when you activate a Script Management policy in production or staging. All users associated with the account will also get this message.

  1. Navigate to the Script Management application, and view the Dashboard for your policy.

  2. Find a script that is blocked or deferred, and identify a page on your site that references that script.

📘

Script Management offers some testing suggestions. To access them on the Dashboard, click the information icon. To access them when editing a policy, select a script or group to view the About panel.

The testing suggestions do not include all pages referencing blocked or deferred scripts, only the pages that have the highest popularity ratings.

  1. Using the Script Management Policy Tester, select the staging version of your policy, and access one of the pages you identified.

📘

The first request you make to a hostname only loads the service worker. Reload the first page you request to see the effects of your Script Management policy.

  1. Check that the policy version shows the time stamp of the policy you last activated in staging. If the correct policy version is not active, refer to the troubleshooting instructions.

  2. If you find any issues in testing, edit your policy, activate in staging, and test again. When you are happy with your policy, continue with going live.