My Personnel checklist

Check List for Web Testing
Type of Testing	Factors	Description	Status
GUI	RESOLUTION	Screen resolution (check that text and graphic alignment still work, font are readable etc.) like 1024 X 768, 600x800, 640 x 480 pixels etc
	LAYOUT	Layout of all the pages in the website should be similar.
	COLOUR	Colour depth (256, 16-bit, 32-bit)
	VISUAL	Images and color of images should be clearly visible both in black & white and color monitors
	CSS	Check whether the style settings i.e. font size, face, tool tips, etc are getting affected in the page for each and every item applied.
	PAGE TITLE	Check the page title of each and every page.
	FIELDS	Are all the field prompts spelt correctly?
	FONTS	Are fonts too large or too small to read?
	COMMAND BUTTON & OPTION	Are names in command button & option box names are not abbreviations.
	GROUP BOX	Assure that option boxes, option buttons, and command buttons are logically grouped together in clearly demarcated areas "Group Box"?
	USER	Can the typical user run the system without frustration?
	PRINT	Do pages print legibly without cutting off text?
	CONVEY	Does the site convey a clear sense of its intended audience?
	LOOK AND FEEL	Does the site have a consistent, clearly recognizable "look-&-feel"?
	USER LOGIN	Does User cab Login Member Area with both UserName/Email ID ?
	CUSTOM SERVICE	Does the system provide or facilitate customer service? i.e. responsive, helpful, accurate?
	TERMINOLOGY	Is all terminology understandable for all of the site’s intended users?
	ICON OF WEBSITE	1.Start Application by Double Click on its ICON.
		2.Clicking on the icon on every page shpul redirect to home page.
	LOADING MESSAGE	Check the loading message should show the Application Name, Version Number and a bigger pictorial representation of the icon.
	NO LOGIN	No Login is necessary.
	SAME CAPTION	Check whether the main window of the application should have the same caption as that of the icon in Program Manager.
	CONFIRMATION MESSAGE	Closing the application should result in a Confirmation Message Box.
	START APPLICATION	Attempt to start application "twice" should not be allowed . User should return to Main Window while doing so.
	HOUR GLASS	On each window, if the application is busy, then the hour glass should be displayed. If there is no hour glass (e.g. alpha access enquiries) then some enquiry in progress message should be displayed.
	HELP OPTION	All screens should have a Help button, F1 should work doing the same.
	WINDOW OF APPLICATION	1. If Window has a Minimize Button, click it.Window Should return to an icon at the bottom of the screen
		2. This icon should correspond to the Original Icon under Program Manager
		3. Double Click the Icon to return the Window to its original size.
		4. The window caption for every application should have the name of the application and the window name - especially the error messages.
		5. These should be checked for spelling, English and clarity , especially on the top of the screen. Check whether the title of the window makes sense or not.
		6. Check all text on window for Spelling/Tense and Grammar
		7. Use TAB to move focus around the Window. Use SHIFT+TAB to move focus backwards.
		8. Tab order should be left to right, and Top to Bottom within a group of text boxes on the screen.
		9. All controls should get focus - indicated by dotted box, or cursor. Tabbing to an entry field with text in it should highlight the entire text in the field.
		10. The text in the Micro Help line should change - Check for spelling, clarity and non-updateable etc
		11. If a field is disabled (grayed) then it should not get focus. It should not be possible to select them with either the mouse or by using TAB. Try this for every grayed control.
		12. Never updateable fields should be displayed with black text on a grey background with a black label
		13. All text should be left-justified, followed by a colon right to it.
		14. In a field that may or may not be updateable, the label text and contents changes from black to grey depending on the current status.
		15. List boxes are always white background with black text whether they are disabled or not. All others are grey.
		16. In general, do not use goto screens, use go sub, i.e. if a button causes another screen to be displayed, the screen should not hide the first screen.
		17. When returning, return to the first screen cleanly i.e. no other screens/applications should appear.
		18. In general, double-click is not essential, everything can be done using both the mouse and the keyboard
		19. All tab buttons should have a distinct letter.
	TEXT BOXES	1. Move the Mouse Cursor to all Editable Text Boxes.Cursor should change from arrow to Insert Bar. If it doesn't ,then the text in the box should be grey or non-editable.
		2.User should be restricted to a certain number of characters to enter in a particular field,so that data overflow errors do not occur.
		3. Enter invalid characters - Letters in numeric fields, try strange characters like + , - * etc. in All fields.
		4. SHIFT and Arrow should Select Characters. Selection should also be possible with mouse. Double Click should select all text in box.
	RADIO OPTIONS	1. Left and Right arrows should move 'ON' Selection. So should Up and Down. Select with mouse by clicking
		2.Only one should be selected from given option.
		3.User can able to select any option using mouse or keyboard.
		4.Arrow key should set or unset the radio buttons.
	CHECK BOXES	1. Click with the mouse on the box, or on the text should SET/UNSET the box. SPACE should do the same
		2.User should be able to select any combination of check boxes.
	PUSH DOWN BUTTONS	1.All buttons except OK/Cancel should have a letter access to them. This is indicated by a letter underlined in the button text. The button should be activated by pressing ALT
		2.Clicking each button with mouse should activate it and trigger required action
		3.Similarly, after giving focus SPACE or RETURN button should also do the same.
		4.If there is any Cancel button on the screen, pressing Esc should activate it.
	COMMAND BUTTON	1. If Command Button leads to another Screen, and if the user can enter or change details on the other screen then the Text on the button should be followed by three dots.
		2. All Buttons except for OK and Cancel should have a letter Access to them.This is indicated by a letter underlined in the button text. The button should be activated by pressing ALT+Letter. Make sure there is no duplication.
		3. Click each button once with the mouse - This should activate
		4. Tab to each button - Press SPACE - This should activate
		5. Tab to each button - Press RETURN - This should activate
