CGI Testing

hgTracks, hgTrackUi, hgc

1. The TrackCheck robot checks this pretty thoroughly
2. manually check anything that has been an issue during the past 2-week release cycle
3. to check hgTrackUis, start from the "Track/Assebmly Overview" from the QA portal here (don't forget to click on the number of the machine that you are testing)
4. click on random tracks to check them

hgGene

1. Heather has a robot to check this CGI
2. test one known gene - click off-site, check entire page
3. test all possible paths among KG, PB, GS, VG (not that you wind up in mouse VG and need to use "Other Species" to get back to human.)

hgNear

1. use the test protocol for Gene Sorter from the QA portal

hgCustom

1. Test all three methods of entering a CT: typed in, uploaded by file, URL.
2. Test editing, deleting, adding, updating, HTML docs, etc.
3. Test adding mutiple tracks at once (multiple tracks in one file, multiple URLs, and pasting in mutiple tracks)
4. Test CTs in relation to the Table Browser.

• See also examples page here: http://genomewiki.ucsc.edu/index.php/Custom_Track_Examples

hgVisiGene

1. test the search box by entering a gene name
2. check the zoom buttons
3. check that the "Gene" link opens the correct gene details page, and that that "visiGene" link in that gene details page retrieves the correct images in visiGene
4. pick an image and check all of the links for that page
5. for images composed of several smaller images, check that the pane descriptions are displaying correctly
6. (Note: the images from Mahoney are a subset of the MGI/Jax images. The Mahoney images should list two sources and should show two sets of acknowledgements.)

hgTables

1. check all drop-downs
2. press on summary/stats button
3. do an intersection with a couple of different output formats
4. make sure filtering is functioning
5. create a custom track in the browser
6. check all output formats
7. try sending output to Galaxy and GREAT; make sure checkboxes stay checked when applying filters, etc.
8. do a subtrack merge (select a table from a composite track to get the option)
9. do a correlation
10. try defining regions

hgPal

1. check a "Protein FASTA" click-through from a UCSC Gene details page
2. check a "CDS FASTA" click-through from a RefSeq Genes details page
3. using the Table Browser, choose "CDS FASTA" as the output format (this should work for any genePred track)
4. check that different settings give expected results

hgBlat

1. perform both a nucleotide and a protein search with default settings
2. make sure colors listed in description section are right
3. zoom in on an alignment and test "View details of parts of alignment within browser window"
4. try different sorts and output types
5. make sure all the buttons work, including uploading a file

hgPcr

1. test some perfectly matching primers
2. vary settings and input primers and see if results make sense
3. for human and mouse browsers, test the "UCSC Genes" target

hgLiftOver, hgConvert

1. Test cases available in the database on hgwdev: qa.liftOverTestCases

pbGateway, pbGlobal, pbTracks

1. general testing; click around
2. enter a protein symbol
3. review results page
4. click into pbGlobal and check display

hgSession

1. check that a new session can be saved
2. check that old sessions are still there
3. delete a session
4. check browser & email button; click the title of session & make sure you can save changes to the description
5. try loading a session via a file and via a URL
6. logout and try to load a session that can be shared and one that can't be shared

hgGenome

Good genome graph data for testing: http://hgwdev.cse.ucsc.edu/~rhead/genomeGraphsWithColumns

1. upload a dataset from a file
2. upload a data set from a URL
3. import data from a track
4. check that you can change the configurations
5. check that the "browser regions" & "sort genes" work

cartDump, cartReset

1. check cart
2. reset cart
3. check cart again

See also: cart test protocol

hgApi

This CGI is responsible for the metadata "..." links on the hgTrackUi page and the "metadata" links on the hgc details pages of composite tracks with metadata.

1. click on a "..." link and check that it opens up - no need to check the content. You only need to test one "..." link - if hgApi is broken, it will break all "..." links.
2. This CGI can also be tested by clicking on a "meatadata" link in hgc details and check that it opens up - no need to check the content.

Probably doing 1 or 2 is sufficient, but it is a good habit to have the testers of hgTrackUi and hgc check 1 and 2 respectively, that way we are double covered in case one person forgets.