Web Presence Working Group: Testing Guide: Difference between revisions
(New page: = Sites to Test = * http://toy.lbl.gov:9012/cgi-bin/amigo/go.cgi * http://toy.lbl.gov:9012/cgi-bin/amigo/search.cgi?action=advanced_query * http://toy.lbl.gov:9012/cgi-bin/amigo/browse.cg...) |
No edit summary |
||
| Line 1: | Line 1: | ||
= | = Things to Remember = | ||
Beyond checking functionality and correctness of the results, here are some other things to keep in mind while testing: | |||
* Travel paths that are less travelled | |||
* Do things quicker/more carelessly than usual | |||
* Opening multiple sessions or windows and juggling between them | |||
* Clicking multiple controls and backtracking | |||
* How do things work in other web browsers; is it accessible | |||
Another thing to try is [http://en.wikipedia.org/wiki/Fuzz_testing fuzz testing]. Basically trying random inputs in an effort to break the program. This would be random things in the URL and inputs. Usually this is automated, but we probably won't have something like that until more of the new AmiGO framework is written. | |||
Along a similar vein is actively trying to break the system given that some of the internal structure is known. This can include things like entering MySQL statements (the bottom layer of AmiGO) in order to try and trick AmiGO into executing an inappropriate statement. Errors found along these lines are very important for the developers to fix quickly. | |||
Finally, there is load testing; where you might try and overload the system. This probably won't be very useful or informative while running on the toy server. | |||
= Sites to Test = | |||
== AmiGO == | |||
* [http://toy.lbl.gov:9012/cgi-bin/amigo/go.cgi Main Page] | |||
* [http://toy.lbl.gov:9012/cgi-bin/amigo/search.cgi?action=advanced_query Advanced Search] | |||
* [http://toy.lbl.gov:9012/cgi-bin/amigo/browse.cgi Browse] | |||
* [http://toy.lbl.gov:9012/cgi-bin/amigo/blast.cgi BLAST] | |||
* [http://toy.lbl.gov:9012/cgi-bin/amigo/term_enrichment Term Enrichment] | |||
* [http://toy.lbl.gov:9012/cgi-bin/amigo/slimmer Slimmer] | |||
[[Category:Web Presence Working Group]] | |||
Revision as of 19:02, 28 November 2007
Things to Remember
Beyond checking functionality and correctness of the results, here are some other things to keep in mind while testing:
- Travel paths that are less travelled
- Do things quicker/more carelessly than usual
- Opening multiple sessions or windows and juggling between them
- Clicking multiple controls and backtracking
- How do things work in other web browsers; is it accessible
Another thing to try is fuzz testing. Basically trying random inputs in an effort to break the program. This would be random things in the URL and inputs. Usually this is automated, but we probably won't have something like that until more of the new AmiGO framework is written.
Along a similar vein is actively trying to break the system given that some of the internal structure is known. This can include things like entering MySQL statements (the bottom layer of AmiGO) in order to try and trick AmiGO into executing an inappropriate statement. Errors found along these lines are very important for the developers to fix quickly.
Finally, there is load testing; where you might try and overload the system. This probably won't be very useful or informative while running on the toy server.