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

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

Steve

• tests and tracks redmine issues for hgTables
• tests if needed, tracks redmine issues for: hgSession

Pauline

• push shepherd

Brian

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

Jonathan

• tests and tracks redmine issues for hgUserSuggestion, hgVai
• tests if needed, and tracks issues for hgPal, hgNear, hgc, hgLogin, hgVisiGene, hgGenome

List of CGIs that we test

• hgVai
• hgUserSuggestion
• 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
• das
• hgEncodeDataVersions
• phyloGif
• hgGateway
• hgRenderTracks

List of CGIs that we no longer push (have been dropped from the RR)

• hgText
• pbGlobal
• pbTracks
• pbGateway