CGI testing responsibilities: Difference between revisions

From Genecats
Jump to navigationJump to search
(Edits to move hgPal hgGenome hgVisiGene out of our testing list to CGIs we don't test)
Line 12: Line 12:
==Cath==
==Cath==
* tests and tracks redmine issues for: '''hgTracks''' (includes checking '''Track Search''' and running '''TrackCheck''')
* tests and tracks redmine issues for: '''hgTracks''' (includes checking '''Track Search''' and running '''TrackCheck''')
* tests if needed, tracks redmine issues for:  '''hgNear''', '''hgVisiGene''', '''hgGtexTrackSettings'''
* tests if needed, tracks redmine issues for:  '''hgNear''', '''hgGtexTrackSettings'''


==ChrisL==
==ChrisL==
* [http://genomewiki.ucsc.edu/genecats/index.php/GBiB_Testing#Official_GBiB_Tester official GBiB tester] (includes '''hgMirror''')
* [http://genomewiki.ucsc.edu/genecats/index.php/GBiB_Testing#Official_GBiB_Tester official GBiB tester] (includes '''hgMirror''')
* tests if needed, tracks redmine issues for:  '''hgHubConnect''', '''hgGenome'''
* tests if needed, tracks redmine issues for:  '''hgHubConnect'''


==ChrisV==
==ChrisV==
Line 27: Line 27:


==Luvina==
==Luvina==
* tests if needed, tracks redmine issues for: '''hgGene''', '''hgPal''',  '''hgc''',  '''hgTrackUi''', '''hgUserSuggestion'''
* tests if needed, tracks redmine issues for: '''hgGene''', '''hgc''',  '''hgTrackUi''', '''hgUserSuggestion'''


==Matt==
==Matt==

Revision as of 19:57, 21 June 2017

Also see: version notes and CGI_Testing.

Process

  • For the changes you are tracking, check if there any new features that need to be added to our trackDb documentation DbDoc DbHub, and be sure to request the engineer documents it (and then push out the pages after the release).
  • Each person (except the Push Shepherd) should review the Code Summaries and Redmine 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. The chatter ticket is the way to provide clues to the Push Shepherd to wait for you to note "done testing" (also noted in the CGI release chatter ticket) before pushing the CGIs.

Brian

  • monitors genome-euro and genome-asia logs after push to RR

Cath

  • tests and tracks redmine issues for: hgTracks (includes checking Track Search and running TrackCheck)
  • tests if needed, tracks redmine issues for: hgNear, hgGtexTrackSettings

ChrisL

ChrisV

  • tests and tracks redmine issues for: hgIntegrator
  • tests if needed, tracks redmine issues for: hgVai, hgCustom, hgFileSearch, hgFileUi

Jairo

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

Luvina

  • tests if needed, tracks redmine issues for: hgGene, hgc, hgTrackUi, hgUserSuggestion

Matt

  • The Push Shepherd

List of CGIs that we test

  • hgc
  • hgCustom
  • hgFileSearch
  • hgFileUi
  • hgGene
  • hgGeneGraph
  • hgHubConnect
  • hgIntegrator
  • hgLogin
  • hgMirror
  • hgNear
  • hgPublicSessions
  • hgSession
  • hgTables
  • hgTracks
  • hgTrackUi
  • hgUserSuggestion
  • hgVai

List of CGIs that we don't test

  • cartDump
  • cartReset
  • das
  • hgBlat
  • hgConvert
  • hgEncodeApi
  • hgEncodeDataVersions -this hasn't been used since hg17 and hg18.
  • hgEncodeVocab
  • hgGateway
  • hgGenome
  • hgLiftover
  • hgLinkIn
  • hgMenubar
  • hgPal
  • hgPcr
  • hgRenderTracks
  • hgSuggest
  • hgVisigene
  • phyloPng

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

  • hgText
  • pbGateway
  • pbGlobal
  • pbTracks