Restricted Third-Party Scripts

To ensure automated tests run reliably, consistently, and safely, CheckView may automatically block or restrict certain third-party scripts during test execution. These scripts can interfere with the browser bot’s ability to complete actions, cause unexpected failures, or consume excessive resources that make testing unstable.

Why Certain Scripts Are Blocked

Scripts may be restricted for one or more of the following reasons:

• Excessive size – Extremely large scripts (sometimes 10MB+) can overload the bot’s available CPU and memory, leading to crashes or incomplete test runs.
• Inconsistent behavior – Some scripts trigger only under specific conditions (e.g., screen resolution), making failures unpredictable and inconsistent.
• Navigation interference – Scripts that alter DOM handling, block navigation, or override standard browser interactions can prevent tests from completing.
• Security or stability risks – Certain external assets may introduce stability concerns or impact test environment isolation.

When blocked, these scripts will not load during CheckView test runs. While this means some embedded functionality may not be directly testable, blocking ensures the broader site functionality can still be reliably validated.

Currently Blocked Scripts

The following third-party scripts are currently blocked by default in CheckView:

• static.matterport.com – Matterport’s embedded 3D viewer script has been shown to interfere with navigation and cause resource overuse during testing.

What This Means for Your Tests

• Your site will continue to be tested normally – core workflows like checkout, logins, and forms are unaffected.
• Blocked scripts won’t load during test execution – If your site relies on a restricted script for critical functionality, please reach out to our support team to discuss possible workarounds.
• We review and update regularly – CheckView monitors issues caused by third-party scripts and updates this list to ensure optimal reliability.