Basic Guidelines for Website Testing

Posted on Apr 7 2009 - 9:08am by Raj

Worldwide web is browsed by customers with different levels of knowledge, while testing websites (static / dynamic) of quality assurance should focus on different aspects to make effective presentation of website in www.

The aspects to cover:
• Functionality
• Ergonomics
• User Interface
• Server side Interface
• Compatibility
• Security
• Performance
• Description


1. Links
The objective is to verify the presence of all the links in the site
All hyperlinks
All internal links
• All external links
• All links Mail
• Check for orphan pages
• Check for broken links
Checking the integrity of the submission of all forms
Field level
• All checks
• All field validations in
• Features create, edit, delete and view
• Treatment of bad entries
• The default values if any (standard)
• Optional Versus Required fields
Make sure that cookies must be activated and how it should be exceeded

Web Indexing
Depending on how the site is designed using metatags, frames, HTMLsyntax, dynamically created pages, passwords or different languages, our site will be looking for different ways
• 1.4.1 Meta Tags
• 1.4.2 Frames
• 1.4.3 HTML syntax
Two types of errors that occur in May web application
a) Data integrity: data incorrect or missing in the table
b) Results of errors: errors in the writing, editing or reading operation in the table
How simple client can visit the website

Navigation describes how the user browses a Web page, the user interface between the various controls (buttons, text boxes, combo boxes, dropdown lists, etc …)
• Application navigation tab is a good (keyboard)
• Application of navigation with the mouse
• Main features accessible from the main / home page (parent window)
• The access keys, control keys access menus

Correctness is whether the information is true or if it contains false information. The accuracy of the information is whether it has correct spelling or grammar. Suppression of information relevant to your site, May cause misunderstandings or confusion
• Spelling and grammar
• Updating of information (mail address IDs help reports)
• General appearance
• Page appearance
• The color, the font size
• Frames
• In accordance Designs
• Symbols and logos (location)
User Interface
• All about exactly how the site looks like (see)
• Basic guidelines for the Web user interface (Microsoft)
• Make sure the screen resolution was taken into account when using the browser itself will resize the user interface that you maximize / minimize it must be tested with different screen resolutions
• check if the number of checks per page were checked, 10 is generally a good number
• Where there are options, the user should be forced to choose among a set of radio buttons and the default value should be at the default message (none, select one … Etc )
• Each menu should have the first choice as N(it could be any other meaning of sentence such as’ Choose one ‘or’ select ‘
• Ensuring persistence of 3.5 for all values when you enter values in a form, and move on the next page and then change back tthe previous screen. Users should not be forced tre-enter all the values again, this must be monitored and guaranteed
• horizontal scrolling is not preferable in general. Avoid using the horizontal scroll bar Ensure that the use of the vertical scroll bar is wise
• Consider the use of pagination where appropriate.
• Ensure that the 3.8 ‘shift click "control over work in list boxes, tclarify these characteristics in both browsers
• The location of the buttons (OK and Cancel) should be at the right hand bottom of the screen and consistent.
• Clarify whether encryption of the password occurs from your login page all the way in the background (the login page does not transmit the password in clear text)
• Should give illegal popup messages (message must be simple and clear)
• Check whether there is an obligation tuse image maps on demand (nnet scape this property
• Positive popup messages should be posted (submitted, deleted, updated, and is allowed)
• Make sure you have several check boxes when multiple selections must be performed
• Avoid long scrolling drop-down list short
• Web site should be small and simple
Interface server side
Interface 4.1 server side
• Check that the communication is made correctly, the web application server, application server, database, break, and vice versa
• Compatibility of server software, hardware, network connections
• Database compatibility
• External interface if necessary
Client side compatibility
• platforms: Check for compatibility with the site
• Windows (95, 98, 2000, NT)
• Unix
• Linux 5.1.3
• Macintosh (if applicable)
• Solaris 5.1.5 (if applicable)
• Internet Explorer (3.x, 4.x, 5.x)
• Netscape Navigator (3.x, 4.x, 6.x)
• Browser settings (security settings graphics, java, etc.).
• Frames and cascading style sheets
• HTML 5.2.6 specification

Loading of graphic images, etc.
• valid and invalid logon
• limits the number of tests
• Can it be bypassed by entering a URL in the page directly in the browser?
• check the log files are kept for the storage of information traceability
• verify the encryption is done correctly if SSL is used (if applicable)
• can access the scripts on the server without authorization
• Connection Speed
• Try with different connection speeds (14.4, 28.8, 56.6, ISDN, cable, DSL, T1, T3)
• Charge
• Perform load test according the SLA (Service Level Agreement)
• What is the estimated number of users per time period and how it will be distributed during the period
• Are there peak loads and how the systems react
• Does your site can manage a large number of users requesting a particular page?
• Is large amount of data transferred from the user?
Stress tests are performed in order to leave a site or some functions to determine how the system reacts
Stress tests are designed to push the limits and test systems and determine if the system recovers gracefully from crashes
Note: Hackers often stress systems by providing load wrong data as it crashes and then have access tit during startup
System of abnormal conditions (stress test)
• Less bandwidth cable
• Low disk memory
• Low CPU speed

About the Author

Leave A Response