CGI testing responsibilities: Difference between revisions

From Genecats
Jump to navigationJump to search
(Link changed from .soe or .cse to .gi)
(Undo revision 4732 by Daniel (talk))
Line 1: Line 1:
Also see: [http://genecats.gi.ucsc.edu/builds/versions.html version notes] and [[CGI_Testing]].
Also see: [http://genecats.cse.ucsc.edu/builds/versions.html version notes] and [[CGI_Testing]].


==Process==
==Process==
* For the changes you are tracking, check if there any new features that need to be added to our trackDb documentation [http://genome.ucsc.edu/goldenPath/help/trackDb/trackDbDoc.html DbDoc] [http://genome.ucsc.edu/goldenPath/help/trackDb/trackDbHub.html DbHub], and be sure to request the engineer documents it (and then push out the pages after the release).
* For the changes you are tracking, check if there any new features that need to be added to our trackDb documentation [http://genome.ucsc.edu/goldenPath/help/trackDb/trackDbDoc.html DbDoc] [http://genome.ucsc.edu/goldenPath/help/trackDb/trackDbHub.html 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 [http://genecats.gi.ucsc.edu/builds/versions.html 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.  
* Each person (except the Push Shepherd) should review the [http://genecats.cse.ucsc.edu/builds/versions.html 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.
* 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.


Revision as of 16:54, 29 August 2018

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.
  • Also see details for testing CGIs on the CGI Testing page.

Ann on Release day

Manual test of hgTables and hgTracks

Brian

  • tests and tracks redmine issues for: hgTracks (includes checking Track Search and running TrackCheck)
  • monitors genome-euro and genome-asia logs after push to RR
  • tests if needed, tracks redmine issues for: hgSession, hgPublicSessions, hgLogin

Daniel

  • tests if needed, tracks redmine issues for: hgVai

TBD

  • tests if needed, tracks redmine issues for: hgGene, hgTrackUi, hgGtexTrackSettings
  • tests if needed, tracks redmine issues for: hgHubConnect, hgCustom, hgc, hgGeneGraph

Jairo

  • The Push Shepherd
  • tests and tracks redmine issues for: hgCollection
  • official GBiB tester (includes hgMirror)


Lou

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


List of CGIs that we test

  • hgc
  • hgCollection
  • hgCustom
  • hgGene
  • hgGeneGraph
  • hgHubConnect
  • hgIntegrator
  • hgLogin
  • hgMirror
  • hgPublicSessions
  • hgSession
  • hgTables
  • hgTracks
  • hgTrackUi
  • 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
  • hgFileSearch
  • hgFileUi
  • hgGateway
  • hgGenome
  • hgLiftover
  • hgLinkIn
  • hgMenubar
  • hgNear
  • hgPal
  • hgPcr
  • hgRenderTracks
  • hgSuggest
  • hgUserSuggestion
  • hgVisigene
  • phyloPng

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

  • hgText
  • pbGateway
  • pbGlobal
  • pbTracks
Retrieved from "https://genomewiki.ucsc.edu/genecats/index.php?title=CGI_testing_responsibilities&oldid=4767"