Issues & Changes View

The Issues & Changes view lists added and removed screens, errors, and diffs found in all tests in the plan or in a single test.

You can filter the list by the following types of issues:

  • Added screens – Screens that were added to the test and do not exist in the baseline. In a full website test this may be caused by screens that were added to the sitemap.

  • Removed screens – Screens that were in the baseline and do not appear in the current test.

  • Errors found – An error which prevented the test from completing properly. See below for a list of common errors

  • Diffs found – Screens that had visual differences that need to be resolved.

Common Errors

Following are some of the common errors:

  • 401 (Unauthorized) – Autonomous does not have permission to access this page. This can occur if the page is password-protected, requires credentials, or you need to accept cookies before the test opens. To resolve this issue, you can add basic authentication or a customized pre-test. For details, see Flow to Run Before Steps.

  • Error 403 (Forbidden) – The server is blocking access. To resolve this issue, add the website to a whitelist (for assistance contact support), or access the website using a tunnel. For details, see Configuring a Tunnel.

  • Error 404 (Not found) – the URL is not currently available, try again later. If this page no longer exists, you should remove it from the sitemap or the list of URLs.

  • Error 429 (Too many requests) – The server is blocking access. To resolve this issue, add the website to a whitelist (for assistance contact support), or access the website using a tunnel. For details, see Configuring a Tunnel.

  • 500 (Internal Server Error) – Autonomous is unable to establish a connection with the server. To confirm that the server is available, try accessing the URL with your browser.

  • 503 (Service Unavailable) – Autonomous is unable to establish a connection with the server, the server may be temporarily overloaded or down for maintenance. To confirm that the server is available, try accessing the URL with your browser.

  • Parameter does not have a value – The custom flow test uses a parameter which has not been defined in the dataset or list of parameters. For details about assigning a value, see Issues & Changes View.