Test execution in Autify Nexus can be disrupted by a variety of factors, including browser configuration problems, network connectivity issues, and errors within individual test steps. This section outlines the most common errors encountered during test execution, explains their likely causes, and provides actionable steps to help you identify and resolve them effectively.
Error: "Timeout 30000ms exceeded waiting for getByRole()"
Autify Nexus was unable to find the target element during test execution.
Resolution
You have many options to resolve this issue.
Re-record the step in the scenario and verify that the correct element can be found
In the step editor, click Advanced settings and add a specific selector
Convert the step into a Playwright step and change the selector being used in the code
Create a new JavaScript or Playwright step and use your own code to target the element and perform an action
Test failures that occur in headless mode
Headless mode executes test scenarios without a visible browser UI, causing some behaviors to differ from headed mode. If a website's implementation does not account for a headless environment, these differences can cause tests to fail.
Examples of unexpected behavior include:
Display issues occur because certain files fail to load.
Human verification screens, such as those originating from Cloudflare, are displayed.
Modal windows do not appear.
Resolution
If a test fails in headless mode, first try running the failed test in headed mode (normal mode) to isolate the issue.
If the test then passes in headed mode, it is highly likely that the issue is not with the test scenario itself, but is being caused by a compatibility problem between the website and the headless environment. In such cases, consider running your tests in headed mode for stable operation.
Unable to click elements that appear on mouseover
When running a test in normal mode (where the browser is visible), you may encounter a situation where elements that appear on mouseover cannot be clicked.
This issue occurs because the actual mouse cursor of the PC overlaps with the browser window where the test is running, which interferes with the automated operation and prevents the mouseover event from being detected correctly.
This problem does not occur in headless mode.
Resolution
When running a test in normal mode, please move your own mouse cursor outside of the browser window where the test is being executed.