View source for Pre-QA

=About Pre-QA=
Preliminary QA, or pre-QA, is the initial review ENCODE tracks undergo. The pre-QAer mainly checks hgTrackui (functionality and content), hgFileUi, and the index page to make sure all the necessary components are in place, takes a first pass at editing the description, and checks for basic functionality. Hopefully pre-QA will speed up the QA of ENCODE tracks.

=Intro to Pre-QA Resources=
Here is a brief introduction to the resources used in pre-QA
==Redmine==
[http://redmine.soe.ucsc.edu Redmine] is our tracking system. This is where we track new tracks for release, features, bugs and documentation changes, and this is where pre-QAer enters any feedback about the tracks. When pre-QA is complete, you'll note this in the redmine ticket.

A couple notes about using Redmine:
* When replying to a redmine update/issue via email, use "Reply" rather than "reply all"
* Delete all text and enter your message (remove all of the previous thread)
* For more info see the [http://redmine.soe.ucsc.edu/projects/genomebrowser/wiki Redmine wiki]

==PushQ==
The [http://hgwbeta.cse.ucsc.edu/cgi-bin/qaPushQ pushQ] is our queue of tracks that are ready for QA. This is where you will figure out which tracks to review. You will only be working on the tracks listed in the "A" section (top-most section). When you've completed pre-QA, you'll put a note in the the "Notes" section.

==ENCODE QA wiki==
The [[ENCODE QA]] wiki page is where we keep the step-by-step instructions for QAing an ENCODE track. For pre-QA, you'll work on the [[ENCODE QA#hgTrackUi|hgTrackUi]] and [[ENCODE QA#Files|Files]] (except 8.1.1) sections.

==hgwdev==
[http://hgwdev.cse.ucsc.edu/cgi-bin/hgGateway hgwdev] is our test browser, which you'll use for pre-QA. The easiest way to get to the track control & description page (hgTrackUi) is via the [http://hgwdev.cse.ucsc.edu/cgi-bin/hgTracks?db=hg19&hgt_tSearch=1 track search].

=Pre-QA Step-by-Step=
==Claim track in PushQ==
Pick a track from the PushQ (ignore anything with "FIX" in the title) and claim it:
# Click on the Id number, click "Lock"
# Enter your name in the "reviewer" section
# Click "submit"
# Determine the redmine ticket number for next step by scrolling down to the notes section.

==Claim the redmine ticket==
# Sign into redmine
# Enter a "#" sign followed by the ticket number in the search field (e.g. #4893)
# Add the current "Assigned to" person as a watcher (on the far left, next to "Watcher" click add, select their name and click "Add")
# Add QA team lead as a "Watcher"
# Click "update" and change the "Assigned to" to yourself & click "submit"

==Find track in browser & go to hgTrackUi==
# Go to [http://hgwdev.cse.ucsc.edu/cgi-bin/hgGateway hgwdev]
# Set the 3 drop-down menus to the following (if they aren't already: Mammal, Human, Feb.2009 (GRCh37/hg19) Note: If you are searching for any other animal i.e mouse, make sure to select mouse from the second drop down menu).
# Click the "track search" button (also, here is a direct link to [http://hgwdev.cse.ucsc.edu/cgi-bin/hgTracks?db=hg19&hgt_tSearch=1 hg19 track search])
# Enter the name of the track (e.g. Broad HMM) and click "search" button
# Click the "folder/wrench" icon next to your track

==Pre-QA hgTrackUi==
Follow the [[ENCODE QA#hgTrackUi|hgTrackUi]] wiki section (content = most important, jury still out on functionality)

===Content===
* skip [[ENCODE QA#Labels|Labels]] section

===Functionality===
* [[ENCODE_QA#Config_Settings_of_Views|Config Settings of Views]]: skip "Check that expId is hidden in "..." on hgwbeta. If it isn't, there is an issue."
* [[ENCODE QA#MetaData"|MetaData]]: skip "in dense, default fixed range should result in meaningful banding at full chromosome (not all gray)"
* [[ENCODE_QA#Links|Links]]: skip "...where applicable, are relative"

==Pre-QA Files==
Follow the [[ENCODE QA#Files|Files]] wiki section, 
* skip the [[ENCODE QA#File Count|File Count]] sub-section.

==Update Redmine ticket & Get fixes==
Enter any issues in the redmine ticket for that track (can be done as you pre-QA).
# Go to redmine to your "My Page" and select the appropriate ticket.
# Click "update", enter your comments. At the bottom, where you see "Assign question to," enter the wrangler (person you added as watcher, also listed as the "Sponsor" in the pushQ), then click "preview" to see how your comment will look, you can edit more, click "Submit" when satisfied.
==Note Pre-QA Pass in PushQ and Redmine==
Once you have completed pre-QA and all issues you found have been addressed/fixed:
# Add comment to redmine ticket, "Passed pre-QA" and reassign to wrangler
# Add comment to 'Notes' section of PushQ entry, "<date> Passed pre-QA (<name>)", and remove your name from the "reviewer" field.

[[Category:Browser QA ENCODE]][[Category:Browser QA ]]