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 of 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.

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
  • uniqueness problems, when your database is not reset between tests or some tests run in parallel. You can see a full description of this problem and a quickfix in the section Edit an existing test from the interface

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, but 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.

Powered by BetterDocs