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

Steve

• tests hgTracks (includes checking Track Search and running TrackCheck), regardless of whether any changes were made or there are any tickets associated with hgTracks

Greg

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

Pauline

• tests and tracks redmine issues for hgTables

Brooke

• tests if needed, tracks redmine issues for:
  • hgPal, hgNear, hgBlat, hgPcr, hgTrackUi, hgc, hgHubConnect

Brian

• tests and tracks redmine issues for hgEncodeApi
• tests if needed, tracks redmine issues for:
  • hgFileUi, hgEncodeVocab, hgFileSearch

Katrina

• tests and tracks redmine issues for hgTracks
• tests if needed, tracks redmine issues for:
  • hgConvert, hgLiftOver

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
• hgLogin
• hgEncodeApi

List of CGIs that we don't test

• hgSuggest
• cartDump
• cartReset
• pbGlobal
• pbTracks
• pbGateway
• das
• hgText (we no longer push this CGI, will be dropped from RR on 07.24.12)
• hgEncodeDataVersions
• phyloGif
• hgGateway
• hgRenderTracks