Aborted Tests
A test is marked as Aborted if it did not complete successfully or was stopped by the user. If the test was aborted by the system, check that the tunnel is configured correctly. For details see Configuring a Tunnel
If the tunnel is configured correctly, you should look at test details and may need to contact support. For details see Viewing or Copying Test Details.
Server 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.
No sitemap file found
Problem:
Autonomous is unable to find the sitemap, or there is no sitemap file.
Solution:
By default, Autonomous looks for a sitemap file in the root directory, the file must be named sitemap.xml or listed in the sitemap.xml file. This error appears if Autonomous is unable to find a sitemap file. To resolve this problem try one of the following:
Add a sitemap file named sitemap.xml to the root directory.
If there is a sitemap file with a different name or in a different location, when creating the full website test, enter the full path to the sitemap file instead of the root directory.
Comments
0 comments
Please sign in to leave a comment.