Web Presence Working Group: Testing Guide
New Things to Test
Current Assignments
Discuss the testing assignments for AmiGO (clarifications)
- Installation scripts (install.pl, refresh.pl, version.pl)
- AmiGO software page
- GONuts integration
- Term page
- GONuts back to AmiGO
- Homolset
- Summary page
- Details pages
- Graphs
- Dynamic
- Static
- Highlights
- GP search
- GP details
- Beta links (if wanted)
- Beta button
- Beta layout
- OpenSearch widget
How to Test
GONuts integration
- Term page
- GONuts back to AmiGO
Installation scripts (install.pl, refresh.pl, version.pl)
- Homolset
- Summary page
- Details pages
- Graphs
- Dynamic
- Static
- Highlights
- GP search
- GP details
- Beta links (if wanted)
- Beta button
- Beta layout
- OpenSearch widget
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 and use inputs that you might not normally use
- 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.