Just wondering in the event that anyone could aid me out with the testing of a web site. Any guides or hints/tips for any testing of a web site would be genuinely grateful.
Thanks.
What exactly can you use to test
For me, I take the time to validate this page. Bookmark this specific!
Things to watch out for:
- Destroyed links
- Incorrect image paths
- Punctuational and/or grammar mistakes
There are a few accessibility tests around too which tend to be worth a taken. I have used this one before, it’s quite informative.
Before I go, view your website in countless browsers as possible. Firefox, Opera, IE, Chrome, Lynx and Go (although same serps as FF) will be the ones I apply.
POST also view my sites on numerous computers with different resolutions and various screen widths.
If you mean you’ll want to test on ones local computer pertaining to run. php report, may you really need to use appserv http: //www. appservnetwork. com/ for set your computer to server.
What’s your site created with
If it really is built with php in that case: O, you should certainly have had any testing list before you decide to began. I think the most beneficial place to watch out for a php web site is under your hood to just remember to are avoiding SQL treatment, url hacking and various such silliness.
Should you have a html web site then post a new link and I am certain a few of people here can spare a short while to begin diagnostic tests it.
- visual website appeal
- accessibility
- XHTML complient markup
- loading time
- what plugins/languages need to be installed on device viewing site
- what’s coursesmart like in several screen resoloutions and also different OS along with browsers
- content
Sounds quite obvious, but lots of people fail on these kind of criteria.
I beleive a good site needs to be visually appealing, be accessible and still have good content. That’s the most important thing. Visual capture the fancy of attract the targeted visitor, then the content to create the visitor keep. Accesiblity is always a key point to consider becasue in the event that someone can’t navigate around your site, then they probably will leave and never visit.
Valid coding is definitely important. If it isn’t valid code, it may well not render properly.
It always keeps me in the good mood if the site loads fast, however loading time isn’t as much of a trouble as it once was.
If the user deserves certain plugins or even applications installed upon their computer or enabled of their browser (eg adobe flash, javascript) then they may not see your own content or they could just leave becasue they have to install something. An excess of trouble.
Remember to test your web site in different tv screen sizes, with different operating systems and browsers. Try as much combinations as achievable becasue browsers render sites differently from time to time, depending on ones code. You want in making as many individuals as possible have the ability to fully cruise through your web blog without hiccups.
In addition to fianlly, get heaps of people to test your web blog. It may be good to you, but maybe others may have a different impression. Make sure that the visual colours etc opt for what your site is all about. Get the market of the site to test it – they’re individuals who are most probably to visit your webblog, as they are who as well as is aimed at.
Happy site testing!
Be sure to test for elements which shouldn’t work. For example. Should you have
catalog. phppage=one
What the results are if you change a main to two Is niagra correct.
Put improper records in every box and ensure that is validated.
Resize the browser to make sure that your website doesn’t collapse.
Test in older browsers also
I will let you. I have worked as QA
You’ll want to test your site essential building it; step by step. I’m not exactly sure things to make of ones question, so I’ll point you to the current site:
http: //validator. w3. org/
Expect this helps.