|
|
| (19 intermediate revisions by 5 users not shown) |
| Line 1: |
Line 1: |
| Before testing your CGIs, check the [http://genecats.cse.ucsc.edu/builds/versions.html version notes] for recent changes particular to your CGIs. Pay extra attention to the changes when testing.
| | This page is no longer maintained. |
| | |
| ==hgTracks, hgc==
| |
| # The TrackCheck robot checks this pretty thoroughly
| |
| # manually check anything that has been an issue during the past 2-week release cycle
| |
| # hgTracks:
| |
| ## set position to 20bp & turn on all the tracks in hg18 to dense (using configure page); make sure all tracks load
| |
| ## check that drag/reorder of tracks works
| |
| # hgc: check the hgc details of one track per group on hg18, try a few links on the details page for a few, and try at least one composite to try composite specific things like metadata link.
| |
| | |
| ==hgTrackUi==
| |
| There are a couple of tracks to always check since they are very popular.
| |
| * ENCODE
| |
| ** test the correspondence between the matrix and the list of tracks when you turn on or off different tracks, including the graying out of boxes in the matrix
| |
| ** test different views for multiple tracks while testing correspondence between matrix and list of tracks
| |
| ** test one track that has 3 dimensional matrix
| |
| ** try sorting list of tracks by different columns
| |
| ** test links at the top of the page to downloads, subtracks and description
| |
| ** test that the buttons allowing users to go to parent tracks from child-tracks at the top of the page work
| |
| * Conservation (a "full" track like the one found on hg19)
| |
| ** test all aspects and buttons of the multiz track, including codon frames and the mini-wiggles visible when both the subtrack and parent track are on "full"
| |
| ** use this as an opportunity to test all aspects of a wiggle track
| |
| ** try filtering by score
| |
| * SNPs
| |
| ** test that adding different gene prediction tracks do change the details page for individual SNPs
| |
| ** test either the Minimum Average Heterozygosity or Maximum Weight filtering
| |
| ** test the filtering by attribute
| |
| ** test color specification, including changing the default color for a specification
| |
| * mRNAs
| |
| ** test filtering by one and more than one search term, as well as different filtering options
| |
| ** test that the coloring by codons/alignment function as expected
| |
| | |
| Finally, test a few random tracks from a few different assemblies (good candidates with non-standard trackUis include Chain/Nets, TransMap, Human Proteins, Restriction Enzymes). A fun one to test is HapMap LD Phased on hg18 since it has a radically different hgTrackUi.
| |
| | |
| Also test the "configure" button for one assembly.
| |
| | |
| ==hgGene==
| |
| # Heather has a robot to check this CGI
| |
| # test one known gene - click off-site, check entire page
| |
| # 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==
| |
| # use the test protocol for Gene Sorter from the QA portal
| |
| | |
| ==hgCustom==
| |
| # Test all three methods of entering a CT: typed in, uploaded by file, URL.
| |
| # Test editing, deleting, adding, updating, HTML docs, etc.
| |
| # Test adding mutiple tracks at once (multiple tracks in one file, multiple URLs, and pasting in mutiple tracks)
| |
| # Test CTs in relation to the Table Browser.
| |
| *See also examples page here: [[Custom_Track_Examples|Custom Track Examples]]
| |
| | |
| ==hgVisiGene==
| |
| # test the search box by entering a gene name
| |
| # check the zoom buttons
| |
| # 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
| |
| # pick an image and check all of the links for that page
| |
| # for images composed of several smaller images, check that the pane descriptions are displaying correctly (not all panes will have an associated pane description)
| |
| # (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==
| |
| # check all drop-downs
| |
| # press on summary/stats button
| |
| # do an intersection with a couple of different output formats
| |
| # make sure filtering is functioning
| |
| # create a custom track in the browser
| |
| # check all output formats
| |
| # try sending output to Galaxy and GREAT; make sure checkboxes stay checked when applying filters, etc.
| |
| # do a subtrack merge (select a table from a composite track to get the option)
| |
| # do a correlation
| |
| # try defining regions
| |
| | |
| ==hgPal==
| |
| # check a "Protein FASTA" click-through from a UCSC Gene details page
| |
| # check a "CDS FASTA" click-through from a RefSeq Genes details page
| |
| # using the Table Browser, choose "CDS FASTA" as the output format (this should work for any [http://genome.ucsc.edu/FAQ/FAQformat.html#format9 genePred] track)
| |
| # check that different settings give expected results
| |
| | |
| ==hgBlat==
| |
| # perform both a nucleotide and a protein search with default settings
| |
| # make sure colors listed in description section are right
| |
| # zoom in on an alignment and test "View details of parts of alignment within browser window"
| |
| # try different sorts and output types
| |
| # make sure all the buttons work, including uploading a file
| |
| # try uploading a file with too many bases or too many queries and verify error message
| |
| | |
| ==hgPcr==
| |
| # test some perfectly matching primers, including a pair on the negative strand
| |
| # find a pair of primers that shouldn't match UCSC Genes and test that they don't
| |
| # vary settings and input primers for several assemblies and see if results make sense
| |
| # for human and mouse browsers, test the "UCSC Genes" target. Check that UI functions as expected
| |
| # check that the UI functions as expected for regular primers as well
| |
| | |
| ==hgLiftOver, hgConvert==
| |
| # Choose an assembly and go to hgTracks
| |
| # Hit "Convert" in the blue bar at the top of the page
| |
| # Compare the output to the same conversion using liftOver:
| |
| # LiftOver is at Home -> Utilities -> Batch Coordinate Conversion (liftOver)
| |
| # Test both position and BED format
| |
| # Test a variety of settings
| |
| # Try converting multiple positions at once
| |
| # Try uploading a file
| |
| | |
| ==pbGateway, pbGlobal, pbTracks==
| |
| # general testing; click around
| |
| # enter a protein symbol
| |
| # review results page
| |
| # click into pbGlobal and check display
| |
| | |
| ==hgSession==
| |
| #check that a new session can be saved
| |
| #check that old sessions are still there
| |
| #delete a session
| |
| #check browser & email button; click the title of session & make sure you can save changes to the description
| |
| #try loading a session via a file and via a URL
| |
| #logout and try to load a session that can be shared and one that can't be shared
| |
| | |
| ==hgGenome==
| |
| #find it by going Home -> Genome Graphs
| |
| #upload a dataset from a file
| |
| #upload a data set from a URL
| |
| #import data from a track
| |
| #change some configurations
| |
| #check that "browse regions" & "sort genes" work
| |
| #check the correlate button
| |
| Some good genome graph data for testing: http://hgwdev.cse.ucsc.edu/~rhead/genomeGraphsWithColumns
| |
| | |
| ==cartDump, cartReset==
| |
| # check cart
| |
| # reset cart
| |
| # 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. | |
| # 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.
| |
| # 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.
| |
| | |
| ==hgEncodeVocab==
| |
| # Go to an ENCODE track, most matrix headers should be links. Click on them, should take you to a page with a row of info about the term.
| |
| # Go to a couple of these pages and check that the sections are displaying (these pages use hgEncodeVocab to display the info on them):
| |
| #* [http://hgw2.cse.ucsc.edu/ENCODE/otherTerms.html Registered Variables]
| |
| #* [http://hgw2.cse.ucsc.edu/ENCODE/antibodies.html Antibodies]
| |
| #* [http://hgw2.cse.ucsc.edu/ENCODE/cellTypes.html Human Cell Types]
| |
| #* [http://hgw2.cse.ucsc.edu/ENCODE/cellTypesMouse.html Mouse Cell Types]
| |
| # Check a few links in the metadata from hgc details (click "metadata" link to view other links) or hgTrackUi (click "..." link to view other links)
| |
| | |
| [[Category:Browser QA]]
| |
