Overview
This article addresses a common issue where test cases fail on the very first step, the initial loading of the application URL. This may appear as an Initial PageInit failure, a timeout, or a browser error page. This problem often indicates that the Functionize test environment cannot access your application, even if the site is accessible from your local machine.
How It Works
Functionize executes tests from a cloud environment that accesses your application from the public internet. If a test fails immediately when trying to load the URL, it is typically due to network or security configurations that prevent external access. Common causes include:
- The application is hosted on an internal network (intranet) and is not publicly accessible.
- Firewall policies are in place that restrict access from external IP addresses.
- The application requires a specific proxy or tunnel to be accessed from outside the corporate network.
If you have multiple projects and one is working while another is not, check the project-level settings. A common cause for this discrepancy is a missing proxy configuration in the failing project. To resolve this, you must configure the necessary proxy or tunnel at the project level. This ensures that the test execution traffic is routed correctly, allowing Functionize to reach your application.
Contact your internal IT or application team to confirm if a proxy is required and to obtain the correct configuration details. Once configured in the project settings, the URL load failures should be resolved.
Limitations
The Functionize platform, by design, simulates an external user accessing your application. It cannot automatically bypass private network restrictions or firewalls. It is the responsibility of the user to provide the necessary network configurations, such as a proxy or tunnel, to allow the Functionize platform to access the application under test.
Related Info
This section is not applicable.