When you’re writing great software, your testing team will benefit from having a checklist to follow. It keeps everyone on the same page and prevents testing from getting stale. There are many different types of bugs and their fixations, so it’s important to have a list of common pitfalls that other developers don’t catch. Fortunately, there are more than 10 common bugs in UI testing! UITestManagers and testers should know about these issues before they start a project. If you’re not sure if something is a bug or just an oversight, document it here so you can refer back to this list when testing new code. You never know when one of these things might come in handy!

1. The user enters the wrong URL or path.

In the early stages of a project, you’ll probably see many bugs like this one. Your development team has just started to deliver functionality and the user has entered the wrong URL or path. You can catch this by clicking on the URL or path at the bottom of the browser window and entering your site again. You should see the correct page if the user mistyped the path.

2. The view is not rendering as expected.

Again, this is usually due to an issue with the user’s computer. If the page looks correct when the user returns, it’s probably because the computer is set to display the page as it exists on the server. This is known as serving the view. If the computer interprets the view as if the user has sent it to the server, there could be a lot of bugs waiting to be discovered.

3. The user taps twice in a row on the same button

When you tap twice in a row on a button, you’re actually hoping to send the computer a back-to-back tap. Unfortunately, many computers interpret this as a click, so they respond with a double tap. If you tap twice in a row on a button, you’re actually hoping to send the computer a back-to-back tap. Unfortunately, many computers interpret this as a click, so they respond with a double tap.

4. The user selects an item that’s not available to save

If the user selects an item that’s not available to save, there could be a lot of problems. For example, you just added a new feature: a shopping cart. When the user selects the “buy now” button, you need to ensure that the system doesn’t let the user return to the home page without making any changes to their shopping cart. This could be a lot of bugs waiting to be discovered.

5. Data is missing or out of date

Again, this could be due to a lot of things. For example, the user may have deleted their cookies. Or the server may be under a network outage that is preventing it from sending the data you need. Or the user may have mistyped their order. Data may be missing or incorrect if no one updated the record after you created it.

6. There is a missing file, function, or variable

Sometimes you simply don’t have the file or function required to test a code path. For example, you just added a new feature: a shopping cart. When you save the cart to the server, you need to ensure that the user is still able to access and use it. If they made a mistake and clicked on the wrong button, you need to inform them which button caused the problem so they can correct it. This could be a lot of bugs waiting to be discovered.

7. Keyboard Shortcuts are not working properly

At the risk of sounding like a broken record, you should know about keysyndrome. While many people think they’re only a problem with older computers, they can also affect modern web browsers. If a keyboard shortcut doesn’t work as expected, it could be a sign that you need to check the keystrokes themselves. This could be a lot of bugs waiting to be discovered.

8. Conclusion

UITestManagers and testers should know about these issues before they start a project. If you’re not sure if something is a bug or just an oversight, document it here so you can refer back to this list when testing new code. You never know when one of these things might come in handy!