Common failures and error messages
This page lists the most common errors you see when a test fails, what each one means and how to resolve it. If the cause is still unclear, select the failed test cases in the Test Recorder and select Assist me to contact CloudQA.
Element with specified selector was not found
Section titled “Element with specified selector was not found”The step couldn’t find its element. Possible causes:
| Cause | How to resolve |
|---|---|
| The page didn’t load, or your application is down. | Check the execution screenshot to confirm the page loaded properly. |
| The page loaded but the element loads slowly and the wait timed out. | Open Edit Steps, add a Pause step with a time in seconds and save. You can also raise the element timeout. |
| The search values changed, for example login credentials that no longer work, so a later element never appears. | Compare the screenshot with the steps performed to see whether the search values were found. |
| The element was removed or is hidden. | Check the screenshot to confirm whether the element is still on the page. |
| The element’s CSS changed, for example after a release, or the selector was invalid. | If the element is still on the page, use Pick CSS in the Chrome extension to get its current CSS path, replace the old selector and run the test again. Use Impact Analysis if many tests use the selector. |
| The element is in an invalid state, such as a disabled element that can’t be clicked. | Check in the screenshot whether the element is enabled and selectable. |
Element not interactable
Section titled “Element not interactable”The page that contains the element hadn’t finished loading before the step needed it, so the step timed out.
To resolve: check the screenshot. If the page is still loading, repeat the steps by hand to gauge its speed. If the page is slow, increase the Element Timeout in Preferences.
Assertion failed
Section titled “Assertion failed”The expected (recorded) value doesn’t match the actual value on the page.
To resolve: hover over or select the failed status to see the actual and recorded text. If the text in your application changed on purpose, update the asserted text and run the test again.
Error occurred while selecting iframe
Section titled “Error occurred while selecting iframe”The execution engine couldn’t find the iframe, or the iframe’s locator changed.
To resolve: use Pick CSS on the element to get the current selector, compare it with the old one and update the step.
Error occurred while executing script
Section titled “Error occurred while executing script”JavaScript in a Script step or assertion raised an error during the run.
To resolve: recheck the script, or run it in your browser’s console to confirm it works.
Internal error occurred
Section titled “Internal error occurred”An internal error occurred on the CloudQA side.
To resolve: run the test case again. If the error persists, contact CloudQA support.