Pre-QA

About Pre-QA

Preliminary QA, or pre-QA, is the initial review that tracks undergo. The pre-QAer mainly checks hgTrackUi (functionality and content), 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. The goal is for pre-QA to get tracks ready for full QA from a QA staffer.

Intro to Pre-QA Resources

Here is a brief introduction to the resources used in pre-QA:

Redmine

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 by clicking on the "Passed Pre-QA" checkbox.

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 Redmine wiki

PushQ

The 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).

QA wiki pages

Genome Browser QA wiki

The New_track_checklist wiki page is where we keep the step-by-step instructions for QAing a Genome Browser track. The steps on that page that should be done by a pre-QAer are marked "(pre-QA)".

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 hgTrackUi and Files (except 8.1.1) sections.

hgwdev

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 track search.

Pre-QA Step-by-Step

Claim track in PushQ

Pick a track from the PushQ that is not claimed (ignore anything with "FIX" in the title) and claim it:

1. Click on the Id number, click "Lock"
2. Enter your name in the "reviewer" section
3. Click "submit"
4. Determine the redmine ticket number for next step by scrolling down to the notes section.

Claim the redmine ticket

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

Find track in browser & go to hgTrackUi

1. Go to hgwdev
2. Set the 3 drop-down menus to the correct assembly (e.g. Mammal, Human, Feb.2009 (GRCh37/hg19). See the list of assemblies.
3. Click the "track search" button (also, here is a direct link to hg19 track search)
4. Enter the name of the track (e.g. Broad HMM) and click "search" button
5. Click the "folder/wrench" icon next to your track

Follow Pre-QA Steps for your Project

• For the Genome Browser, follow steps marked "Pre-QA" on this page.
• For the ENCODE project, follow this page.

Update Redmine ticket & Get fixes

Enter any issues in the redmine ticket for that track (can be done as you pre-QA).

1. Go to redmine to your "My Page" and select the appropriate ticket.
2. Click "update", enter your comments. At the bottom, where you see "Assign question to," enter the developer/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 Redmine and PushQ

Once you have completed pre-QA and all issues you found have been addressed/fixed:

1. Check the "Passed pre-QA" check-box in the redmine issue and remove your name from the "Assigned to" field of the issue.
2. Remove your name from the "reviewer" field in the pushQ entry.