INTERACTIVE SAUDI ARABIA LTD
ISA Website Testing Checklist Basic Guidelines and Checklist for Website Testing Ahmed Abdulhamid
,2008 © Interactive Saudi Arabia Limited. All rights reserved. This document or any part thereof may not, without the written consent of Interactive Saudi Arabia Limited (ISA), be copied, reprinted, or reproduced in any material from, including but not limited to photocopying, transcribing, transmitting, or sorting it in any medium or translation it into any language, in any form or by any means, be it electronic, mechanical, xerographic, optical, magnetic or otherwise. The information contained in this document is propriety and confidential; all copyrights, trademarks, trade names, patents and other intellectual property rights in the documentation are the exclusive properly of ISA unless otherwise specified. The information (including but not limited to data, drawings, specification and documentation) shall not at any time, be disclosed directly or indirectly to any third party without the prior written consent of ISA. The information contained herein is believed to be accurate and reliable. ISA accepts no responsibility for its use by any means or in any way whatsoever. The information contained herein is subject to change without notice.
WEBSITE TESTING CHECKLIST
Table of Contents Introduction ......................................................................................................................................3 Functionality......................................................................................................................................3 Links .......................................................................................................................................................... 3 Forms ........................................................................................................................................................ 3 Cookies ...................................................................................................................................................... 4 Web Indexing ............................................................................................................................................ 4 Database ................................................................................................................................................... 4 Usability ............................................................................................................................................5 Navigation ................................................................................................................................................. 5 Content ..................................................................................................................................................... 5 General appearance .................................................................................................................................. 5 User Interface ....................................................................................................................................6 Server side Interface ..........................................................................................................................7 Server side Interface ................................................................................................................................. 7 Client side Compatibility ..................................................................................................................7 Platforms ................................................................................................................................................... 7 Browsers ................................................................................................................................................... 7 Graphics .................................................................................................................................................... 7 Security .............................................................................................................................................8 Performance ......................................................................................................................................8 Connection speed ..................................................................................................................................... 8 Load........................................................................................................................................................... 8 Stress ......................................................................................................................................................... 8
Page 2 of 8
WEBSITE TESTING CHECKLIST
Basic Guidelines and Checklist for Website Testing Introduction Worldwide web is browsed by customers with different knowledge levels, while testing websites (static/Dynamic) QA department should concentrate on various aspects to make effective presentation of website in www.
Functionality Links Objective is to check for all the links in the website
All Hyperlinks All Internal links All External links All Mail links Check for orphan pages Check for Broken links
Forms Check for the integrity of submission of all forms
All Field level Checks Page 3 of 8
WEBSITE TESTING CHECKLIST
All Field level Validations
Functionality of create, modify, delete and view
Handling of wrong inputs
Default values if any (standard)
Optional Versus Mandatory fields
Cookies Check for the cookies that has to be enabled and how it has to be expired
Web Indexing Depending on how the site is designed using metatags, frames, HTMLsyntax, dynamically created pages, passwords or different languages, our site will be searchable in different ways
Meta Tags
Frames
HTML syntax
Database Two types of errors that may occur in web application
Data Integrity : Missing or wrong data in table
Output Errors : Errors In writing ,editing or reading operation in the table
Page 4 of 8
WEBSITE TESTING CHECKLIST
Usability How simple customer can browse the website
Navigation Navigation describes the way user navigate with in a webpage, between different user interface controls (buttons, text boxes, combo boxes, dropdown lists ...etc)
Application navigation is proper through tab (key board) Application navigation through mouse Main features accessible from the main/home page (mother window) Any hotkeys, control keys to access menus
Content Correctness is whether the information is truthful or contains misinformation. The accuracy of the information is whether it is without grammatical or spelling errors. Remove irrelevant information from your site this may otherwise cause misunderstanding or confusion
Spelling and grammar Updated information (contact details mail IDs help reports)
General appearance
Page appearance Color, font size Frames Consistent Designs Symbols and logos (localization)
Page 5 of 8
WEBSITE TESTING CHECKLIST
User Interface All about how exactly website looks like (view) Basic guidelines for web User interface (Microsoft)
Verify whether screen resolution been taken in to account while using browser, will the UI resize itself as you maximize/minimize this must be tested with various screen resolutions verify whether the number of ‘controls’ per page have been checked, generally 10 is a good number Where there are options to choose from, user should be forced to choose from a set of radio buttons and the default should be pointing at default message (none, select one...Etc) Every dropdown box should have the first choice as NONE (it could be any other meaningful sentence such as ‘Choose one’ or ‘select’ Ensure persistency of all values, when you enter values in a form, and move on the next page and then return to change one of the previous screen .The users must not be forced to re-enter all the values once again, this must be checked and ensured Horizontal scrolling is not preferable in general .Avoid using horizontal scroll bar Ensure that the use of vertical scroll bar is judicious Consider the use of pagination where appropriate. Ensure that ‘shift click’ ‘control click ‘work in list boxes, clarify these features work in both browsers The location of buttons (OK and Cancel) should be at the right hand bottom side of a screen and consistent. Clarify whether encryption of the password occurs from your login page all the way to the backend (the login page must not transmit clear –text password) Illegal operations should give popup messages (message should be simple and clear) positive popup messages should be displayed (submitted, deleted, updated, done and cleared) Ensure that you have multiple check boxes when multiple selections is to be performed Avoid long scrolling drop down list make it short website URL should be small and simple
Page 6 of 8
WEBSITE TESTING CHECKLIST
Server side Interface Server side Interface
Verify that communication is done correctly, web server-application server, application server-database server and vice versa Compatibility of server software, hardware, network connections Database compatibility External interface if any
Client side Compatibility Platforms Check for the website compatibility with
Windows (XP, Vista)
Browsers
Internet Explorer Firefox Chrome Browser settings (security settings graphics, java etc...) Frames and cascade style sheets HTML specification
Graphics
Loading of images graphics, etc…
Page 7 of 8
WEBSITE TESTING CHECKLIST
Security
Valid and invalid login limits defined for the number of tries Can it be bypassed by typing URL to a page inside directly in the browser? verify log files are maintained to store the information for traceability verify encryption is done correctly if SSL is used (if applicable) No access to edit scripts on the server without authorization
Performance Connection speed
Try with different connection speeds (14.4, 28.8, 56.6, ISDN, cable DSL, T1, T3)
Load
Perform load test as per the SLA (Service Level Agreement) What is the estimated number of users per time period and how will it be divided over the period Will there be peak loads and how systems react Can your site handle a large amount of users requesting a certain page? Is large amount of data transferred from user?
Stress
Stress testing is done in order to actually break a site or certain features to determine how the system reacts Stress tests are designed to push and test system limitations and determine whether the system recovers gracefully from crashes Note: Hackers often stress systems by providing loads of wrong in-data until it crash and then gain access to it during start-up System abnormal conditions (stress testing) o Less bandwidth of cable o Low disk memory o Low processor speed
Page 8 of 8