CGI testing responsibilities: Difference between revisions

Revision as of 20:10, 6 November 2018

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.

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

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

tests and tracks redmine issues for: hgCollection
tests if needed, tracks redmine issues for: hgIntegrator, hgCustom, hgc
official GBiB tester (includes hgMirror)

@@ Line 14: / Line 14: @@
 ==Conner==
 * tests and tracks redmine issues for: '''hgTracks''' (includes checking '''Track Search''' and running '''TrackCheck''')
-* tests if needed, tracks redmine issues for:  '''hgTrackUi''', '''hgGtexTrackSettings''' ,'''hgGene''',  '''hgGeneGraph'''
+* tests if needed, tracks redmine issues for:  '''hgTrackUi''', '''hgGtexTrackSettings''','''hgGene''',  '''hgGeneGraph'''
 ==Daniel==