CGI testing responsibilities

Also see: version notes and CGI_Testing.

Process

Each person (except the Push Shepherd) should review the Code Summaries to see if developers have checked in code pertaining to their CGI(s). Sometimes developers make big changes to CGIs that are not listed in Redmine, and this is the only way to catch them before they leak out. If you find something you are going to test, and there is no Redmine ticket for it, please make a note in the CGI release chatter Redmine ticket. This will be the clue to the Push Shepherd to wait for you to note "done testing" (also in the CGI release chatter ticket) before pushing the CGIs.

Luvina

• push shepherd

Vanessa

• tests hgTracks (includes checking Track Search and running TrackCheck)

Greg

• tracks redmine issues for:
  • hgTracks

Brooke

• tests and tracks redmine issues for hgTables

Pauline

• tests if needed, tracks redmine issues for:
  • hgPal, hgNear, hgConvert, hgLiftOver, hgBlat, hgPcr, hgHubConnect

Steve

• tests if needed, tracks redmine issues for:
  • hgCustom, hgSession, hgGenome, hgGene, hgVisiGene

Katrina

• tests if needed, tracks redmine issues for:
  • hgTrackUi, hgc, hgFileUi, hgFileSearch, hgEncodeVocab

List of CGIs that we test

• hgTracks
• hgPcr
• hgCustom
• hgGenome
• hgBlat
• hgFileUi
• hgFileSearch
• hgTrackUi
• hgConvert
• hgLiftOver
• hgTables
• hgGene
• hgVisiGene
• hgPal
• hgSession
• hgEncodeVocab
• hgNear
• hgc
• hgHubConnect

List of CGIs that we don't test

• hgSuggest
• cartDump
• cartReset
• pbGlobal
• pbTracks
• pbGateway
• das
• hgText
• hgEncodeDataVersions
• mkEncodeFrameset
• phyloGif
• hgGateway
• hgRenderTracks