In last week’s post, we covered the basics of UI testing and how Testomato is a simple service that helps developers automate error checking throughout the UI testing process.
This week we’d like to give you a brief rundown of the types of errors that Testomato actually checks for on an application’s user interface.
When creating a project and configuring your test suite’s settings, you have the ability to run basic tests, which are automatically configured, as well as tests with custom created parameters and possible user interactions that may occur during the use of your application or website.
Testomato is able to detect simple user interface problems without any other customized settings. This means that a basic test suite will test your application or website for the following UI issues:
- Empty or missing pages
- Unexpected error messages within the content on a page, resulting in a broken layout
- Timeouts (the load time is too slow and exceeds the wait time of the average user)
Users also have the option to configure custom tests to fit their needs. Developers can customize their tests to check for the following:
- Errors after sending a form
- Broken or missing UI elements such as menus, titles, etc.
- Ensuring hidden elements (e.g. an edit button) are not present
Basically, Testomato allows developers to automate simple error checks and avoid writing your own tests, or writing new tests each time your application undergoes changes.
While error checking is only one piece of UI testing, it’s an important piece. By automating this part of the user interface testing process, you can save yourself and your team a lot of time and money (and maybe even a migraine or two).
Did you find this post helpful? Have a story to share about UI testing?