When working on a project, you will always need to confirm if your code is up to standard.

No matter how big the project is, you will always need to test the functionality of your code. If you do not check your code’s functionality, it will cause unnecessary problems.

In this article, I will be giving a few guidelines on what you should do when testing your project.

1. Create test logs

When you start testing your website, web application or mobile app, it is always recommended to make notes on every little detail you find while you are testing (i.e. Header seems to overlay with a paragraph or you are unable to continue the form when clicking on the continue button).

Personally, I write down my logs in my notebook, since it’s a good reference for when you want to look back if you are in meetings or you want to remember when exactly you experienced the issue. Writing test logs on a Word document should also suffice.

2. Always compare documentation and mockups

If you are testing, you will need to know what exactly the project’s functionality is and what it should look like. If the description of an input or button element does not match the mockup and document, you will need to log the issue and ensure the issue is dealt with.

If you are not fully sure about the documentation’s description, confirm with the client and colleagues working on the project.

3. Always be thorough with your testing

When you are testing an application, you will need to make sure that everything is working as it is intended. Always ensure that you test every nook and cranny of the application, because if you don’t, you might miss a few issues.

The best thing to do when testing, is to think what a normal user, who has no knowledge of the project, would do. Try to add an extra digit to a phone number or try clicking in between radio buttons or leave an input blank. Anything that can be as simple as pressing a random button could lead to the application breaking – Do whatever you can to break the application so you can find the bugs.

4. Specify the bug’s description and location

When you have logged the bug and notified your fellow colleagues on the issue, always specify where exactly the bug is located. It helps other developers know where the issue is residing and giving specified details on what the issue is doing, helps them figure out what the best course of action is to fix it.

5. Test after submitting fixes

When you are working on a group project, it is very important to test submitted fixes. Every time a colleague has submitted a fix for the application, test the entire application to ensure everything is working. Sometimes, fixing one problem can cause another. It is always best to ensure that your fix hasn’t caused another issue.

It’s also recommended to mark the progress of the bug. If someone is currently working on the logged issue, they will need to change the issue status from To Do to In Progress. If the issue is confirmed fixed, the status can be changed to Done or Complete. This helps narrow down on how many issues are left and what issues have been dealt with.

6. Ensure you have tested on all browsers

When testing your project’s code, always make sure that you have tested on at least three browsers. Most important browsers you should focus on include Google Chrome, Firefox and Safari.

The reason why you need to test on these browsers the most is because the code you used can be displayed differently on another browser. The same goes for responsive testing.

For example, your validation message would display perfectly on Google Chrome, but will display incorrectly on Safari.

The most important key in testing, is communication. If you do not ensure that your communication with your colleagues is properly managed, it will cause miscommunication and possibly lead to unnecessary issues.