CGI testing responsibilities: Difference between revisions

From Genecats
Jump to navigationJump to search
No edit summary
Line 1: Line 1:
Also see: [http://genecats.cse.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]].


There is going to be a "guest CGI" each release. For now we are going to try having at least 2 of the 4 people tracking redmine issues test that CGI.
==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.
 
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.


==Pauline==
==Pauline==

Revision as of 20:41, 19 August 2011

Also see: version notes and CGI_Testing.

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.

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, 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.

Pauline

  • push shepherd

Vanessa

  • tests hgTracks (includes checking Track Search and running TrackCheck)

Brooke

  • tests hgTables

Mary

  • tracks redmine issues for:
    • hgTracks
  • possibly tests guest CGI

Luvina

  • tests if needed, tracks redmine issues for:
    • hgTables, hgPal, hgNear, hgConvert, hgLiftOver, hgBlat, hgPcr
  • possibly tests guest CGI

Greg

  • tests if needed, tracks redmine issues for:
    • hgCustom, hgSession, hgGenome, hgGene, hgVisiGene, hgHubConnect
  • possibly tests guest CGI

Katrina

  • tests if needed, tracks redmine issues for:
    • hgTrackUi, hgc, hgFileUi, hgFileSearch, hgEncodeVocab
  • coordinates testing of guest CGI

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

List of CGIs that we don't test

  • hgSuggest
  • cartDump
  • cartReset
  • pbGlobal
  • pbTracks
  • pbGateway
  • das
  • hgText
  • hgEncodeDataVersions
  • mkEncodeFrameset
  • phyloGif
  • hgGateway
Retrieved from "https://genomewiki.ucsc.edu/genecats/index.php?title=CGI_testing_responsibilities&oldid=474"