Configure Page Load Settings

When Thunders runs tests on your website, it needs to know when a page has finished loading before it can begin testing. Since different websites load content in different ways, you can customize this behavior to match your site's needs.

Four network settings work together to intelligently detect page load completion, ensuring the system waits for pages to fully load before taking actions like screenshots or interactions.

You might want to customize this if your website:

Navigate to your Test Project → Project Settings → Page Stability Settings tab

The Page Load Settings form contains four configurable fields:

This setting defines how long the network must be completely idle (no pending requests) before considering the page stable. It prevents premature action execution when background requests might still be loading content.

→ Default: 500 (0.5 second)

This is the maximum time to wait for page stability after a URL change/navigation. It acts as a timeout to prevent indefinite waiting on slow-loading pages.

→ Default: 5000 (5 seconds)

This provides an absolute maximum wait time regardless of network activity. It's a safety net that ensures the system doesn't hang indefinitely even if network requests never complete or if it change url.

→ Default: 10000 (10 seconds)

This ensures the system waits at least this minimum time before checking for stability. It prevents false positives where the network appears idle immediately but content is still loading.

→ Default: 200ms (0.2 second)

Click "Save" to apply your custom page load strategy to all future test runs for this project.

To return to the default page load strategy:

Tests are timing out: Try increasing the timeout values.

Tests start too early: Add a post-load delay or include additional loading events.

Pages load slower in tests than expected: Your site might need longer timeouts or a different combination of loading events.