Web Presence Working Group: Testing Guide: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 34: Line 34:
==== General Check (Everybody) ====
==== General Check (Everybody) ====


=== Visualize (???) ===
=== Visualize ===


==== Term Enrichment (???) ====
==== Term Enrichment (???) ====

Revision as of 13:53, 3 August 2009

New Things to Test

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, please contact Seth or the WPWG list. Feel free to trade assignments as long as the wiki is updated.

Testable new features

  • Installation script (simulate.pl)
  • AmiGO software page
  • IEAs (problem areas)
    • Term enrichment
    • Gene product count
    • Species
  • Visualize
    • Term enrichment
    • Browser
    • Homolset
    • Standalone client

How to Test

Installation script (Ben)

Basically, successfully install AmiGO on a machine and check to see if the installation script lies.

AmiGO software page (???)

Should contain proper links to all features not included in the menu bar.

IEAs

Term Enrichment (???)

General Check (Everybody)

Visualize

Term Enrichment (???)

Browser (???)

Homolset (???)

Standalone Client (???)

Things to Remember

Beyond checking functionality and correctness of the results, here are some other things to keep in mind while testing:

  • Please check for consistency in terminology (i.e. "ref genome" vs. "homolog" vs. "equivalog").
  • 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.

Sites to Test

AmiGO