Why did my test case fail?

There are three possibilities. Here is what you need to know about each of them:

Bugs or changes in your application

One is that Trudon detected a bug or a change in your application. That is the purpose of Trudon and it’s a good thing. You may also experience caching issues, Javascript trouble, and other pesky errors caused by your application.

To properly identify why it failed, go to the failing step on the test results page, and identify the error message. Look at the screenshot and compare it with previous test runs. It is usually helpful to check several steps before the first failing one as the problem might be from a previously executed action but with incorrect data.

Please note that a test recorded using a web browser often fails on mobile devices, if the responsive design is much different. In this case, record a mobile test using the instructions in the advanced section.

Configuration issues

A second possibility is related to configuration. The most common two cases are:

• Testing pages without authentication, where those pages require previous authentication. Check the Best practices for handling logins article.
• Uniqueness problems, when your database is not reset between tests or some tests run in parallel. It is usually a best practice to not execute tests that create or change something in your app in parallel.

Remember to always setup the proper pre and post-hooks as required by your application flow.

If an element is not found, not visible, not clickable, or uneditable, you can visually check the screenshot. If indeed it is there and looks right, it means there are issues with your selector configuration, which you can define or refine in project settings. If you are not sure what to do, contact us. We’re happy to help.

If an element loading with AJAX fails to show up in the designated time setup by you in settings, you can try adjusting the timeout. Still, it is recommended that you investigate the source of the slowdown in your application, especially if that element has loaded correctly in the past.

Problems with Trudon

An uncommon possibility is failures within Trudon itself, in which case you should contact us immediately so we can find a fix.

Troubleshooting test issues

If your test fails to get past the first step

Make sure your test environment is accessible from the public internet and doesn’t block traffic from bots. If you want to keep your test environment behind a firewall, read the testing private/local environments article.

If your test passes when run locally or manually but fails when run from Trudon cloud

Each new test is executed on a brand new container in a virtual machine. Frequently, cookies or local storage values changes the way your application behaves. If this is the case, you can remove all of them and try to create the test one more time.

Your test fails intermittently

Application performance is highly variable, especially in test or staging environments. If a particular test or step fails intermittently, consider adding a pause step before it or increase the timeout value when starting the test (or test suite).

Your test fails on a hover step

Try replacing the recorded hover CSS selector. Sometimes, depending on how your application changes, we might record the hover action for another element. The most common issue is when another element appears right above the element on hover.