Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
dev:guidelinesandchecklistfortesting [2010/04/19 23:01] david_pate Added images of form elements |
dev:guidelinesandchecklistfortesting [2010/04/19 23:04] david_pate Minor edits done to formatting. |
||
|---|---|---|---|
| Line 126: | 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 | + | |
| ====Load==== | ====Load==== | ||
| Line 133: | Line 133: | ||
| Check/ | Check/ | ||
| - | - 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. | + | |
| - | - 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. | + | |
| - | 6.3 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. | + | |
| - | 6.5 Verify encryption is done correctly if SSL is used (If applicable) | + | |
| - | 6.6 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 180: | 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 265: | 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:** |
| \\ | \\ | ||
