Web Presence Working Group: Testing Guide: Difference between revisions
No edit summary |
No edit summary |
||
Line 35: | Line 35: | ||
Make sure that the link to the new software page appears in the menu bar ("Other tools") and that the experimental features never show up on the page (i.e. AmiGO features that you haven't heard of yet). | Make sure that the link to the new software page appears in the menu bar ("Other tools") and that the experimental features never show up on the page (i.e. AmiGO features that you haven't heard of yet). | ||
=== GONuts integration === | === GONuts integration (Eurie) === | ||
Make sure that "Community" information appears on term details pages, that the link to GONuts is functional, and that the return links from GONuts work as well. | Make sure that "Community" information appears on term details pages, that the link to GONuts is functional, and that the return links from GONuts work as well. | ||
=== Homolset summary page === | === Homolset summary page (Pascale) === | ||
=== Homolset details page === | === Homolset details page (Jane) === | ||
=== Homolset dynamic graphs === | === Homolset dynamic graphs (Rama) === | ||
=== Homolset static graphs === | === Homolset static graphs (Val) === | ||
=== Homolset highlights === | === Homolset highlights (Rachel) === | ||
GP search and GP details | GP search and GP details | ||
=== Link to AmiGO Beta === | === Link to AmiGO Beta (Amelia) === | ||
link to wiki, link to beta, link back to stable | link to wiki, link to beta, link back to stable |
Revision as of 19:42, 2 February 2009
I pulled these assignments from the WPWG mailing list and chose people more or less based on how much I heard from them (hoping that would be an indicator of their availability).
If you have problems or want to change the assignments, please contact Seth or the WPWG.
New Things to Test
Testable new features
- 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
Installation scripts (Ben)
Basically, successfully install AmiGO on a machine and check to see if the installation scripts lie.
AmiGO software page (Siddartha)
Make sure that the link to the new software page appears in the menu bar ("Other tools") and that the experimental features never show up on the page (i.e. AmiGO features that you haven't heard of yet).
GONuts integration (Eurie)
Make sure that "Community" information appears on term details pages, that the link to GONuts is functional, and that the return links from GONuts work as well.
Homolset summary page (Pascale)
Homolset details page (Jane)
Homolset dynamic graphs (Rama)
Homolset static graphs (Val)
Homolset highlights (Rachel)
GP search and GP details
Link to AmiGO Beta (Amelia)
link to wiki, link to beta, link back to stable
OpenSearch widget
TBD
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.