1. Functionize
  2. User Guide
  3. Test Editing & Debugging

Network Logs

Follow

Network Logs Overview

The Network Logs feature in Functionize captures essential details of network traffic, including requests, responses, and HTTP status codes. These logs are fine-tuned to filter out irrelevant data, highlighting only the relevant information, which helps in quickly identifying issues like timeouts, failed requests, or DNS resolution errors. This is particularly useful when testing applications that interact with sites behind firewalls from the cloud.

Benefits of Network Logs

  1. Targeted Troubleshooting:

    • By focusing only on relevant information, network logs prevent information overload and allow you to focus on actual problems, making the debugging process more manageable.

  2. Contextual Error Information:

    • Each log is linked to a specific test step, providing a clear picture of what went wrong at the moment of failure. This level of detail is invaluable for understanding the exact scenario leading to the error, helping you make informed decisions quickly.

  3. Actionable Insights:

    • With detailed information at your fingertips, you can take immediate action. For example, if a timeout error is detected, you can look into firewall settings or server performance issues. If a DNS resolution error appears, you can check the DNS settings and ensure the domain name is correctly configured.

Access to Network Logs

To access network logs:

  1. Open the Browser Results Tab:

    • Navigate to the Test Details page with a completed execution.

  2. View Results:

    • Click the View Result button or click the View button to the right of any action.

  3. Access Network Logs:

    • Click the Network tab to view the network log.

Network Errors

When accessing tests both from within and outside your network, you may encounter several network-related errors. Here’s a list of common network errors and their resolutions:

400 Bad Request

  • Description: The server cannot process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
  • Resolution: Check the request URL and parameters to ensure they are correct.

401 Unauthorized

  • Description: The request requires user authentication. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource.
  • Resolution: Ensure that you are properly authenticated and have the necessary credentials.

403 Forbidden

  • Description: The server understood the request but refuses to authorize it. This might be due to insufficient permissions.
  • Resolution: Check your permissions and ensure you have access rights to the resource.

404 Not Found

  • Description: The server can't find the requested resource. This response code is one of the most common and indicates that the URL is incorrect or the resource has been removed.
  • Resolution: Verify the URL for typos and ensure the resource exists.

500 Internal Server Error

  • Description: The server encountered an unexpected condition that prevented it from fulfilling the request.
  • Resolution: This is typically a server-side issue. Contact your server administrator.

502 Bad Gateway

  • Description: The server, while acting as a gateway or proxy, received an invalid response from the upstream server.
  • Resolution: This might be a temporary issue with the upstream server. Try again later or contact the server administrator.

503 Service Unavailable

  • Description: The server is currently unable to handle the request due to temporary overloading or maintenance of the server.
  • Resolution: Wait for some time and try again. If the issue persists, contact the server administrator.

504 Gateway Timeout

  • Description: The server, while acting as a gateway or proxy, did not get a response in time from the upstream server.
  • Resolution: This might be a network issue or a problem with the upstream server. Try again later or contact the server administrator.

Timeout Errors

  • Description: The server took too long to respond, often due to firewall restrictions.
  • Resolution: Ensure that the firewall settings allow traffic to and from the testing server.

DNS Resolution Errors

  • Description: The domain name cannot be resolved, often due to network configuration issues.
  • Resolution: Check the DNS settings and ensure the domain name is correctly configured.

By leveraging network logs in Functionize, testers can effectively troubleshoot and resolve network-related issues, ensuring smoother and more reliable test executions.

Related articles