Web Application Testing Checklist
application serverdatabase server and vice versa.1 Have all supported browsers been tested? 3.2 VIDEO SETTINGS 4.3.6 Have you implemented intelligent error handling (from disabling cookies. network connections 3.3.)? 4.1.1 BROWSERS 4.5 Are you able to submit unencrypted form data? 3.1.3 CONNECTION SPEED 4.2 Compatibility of server software.4.2 Do images display correctly with browsers under test? 4.4 Can users use copy/paste functionality? Does it allows in password/CVV/credit card no field? 3. 2.3 Are failures handled if there are errors in download? 3. COMPATIBILITY 4.4 INTERNAL INTERFACE 3.6 Include data items with last position blank.2 If we leave the site in the middle of a task does it cancel? 3.2 Have all error conditions related to external interfaces been tested when external application is unavailable or server inaccessible? 3.
3. INTERFACE AND ERROR HANDLING 3. 600x800.4.2. can Microsoft Word be opened on Solaris)? 3.4 Is Java Code/Scripts usable by the browsers under test? 4.1 If the system does crash.2 Colour depth (2126.96.36.199.4. web server-application server.3.4 PRINTERS
. 2.1.1 If the site uses plug-ins.4. 188.8.131.52 EXTERNAL INTERFACE 3.1.1 Does the site load quickly enough in the viewer's browser within 8 Seconds? 4. font are readable etc. 32-bit) 4.3 Include invalid characters & symbols.1 Use blank and non-blank data.3 Verify the fonts are usable on any of the browsers 4.5 Have you tested Animated GIFs across browsers? 4. are the re-start and recovery mechanisms efficient and reliable? 3.4.3 INTERNAL INTERFACE 3.1.) like 1024 by 768.4.3. can the site still be used without them? 3.4.1 Is the HTML version being used compatible with appropriate browser versions? 4.5 Does our solution handle network failures between Web site and application servers? 3.1. 640 x 480 pixels etc 4.1 Screen resolution (check that text and graphic alignment still work. 16-bit. 2.5 Include data items with first position blank. 2.4 Include valid characters. etc.4 Does our solution handle browser crashes? 3.3.3 If we lose our Internet connection does the transaction cancel? 3.2 Include lowest and highest values.2 Can all linked documents be supported/opened on all platforms (i.1.e.3. 2.1 SERVER INTERFACE 184.108.40.206 Verify that communication is done correctly.4. hardware.4.
3.2.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.5.4. and same font & font size.1.8 When an error message occurs does the focus return to the field in error when the user cancels it?
.2 Are all the screen prompts specified in the correct screen font? 220.127.116.11 Colours of text.2 Are graphics being used the most efficient use of file size? 18.104.22.168.3.1.1 Is all the error message text spelt correctly on this screen? 1.4 INSTRUCTIONS 1.e tool tip) spelt correctly on this screen? 1.4 Progress messages on load of tabbed(active screens) screens 1.7 On open of tab focus will be on first editable field 1.5.8 Is the page background (color) distraction free? 1.4 Are the screen and field colors adjusted correctly for non-editable mode? 1.5. 22.214.171.124.1 Are all disabled fields avoided in the TAB sequence? 1.6 Are all the buttons are in standard format and size? 1.5 NAVIGATION 126.96.36.199 Are graphics optimized for quick downloads? 1.3.e tool tip) for every enabled field & button 1.3 Can all screens accessible via buttons on this screen be accessed correctly? 1. USER INTERFACE 1.5 Is the text in all fields specified in the correct screen font? 188.8.131.52.4.3.5 Banner style & size & display exact same as existing windows 1.2.1 Text and image alignment 4.2 Are all read-only fields avoided in the TAB sequence? 1. 1.4 Tables and borders 4.2.2 Are the field backgrounds the correct color? 1.3 Does content remain if you need to go back to a previous page.7 Does the first letter of the second word appears in lowercase? Eg: 1.5.2 CONTENT 1.4 Does a scrollbar appear if required? 184.108.40.206 Is it visually consistent even without graphics? 1.1. foreground and background 4.1.7 Is the general screen background the correct color? 1.6 Is all the heading are left aligned 1.3 Are the field prompts the correct color? 1.4 Assure that command buttons are all of similar size and shape.6 Does text wrap properly around pictures/graphics? 1.5 Does the site use (approximately) standard link colors? 1.5 Do pages print legibly without cutting off text?
User Interface Testing Checklist
220.127.116.11.4.4.4 Is all text properly aligned? 1.1 All fonts to be the same 1.1 Are hyperlink colors standard? 1.2 Is all the micro-help text(i.3 IMAGES 1.3 Microhelp text(i.3 Scalability to fit paper size 4.1 Are all graphics properly aligned? 1.6 Is there a link to home on every single page? 1.1. or if you move forward to another new page? 1.3.1 COLORS 1.5.
This checklist can give some guidance to the development and QE. 600x800 etc. If screen has control menu.1 Are all the field prompts spelt correctly? 1.6. On every application. TAB should move focus in forward direction and SHIFT+TAB in backward direction. it should come by pressing F1 button.
Window caption for every application should have application name and window name. b. Windows Compliance Standards
These compliance standards are followed by almost all the windows based application. f. This GUI test checklist can ensure that all the GUI components are thoroughly tested.6. c.1. error messages.
Compliance for each application a. g. Main window of application should have same caption as the icon in the program manager.6 Do pages print legibly without cutting off text? 1. c. h. d.4 Assure that option boxes. accurate? 1.5 Can the typical user run the system without frustration? 1. d. use the entire control menu like move. icon etc.
. Try to start application while it is loading g. if application is busy it should show hour glass or some other mechanism to notify user that it is processing.9 Does User cab Login Member Area with both UserName/Email ID ? 1.6.6. These compliances can be categorized according to following criteria
i. e. Normally F1 button is used for help. e. If tab navigation is present.6. both the teams. option buttons.3 Are names in command button & option box names are not abbreviations.6. Tab order should be left to right and top to bottom within a group box. Closing of the application should result in “Are you sure?” message. i. Text present should be checked for spelling and grammar. responsive.7 Does the site convey a clear sense of its intended audience? 1. Development team can make sure that during the development they follow guidelines related to the compliance. 1. If focus is present on any control.11 Is all terminology understandable for all of the site’s intended users?
GUI Testing Checklist
Purpose of this GUI Testing Checklist is to help you understand how your application can be tested according to the known and understood standards for GUI. close.? 1. This compliance must be followed for every application. aesthetics.6. resize etc.10 Does the system provide or facilitate customer service? i. it should be presented by dotting lines around it. Title of the window and information should make sense to the user. Application should be started by double clicking on the icon.6. If your product has help integrated.8 Does the site have a consistent. Any variance from these standards can result into inconvenience to the user.6 USABILITY 1.9 Does the site look good on 640 x 480. we will cover Windows compliance standard and some test ideas for field
specific tests. f.
a. In the first part of this checklist.6. version number. Behaviour for starting application more than once must be specified. helpful.6.6.6. navigation etc. Specially. clearly recognizable "look-&-feel"? 1.2 Are fonts too large or too small to read? 1.e. Minimize and restoring functionality should work properly Compliance for each window in the application
ii. but onus of testing GUI is on the QE team and as a tester it is your responsibility to validate your product against GUI standards followed by your organization.
b. Loading message should have information about application name. and command buttons are logically grouped together in clearly demarcated areas "Group Box" 1.
Also test width of the text field by entering all capital W. Check boxes a. User should be able to select text using Shift + arrow keys. Test plan is usually created by Test Manager. c. Clicking mouse on the box should set/unset the checkbox. Text should be left justified In general. All buttons except OK/Cancel should have a letter access to them. j. List can be scrollable but user should not be able to type in.
vii. c. Similar to the list mentioned above. execution. all the operations should have corresponding key board shortcut key for this. special characters and make sure that there is no abnormality. pressing Esc should activate it.
vi. Selected item should be displayed on the list. If there is any Cancel button on the screen. Similarly. schedule. This is indicated by a letter underlined in the button text. Make sure that all the data can be seen using scroll bar. Test overflowing textbox by inserting as many characters as you can in the text field.h.
Text boxes a. b. ix. Spacebar should also do the same Push Buttons a. either by mouse or arrow keys.
iv. double clicking on icon should be mapped to these behaviour.
viii. b. Clicking each button with mouse should activate it and trigger required action. Selection should be possible using mouse and double click should select entire text in the text box. after giving focus SPACE or RETURN button should also do the same. User should be able to select any combination of checkboxes b. b.
v. c. Test plan may contain information related to scope. Should allow single select. Radio Buttons a. Drop down list boxes a. Items should be in alphabetical order in any list.
User should not be able to select greyed or disabled control. Enter invalid characters. Pressing Ctrl-F4 should open the list box. Try this using tab as well as mouse. Test Lead or senior
. List Boxes a. Pressing any letter should take you to the first element starting with that letter c. but user should be able to enter text in it. f. There should be only one blank space in the dropdown list. If there are view/open button. d. c.
iii. d. Only one should be selected from the given option. i. Arrow key should set/unset the radio buttons. k. resources. environment. Combo Box a. Pressing the arrow should give list of options available to the user. completion criteria etc. b. The button should be activated by pressing ALT b. Pressing a letter should bring the first item in the list starting with the same letter. reporting. All tab buttons should have distinct letter for it. e. User should be able to select any button using mouse or key board c. Move mouse to textbox and it should be changed to insert bar for editable text field and should remain unchanged for non-editable text field. d. risk.
Test plan is probably one of the most significant document for software testing projects. d. automation.
You should have information on what features will be tested and what will not be tested. test case management tool. Testing Tools and Automation: You should have information about what tools you are using to manage your testing activities. Any changes in the documents you are referring should be reflected in your plan. Risk will be different from one project to another and so your Test strategy. along with the other stake holders define what are the potential risk in the project? What will be the impact if these risks are materialized? What is the mitigation plan for these risks and how your testing activities are making sure that these risks are managed properly. Information about these activities can be gathered from various stakeholders by asking questions that are required for your Test Plan. In your testing strategy. every Test Plan contain information about following activities. This should have information on the various matrixes and how they should be interpreted. For example instead of saying product should be stable. Risk associated with a desktop tax calculation software will be different from payment gateway or life support system. every one will have clear understanding about what is tested and what is not. defect tracking system.testers in the team. From this data you can make out which platform will be tested more. You should also have information on what areas your team is owning? Are you taking care of all the types of testing that is required for the product including Performance. You should have information on the configuration management for test artifacts. Criteria Definition: Criteria for Entry and Exit should be clearly defined for every activity of your testing project. Security. scope of the test activities should be known. test automation should be treated as separate project and you should have brief information here along with the link to automation plan. Defining scope for your testing project is very important for the management as well. Release Criteria: This should clearly state release criteria for the product. 15 percent are on Linux and 5 percent are on Mac. you can say No P1 defect should be reported for at-least two weeks. stopping. No regression defect sho
. Test Environment: You should have information on what will be the environment for the testing. testing project follows development activities. globalization etc. Information captured from stake holder is reflected in the Test Plan. What kind of reports you are planning to generate from the data that you gather from test activities. Before start preparing Test Plan. You should have well defined entry/exit criteria for starting. Execution and Reporting: In this section you should have information on how execution will be managed for the various testing activities. So for estimation and scheduling you should have information on the development plan and milestone. you can schedule your testing activities accordingly. This information is captured from stake holders by asking them. tools for automation etc. you need to make sure that all the potential risks are captured and managed by your testing activities. You should also have criteria defined for specifying when testing is complete. Estimation. Typically. Scheduling and Resource Management: Mostly. What type of environment will be supported by product? What is the priority for these environment? For example. Resources in testing projects include hardware. Criteria defined here should be clear and measurable. Once you have information on the development plan. If product is supported on all the platform and data for user distribution says that 80 percent are on Windows. Information captured here will be useful for planning hardware and software requirement for your Test Lab. You should. Ideally. information should be captured from various stakeholders of the project. If scope is properly defined. software and people management. Reference: You should clearly define documents you are referring to prepare test plan. Risk Management: Test strategy is derived from the risk analysis. suspending and resuming test activities. Scope Management: Before starting Test Planning activity.