Wednesday, February 2, 2011

Site testing


Aha, you are done with a site!
Is it really done?
What you might want to consider to test? :
  • Cross browser look and feel?
  • Spell & grammar check?
  • Browser check script? (stop user from continuing and browser recommendation)?
  • Have you done a LinkChecker on the site?
  • Have you optimize the site for search engine? Have you put up robots.txt? Have you put up favicon?
  • Have you done a webpagetest.org test on your site?
  • Have you done a country base test on just-ping.com and http://www.websitepulse.com/help/testtools.china-test.html for china users?
  • Is the site ready for mobile users? IPhone? Ipad? Blackberry? Mini opera?
  • Unit Testing for each function in controller of mv"c"?
  • Data entry of invalid values in form fields?
  • Detect and blocking DOS attack?
  • What if facing heavy traffic? Temporary stop execution ? How to detect it?
  • Cross Site scripting by script entry in form?
  • IP Spoofing prevention / proxy connection prevention for transaction?
  • IP filtering to narrow down user access from specific countries?
  • Is the server date and timezone correct?
  • What if multiple user hit concurrently on 1 process? Will duplicate happen?
  • If flash is involved, how to detect for flash block? and put up notices?
  • If you have file protected, is the indexing of directory disabled? Is direct URL access being disabled?
  • Have the website being optimized? (example: setup css and js into separate files)
  • Do you have large files to target specific country audiences? Do you need fast loading? CDN (Content delivery network)?
  • Have you put up notes on project/site objective and target audience?
  • Do you provide font-size adjustment on site?
  • Does the site require multi-lingual in the future? is it ready for that?
  • Do you have logs to track invalid calls or exception on site?
  • Have you combined all functions by avoiding duplicate codes?
  • Have you documented / commented the code?

No comments: