You are here: start » dev » guidelinesandchecklistfortesting

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
dev:guidelinesandchecklistfortesting [2010/04/18 17:10]
david_pate 		dev:guidelinesandchecklistfortesting [2010/04/19 23:04]
david_pate Minor edits done to formatting.
Line 1: Line 1:
-=====Guidelines and Checklist=====+=====Guidelines and Checklist Documentation===== 
 +The original Guidelines and Checklist documentation can be found here: {{dev:guidelines_and_checklist.doc|}}
  
 =====Functionality===== =====Functionality=====
Line 125: Line 126:
 ====Connection speed==== ====Connection speed====
  
-- Try with Connection speed: 14.4, 28.8, 33.6, 56.6, ISDN, cable, DSL, T1, T3 +  * Try with Connection speed: 14.4, 28.8, 33.6, 56.6, ISDN, cable, DSL, T1, T3 
-- Time-out+  * Time*out
  
 ====Load==== ====Load====
Line 132: Line 133:
 Check/Measure the following: Check/Measure the following:
  
-- What is the estimated number of users per time period and how will it be divided over the period?  +  * 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 will the system react?  +  * Will there be peak loads and how will the system react?  
-- Can your site handle a large amount of users requesting a certain page?  +  * Can your site handle a large amount of users requesting a certain page?  
-- Large amount of data from users.+  * Large amount of data from users.
  
 ====Stress==== ====Stress====
  
-Stress testing is done in order to actually break a site or a certain feature 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. Hackers often stress systems by providing loads of wrong in-data until it crash and then gain access to it during start-up. +Stress testing is done in order to actually break a site or a certain feature 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. Hackers often stress systems by providing loads of wrong in*data until it crash and then gain access to it during start*up. 
  
-- Typical areas to test are forms, logins or other information transaction components.  +  * Typical areas to test are forms, logins or other information transaction components.  
-- Performance of memory, CPU, file handling etc. +  * Performance of memory, CPU, file handling etc. 
-- Error in software, hardware, memory errors (leakage, overwrite or pointers)+  * Error in software, hardware, memory errors (leakage, overwrite or pointers)
  
 ====Continuous Use==== ====Continuous Use====
  
-- Is the application or certain features going to be used only during certain periods of time or will it be used continuously 24 hours a day 7 days a week?  +  * Is the application or certain features going to be used only during certain periods of time or will it be used continuously 24 hours a day 7 days a week?  
-- Will downtime be allowed or is that out of the question?  +  * Will downtime be allowed or is that out of the question?  
-- Verify that the application is able to meet the requirements and does not run out of memory or disk space.+  * Verify that the application is able to meet the requirements and does not run out of memory or disk space.
  
 =====Security===== =====Security=====
  
-6.1 Valid and Invalid Login +  * Valid and Invalid Login 
-6.2 Limit defined for the number of tries. +  * Limit defined for the number of tries. 
-6.3 Can it be bypassed by typing URL to a page inside directly in the browser? +  * Can it be bypassed by typing URL to a page inside directly in the browser? 
-6.4 Verify Log files are maintained to store the information for traceability. +  * Verify Log files are maintained to store the information for traceability. 
-6.5 Verify encryption is done correctly if SSL is used (If applicable) +  * Verify encryption is done correctly if SSL is used (If applicable) 
-6.6 No access to edit scripts on the server without authorization.+  * No access to edit scripts on the server without authorization.
  
 =====Before Hosting a Website===== =====Before Hosting a Website=====
-Checklist before hosting a website:+**Checklist before hosting a website:**
  
 ====Functionality==== ====Functionality====
Line 179: Line 180:
   * Optional should allow the user to skip the field.    * Optional should allow the user to skip the field.
  
-**Cookies**  +**Cookies** \\  
-Check whether cookies are enabled. **Depends on project** +Check whether cookies are enabled. \\ **Depends on project**
  
 **Web Indexing** **Web Indexing**
Line 264: Line 265:
  
 =====Golden Rules of Interface Design===== =====Golden Rules of Interface Design=====
-You Should Use the Eight Golden Rules of Interface Design:+**You Should Use the Eight Golden Rules of Interface Design:**
  
 \\  \\ 
Line 323: Line 324:
   * The third principle is to prevent errors whenever possible. Steps can be taken to design so that errors are less likely to occur, using methods such as organizing screens and menus functionally, designing screens to be distinctive and making it difficult for users to commit irreversible actions. Expect users to make errors, try to anticipate where they will go wrong and design with those actions in mind.   * The third principle is to prevent errors whenever possible. Steps can be taken to design so that errors are less likely to occur, using methods such as organizing screens and menus functionally, designing screens to be distinctive and making it difficult for users to commit irreversible actions. Expect users to make errors, try to anticipate where they will go wrong and design with those actions in mind.
  
- 
- 
-Section 2 - Tester's Screen Validation Checklist 
-2.1. Aesthetic Conditions 
-2.2. Validation Conditions 
-2.3. Navigation Conditions 
-2.4. Usability Conditions 
-2.5. Data Integrity Conditions 
-2.6. Modes (Editable Read-only) Conditions 
-2.7. General Conditions 
-2.8. Specific Field Tests 
-2.8.1. Date Field Checks 
-2.8.2. Numeric Fields 
-2.8.3. Alpha Field Checks 
- 
-Section 3 - Other 
-3.1. On every Screen 
-3.2. Shortcut keys / Hot Keys 
-3.3. Control Shortcut Keys 
- 
-Section 1 - Windows Compliance Testing 
-1.1. Application 
-1.2. For Each Window in the Application 
-1.3. Text Boxes 
-1.4. Option (Radio Buttons) 
-1.5. Check Boxes 
-1.6. Command Buttons 
-1.7. Drop Down List Boxes 
-1.8. Combo Boxes 
-1.9. List Boxes 
 =====Windows Compliance Testing===== =====Windows Compliance Testing=====
 ====Application==== ====Application====
Line 416: Line 387:
 ====Application Objects==== ====Application Objects====
 **Text Boxes** \\  **Text Boxes** \\ 
 +
 +{{http://upload.wikimedia.org/wikipedia/commons/thumb/2/21/Textbox2.gif/220px-Textbox2.gif}}
 +Original image and more information at: [[http://en.wikipedia.org/wiki/Text_box]]
  
 Move the Mouse Cursor over all Enterable 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-updateable. Refer to previous page. Move the Mouse Cursor over all Enterable 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-updateable. Refer to previous page.
Line 429: Line 403:
 \\  \\ 
 **Option (Radio Buttons)** \\  **Option (Radio Buttons)** \\ 
 +
 +{{http://upload.wikimedia.org/wikipedia/commons/c/cb/Radio_button.png}}
 +Original image and more information at: [[http://en.wikipedia.org/wiki/Radio_button]]
  
 Left and Right arrows should move 'ON' Selection. So should Up and Down.. Select with mouse by clicking. Left and Right arrows should move 'ON' Selection. So should Up and Down.. Select with mouse by clicking.
Line 434: Line 411:
 \\  \\ 
 **Check Boxes** \\  **Check Boxes** \\ 
 +
 +{{http://upload.wikimedia.org/wikipedia/commons/7/72/Checkbox.png}}
 +Original image and more information at: [[http://en.wikipedia.org/wiki/Check_box]]
  
 Clicking with the mouse on the box, or on the text should SET/UNSET the box. SPACE should do the same Clicking with the mouse on the box, or on the text should SET/UNSET the box. SPACE should do the same
Line 439: Line 419:
 \\  \\ 
 **Command Buttons** \\  **Command Buttons** \\ 
 +
 +{{http://upload.wikimedia.org/wikipedia/commons/thumb/c/c4/Gimp-buttons.png/220px-Gimp-buttons.png}}
 +Original image and more information at: [[http://en.wikipedia.org/wiki/Button_(computing)]]
  
 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. 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.
Line 457: Line 440:
 \\  \\ 
 **Drop Down List Boxes** \\  **Drop Down List Boxes** \\ 
 +
 +{{http://upload.wikimedia.org/wikipedia/commons/d/d1/Drop-down_list_example.PNG}}
 +Original image and more information at: [[http://en.wikipedia.org/wiki/Drop-down_list]]
  
 Pressing the Arrow should give list of options. This List may be scrollable. You should not be able to type text in the box. Pressing the Arrow should give list of options. This List may be scrollable. You should not be able to type text in the box.
Line 470: Line 456:
 \\  \\ 
 **Combo Boxes**\\  **Combo Boxes**\\ 
 +
 +{{http://upload.wikimedia.org/wikipedia/commons/5/5d/Combo_box_example.PNG}}
 +Original image and more information at: [[http://en.wikipedia.org/wiki/Combo_box]]
  
 Should allow text to be entered. Clicking Arrow should allow user to choose from list Should allow text to be entered. Clicking Arrow should allow user to choose from list
Line 475: Line 464:
 \\  \\ 
 **List Boxes** \\  **List Boxes** \\ 
 +
 +{{http://upload.wikimedia.org/wikipedia/commons/d/da/List_example.PNG}}
 +Original image and more information at: [[http://en.wikipedia.org/wiki/List_box]]
  
 Should allow a single selection to be chosen, by clicking with the mouse, or using the Up and Down Arrow keys. Should allow a single selection to be chosen, by clicking with the mouse, or using the Up and Down Arrow keys.
Line 681: Line 673:
   - Shortcut keys - Alt + F   - Shortcut keys - Alt + F
 ====Shortcut Keys / Hot Keys==== ====Shortcut Keys / Hot Keys====
-  * __**Shortcut keys go here**__+^ Key ^ No Modifier ^ SHIFT ^ CTRL ^ ALT ^ 
 +| F1 | Help | Enter Help Mode | N/A | N/A | 
 +| F2 | N/A | N/A | N/A | N/A | 
 +| F3 | N/A | N/A | N/A | N/A | 
 +| F4 | N/A | N/A | Close Document Window | Close Application Window | 
 +| F5 | N/A | N/A | N/A | N/A | 
 +| F6* | Move clockwise to next pane of active window | Move counterclockwise to next pane of active window | Move to next document window; top window moves to bottom of stack (adding SHIFT reverses action : previous window moves to top.) | Move to application's next open non-document window (Adding SHIFT reverses order of movement) | 
 +| F7 | N/A | N/A | N/A | N/A | 
 +| F8 | Toogle extend mode, if supported | Toggle add mode, if supported | N/A | N/A | 
 +| F9 | N/A | N/A | N/A | N/A | 
 +| F10 | Toggle menu bar activation | N/A | N/A | N/A | 
 +| F11 | N/A | N/A | N/A | N/A | 
 +| F12 | N/A | N/A | N/A | N/A |
 \\  \\ 
 **Control Shortcut Keys** \\  **Control Shortcut Keys** \\ 
 __Recommended CTRL+Letter Shortcuts__ \\  __Recommended CTRL+Letter Shortcuts__ \\ 
-  * __**Shortcut keys go here**__+^ Key ^ Function ^ 
 +| CTRL + Z | Undo | 
 +| CTRL + X | Cut | 
 +| CTRL + C | Copy | 
 +| CTRL + V | Paste |
 \\  \\ 
 __Suggested CTRL+Letter Shortcuts__ \\  __Suggested CTRL+Letter Shortcuts__ \\ 
-  * __**Shortcut keys go here**__+^ Key ^ Function ^ 
 +| CTRL + N | New | 
 +| CTRL + O | Open | 
 +| CTRL + P | Print | 
 +| CTRL + S | Save | 
 +| CTRL + B | Bold* | 
 +| CTRL + I | Italic* | 
 +| CTRL + U | Underline* |
   * **These shortcuts are suggested for text formatting applications, in the context for   * **These shortcuts are suggested for text formatting applications, in the context for
 which they make sense. Applications may use other modifiers for these operations.** which they make sense. Applications may use other modifiers for these operations.**
  
-=====Guidelines and Checklist Documentation===== 
-The original Guidelines and Checklist documentation can be found here: {{dev:guidelines_and_checklist.doc|}} 

Trace:

QR Code
QR Code dev:guidelinesandchecklistfortesting (generated for current page)