6. If there is a Cancel Button on the screen , then pressing should activate it.
7. If pressing the Command button results in uncorrectable data e.g. closing an action step, there should be a message phrased positively with Yes/No answers where Yes results in the completion of the action.
DROP-DOWN LIST BOXES	1. Pressing the Arrow should give list of options. This List may be scrollable. User should not be able to type text in the box
	2. Pressing a letter should bring User to the first item in the list, which starts with that letter. Pressing ‘Ctrl + F4’ should open/drop down the list box.
	3. Spacing should be compatible with the existing windows spacing (word etc.). Items should be in alphabetical order with the exception of blank/none which should be at the top or at the bottom of the list box.
	4. Drop down with the item selected should display the list with the selected item on the top.
	5. Make sure only one space appears, shouldn't have a blank line at the bottom.
COMBO BOXES	1. Should allow text to be entered. Clicking Arrow should allow user to choose from list
LIST BOXES	1. Should allow a single selection to be chosen, by clicking with the mouse, or using the Up and Down Arrow keys.
	2. Pressing a letter should take you to the first item in the list starting with that letter.
	3. If there is a 'View' or 'Open' button beside the list box then double clicking on a item in the List Box, should act in the same way as selecting an item in the list box and clicking the command button.
	4. Force the scroll bar to appear, make sure all the data can be seen in the box.
COMPATIBILITY	BROWSERS	1 Is the HTML version being used compatible with appropriate browser versions?
		2 Do images display correctly with browsers under test?
		3 Verify the fonts are usable on any of the browsers
		4 Is Java Code/Scripts usable by the browsers under test?
		5 Have you tested Animated GIFs across browsers?
CACHE	CONNECTION SPEED	Does the site load quickly enough in the viewer's browser within 8 Seconds?
USABILITY	PRINTERS	1 Are text and image alignment proper?
		2 Are colours of text, foreground and background is standard?
		3 Scalability to fit paper size
		4 Are tables and borders provided?
		5 Do pages print legibly without cutting off text?
	COLORS	1 Are hyperlink colors standard?
		2 Are the field backgrounds the correct color?
		3 Are the field prompts the correct color?
		4 Are the screen and field colors adjusted correctly for non-editable mode?
		5 Does the site use (approximately) standard link colors?
		6 Are all the buttons are in standard format and size?
		7 Is the general screen background the correct color?
		8 Is the page background (color) distraction free?
	CONTENT	1 All fonts to be the same
		2 Are all the screen prompts specified in the correct screen font?
		3 Does content remain if you need to go back to a previous page, or if you move forward to another new page?
		4 Is all text properly aligned?
		5 Is the text in all fields specified in the correct screen font?
		6 Is all the heading are left aligned
		7 Does the first letter of the second word appears in lowercase?
	IMAGES	1 Are all graphics properly aligned?
		2 Are graphics being used the most efficient use of file size?
		3 Are graphics optimized for quick downloads?
		4 Assure that command buttons are all of similar size and shape, and same font & font size?
		5 Banner style & size & display exact same as existing windows
		6 Does text wrap properly around pictures/graphics?
		7 Is it visually consistent even without graphics?
	INSTRUCTIONS	1 Is all the error message text spelt correctly on this screen?
		2 Is all the micro-help text (i.e tool tip) spelt correctly on this screen?
		3 Is microhelp text(i.e tool tip) for every enabled field & button?
		4 Is progress messages on load of tabbed(active screens) screens
	NAVIGATION	1 Are all disabled fields avoided in the TAB sequence?
		2 Are all read-only fields avoided in the TAB sequence?
		3 Can all screens accessible via buttons on this screen be accessed correctly?
		4 Does a scrollbar appear if required?
		5 Does the Tab Order specified on the screen go in sequence from Top Left to Bottom Right? This is the default unless otherwise specified.
		6 Is there a link to home on every single page?
		7 On open of tab focus will be on first editable field
		8 When an error message occurs does the focus return to the field in error when the user cancels it?
