When testing a website that you’ve created the best idea is to have someone else do the testing.  If you created it then chances are you’re too close to the project to see the potential issues.  You know how the site works and how to navigate your way around but how will it feel for someone visiting the site for the first time?  A fresh set of eyes will bring an objective opinion to the functionality and flow of the site.  Someone who has never seen it before will be a better representation of the average user than you who has been so close to the project for so long.  If for some reason you don’t have anyone that can help then here are a few simple techniques you can use to troubleshoot the site.

1) Don’t take anything for granted. Don’t assume the visitors are going to be computer savvy and will be able to figure everything out, in fact assume the opposite.  Obviously if your website is dedicated to advanced computer programming or how to correctly texture a 3d nurb model then you can make some assumptions about the user.  If your site however is set up to sell Christmas cards that you made then you need the site to be ready for the most basic of users.  You’ll need to pay attention to the flow of the site; is the path the user will follow the most efficient one?  Make sure all of the buttons work.  Make sure the input fields are accepting data.  If you have a site map make sure that each item is linking to the correct place on the site.

2) Now that you’ve got the basic tests out of the way expand upon them. You know the flow works well for a first time user but how does it work for a returning user?  Maybe the flow is only efficient the first time and a new flow needs to be created for returning users.  You know that the buttons work when they’re clicked so now click them multiple times, do they still work?  You know that your site will correctly store information that was entered into the fields so now try entering unfriendly information into those fields.  Enter capitals and spaces and periods where they don’t belong.  Fill the fields all the way full and try submitting, how does your site handle it?

3) If you’re an advanced website developer and know how to set up scripts to test the site then try that too. Pretend you’re a hacker and try to break your own site.  These types of tests won’t need to be run on a site that’s providing general information but will need to be run on a site where anything is being sold.  Any sort of e-commerce site will definitely need to be tested for holes.

These are just a few examples of tests that can be run and there are many others depending on the type of site you are building.  The bottom line is that thorough testing needs to be done to ensure the best experience for the user and if you built the site then you are too close to the project to see the potential holes that exist.