CGI testing responsibilities: Difference between revisions

From Genecats
Jump to navigationJump to search
(switched Greg <-> Mary)
No edit summary
 
(155 intermediate revisions by 10 users not shown)
Line 2: Line 2:


==Process==
==Process==
There will be a "guest CGI" each release. The Push Shepherd will place an asterisk next to the "guest CGI" in the "testing responsibilities" issue associated with the release. One person, noted below, will be responsible for coordinating the testing of that guest CGI.
* 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.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.


Each person (except the Push Shepherd) should review the [http://genecats.cse.ucsc.edu/builds/versions.html 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, whether it's listed in redmine or not, '''add your name to the *description* section of the "testing responsibilities" issue like so "hgCustom - Greg"'''. This will be the clue to the Push Shepherd to wait for you to note "done testing" in the "testing responsibilities" issue before pushing the CGIs.
* Also see details for testing CGIs on the [http://genomewiki.ucsc.edu/genecats/index.php/CGI_Testing CGI Testing] page.


==Pauline==
==Brian==
* push shepherd
* updates and runs post-release script on preview2/beta/RR
* monitors '''genome-euro''' and  '''genome-asia'''  logs after push to RR


==Vanessa==
==Jairo==
* tests '''hgTracks''' (includes checking Track Search and running TrackCheck)
* '''The Push Shepherd'''
* Tests and splits redmine issues for:  '''hgTracks''' (includes checking '''Track Search''' and running '''TrackCheck''')
* Performs single thorough test of, and tracks redmine issues for:
** hgApi
** hgFileSearch
** hgGtexTrackSettings
** hgLogin
** hgPhyloPlace
** hgUserSuggestion


==Brooke==
==Lou==  
* tests '''hgTables'''
* Tests and splits redmine issues for: '''hgTracks'''
* Performs single thorough test of, and tracks redmine issues for:
** hgCollection
** hgFileUi
** hgGene
** hgHubConnect
** hgTrackUi
** hgVai
** hgVisiGene
** hgLiftOver, hgConvert
** cartDump, cartReset


==Greg==
==Dan==
* tracks redmine issues for:
* Performs single thorough test of, and tracks redmine issues for:
** '''hgTracks'''
** hgBlat
* possibly tests guest CGI
** hgc
** hgCustom
** hgGeneGraph
** hgIntegrator
** hgNear
** hgPal
** hgPcr


==Luvina==
==Gerardo==
* tests if needed, tracks redmine issues for:
* [http://genomewiki.ucsc.edu/genecats/index.php/GBiB_Testing#Official_GBiB_Tester official GBiB tester] (includes '''hgMirror''')
** '''hgTables''', hgPal, hgNear, hgConvert, hgLiftOver, hgBlat, hgPcr
* Performs single thorough test of, and tracks redmine issues for:
* possibly tests guest CGI
** hgGateway
 
** hgGenome
==Mary==
** hgLinkIn
* tests if needed, tracks redmine issues for:
** hgPublicSessions
** hgCustom, hgSession, hgGenome, hgGene, hgVisiGene, hgHubConnect
** hgSession
* possibly tests guest CGI
** hgTables
 
** hubApi
==Katrina==
** hgTables (looks at output each build for hgTables test robot)
* tests if needed, tracks redmine issues for:
** GBiC
** hgTrackUi, hgc, hgFileUi, hgFileSearch, hgEncodeVocab
* coordinates testing of guest CGI


==List of CGIs that we test==
==List of CGIs that we test==
*hgTracks
*hgc
*hgPcr
*hgCollection
*hgCustom
*hgCustom
*hgGenome
*hgBlat
*hgFileUi
*hgFileSearch
*hgTrackUi
*hgConvert
*hgLiftOver
*hgTables
*hgGene
*hgGene
*hgVisiGene
*hgGeneGraph
*hgPal
* hgGtexTrackSettings
*hgHubConnect
*hgIntegrator
*hgLogin
*hgMirror
*hgPublicSessions
*hgSession
*hgSession
*hgEncodeVocab
*hgTables
*hgNear
*hgTracks
*hgc
*hgTrackUi
*hgHubConnect
*hgVai


==List of CGIs that we don't test==
==List of CGIs that we don't test==
*hgSuggest
*cartDump
*cartDump
*cartReset
*cartReset
*pbGlobal
*pbTracks
*pbGateway
*das
*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
*hgText
*hgEncodeDataVersions
*pbGateway
*mkEncodeFrameset
*pbGlobal
*phyloGif
*pbTracks
*hgGateway
 


[[Category:Browser QA]]
[[Category:Browser QA]]
[[Category:Browser QA CGI]]
[[Category:Browser QA CGI]]

Latest revision as of 20:54, 18 April 2022

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.

Brian

  • updates and runs post-release script on preview2/beta/RR
  • monitors genome-euro and genome-asia logs after push to RR

Jairo

  • The Push Shepherd
  • Tests and splits redmine issues for: hgTracks (includes checking Track Search and running TrackCheck)
  • Performs single thorough test of, and tracks redmine issues for:
    • hgApi
    • hgFileSearch
    • hgGtexTrackSettings
    • hgLogin
    • hgPhyloPlace
    • hgUserSuggestion

Lou

  • Tests and splits redmine issues for: hgTracks
  • Performs single thorough test of, and tracks redmine issues for:
    • hgCollection
    • hgFileUi
    • hgGene
    • hgHubConnect
    • hgTrackUi
    • hgVai
    • hgVisiGene
    • hgLiftOver, hgConvert
    • cartDump, cartReset

Dan

  • Performs single thorough test of, and tracks redmine issues for:
    • hgBlat
    • hgc
    • hgCustom
    • hgGeneGraph
    • hgIntegrator
    • hgNear
    • hgPal
    • hgPcr

Gerardo

  • official GBiB tester (includes hgMirror)
  • Performs single thorough test of, and tracks redmine issues for:
    • hgGateway
    • hgGenome
    • hgLinkIn
    • hgPublicSessions
    • hgSession
    • hgTables
    • hubApi
    • hgTables (looks at output each build for hgTables test robot)
    • GBiC

List of CGIs that we test

  • hgc
  • hgCollection
  • hgCustom
  • hgGene
  • hgGeneGraph
  • hgGtexTrackSettings
  • 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=5869"