FUNCTIONAL	LINKS	1 Check that the link takes you to the page it said it would.
		2 Ensure to have no orphan pages (a page that has no links to it)
		3 Check all of your links to other websites
		4 Are all referenced web sites or email addresses hyperlinked?
		5 If we have removed some of the pages from our own site, set up a custom 404 page that redirects your visitors to your home page (or a search page) when the user try to access a page that no longer exists.
		6 Check all mailto links and whether it reaches properly
	FORMS	1 Acceptance of invalid input
		2 Optional versus mandatory fields
		3 Input longer than field allows
		4 Radio buttons
		5 Default values on page load/reload (Also terms and conditions should be disabled)
		6 Is Command Button can be used for HyperLinks and Continue Links ?
		7 Is all the datas inside combo/list box are arranged in chronological order?
		8 Are all of the parts of a table or form present? Correctly laid out? Can you confirm that selected texts are in the "right place?
		9 Does a scrollbar appear if required?
	DATA VERIFICATION AND VALIDATION	1 Is the Privacy Policy clearly defined and available for user access?
		2 At no point of time the system should behave awkwardly when an invalid data is fed
		3 Check to see what happens if a user deletes cookies while in site
		4 Check to see what happens if a user deletes cookies after visiting a site
SPECIFIC FUNCTIONAL	DATA INTEGRATION	1 Check the maximum field lengths to ensure that there are no truncated characters?
		2 If numeric fields accept negative values can these be stored correctly on the database and does it make sense for the field to accept negative numbers?
		3 If a particular set of data is saved to the database check that each value gets saved fully to the database. (i.e.) Beware of truncation (of strings) and rounding of numeric values.
	DATE FIELD CHECKS	1 Assure that leap years are validated correctly & do not cause errors/miscalculations.
		2 Assure that Feb. 28, 29, 30 are validated correctly & do not cause errors/ miscalculations.
		3 Is copyright for all the sites includes Yahoo co-branded sites are updated
	NUMERIC FIELDS	1 Assure that lowest and highest values are handled correctly.
		2 Assure that numeric fields with a blank in position 1 are processed or reported as an error.
		3 Assure that fields with a blank in the last position are processed or reported as an error an error.
		4 Assure that both + and - values are correctly processed.
		5 Assure that division by zero does not occur.
		6 Include value zero in all calculations.
		7 Assure that upper and lower values in ranges are handled correctly. (Using BVA)
	ALPHANUMERIC FIELD CHECKS	1 Use blank and non-blank data.
		2 Include lowest and highest values.
		3 Include invalid characters & symbols.
		4 Include valid characters.
		5 Include data items with first position blank.
		6 Include data items with last position blank.
INTERFACE AND ERROR HANDLING	SERVER INTERFACE	1 Verify that communication is done correctly, web server-application server, application server-database server and vice versa.
		2 Compatibility of server software, hardware, network connections
	EXTERNAL INTERFACE	1 Have all supported browsers been tested?
		2 Have all error conditions related to external interfaces been tested when external application is unavailable or server inaccessible?
	INTERNAL INTERFACE	1 If the site uses plug-ins, can the site still be used without them?
		2 Can all linked documents be supported/opened on all platforms (i.e. can Microsoft Word be opened on Solaris)?
		3 Are failures handled if there are errors in download?
		4 Can users use copy/paste functionality?Does it allows in password/CVV/credit card no field?
		5 Are you able to submit unencrypted form data?
		6 If the system does crash, are the re-start and recovery mechanisms efficient and reliable?
		7 If we leave the site in the middle of a task does it cancel?
		8 If we lose our Internet connection does the transaction cancel?
		9 Does our solution handle browser crashes?
		10 Does our solution handle network failures between Web site and application servers?
		11 Have you implemented intelligent error handling (from disabling cookies, etc.)?
	SEARCH FOR DEAD LINKS	Check each and every link whether it is navigating to a proper page or not.
	TESTING FORMS AND SCRIPTS	Testing the scripts and forms with various forms of data and checking for the validation of the data.
CONTENT PROOFING	SPELLING AND GRAMMER	Assure that there are no spelling mistakes and as well as grammatical mistakes related to the general content the site contains.
	MESSAGES	Assure that there are no spelling mistakes and as well as grammatical mistakes related to the messages displayed to the user.
SYSTEM AND BROWSER COMPATIBILITY	DIFFERENT BROWSERS	The site should be tested under different browsers like IE 7.0, 8.0, 9.0 and Safari 4.0 and 5.0 and Chrome 12,13.0 and firefox 12,13.0
	DIFFERENT OS	The site should be tested under different Operating systems like Windows 98, XP,2000, NT, 7, Unix, Linux.
DELIVERY TESTING	DOWNLOAD OR RESPONSE TIME	The site should be tested under different loads measure the download or response time.
	FILE SIZE	The site should be tested for the maximum file size that it can upload.
USER ACCEPTANCE	PUBLIC REACTION OF WEBSITE	The site should be tested with a person who has no knowledge of the information of the site, or he should be similar to a lay man so as to know the reaction of the user on the site.
SCRIPTING	HTML MULTI PLATFORM CAPABILITY	There are various versions of HTML, which are all similar but with slight differences. Check for the valid HTML to ensure multi flatform capability.
DATABASE	DATABASE ACCESS	Check whether a query for the data is properly handled and correct data is displayed to the user.