QA Home Page: Difference between revisions

From Genecats
Jump to navigationJump to search
(Genome Browser Setup)
 
(24 intermediate revisions by 7 users not shown)
Line 1: Line 1:
== General Goals ==
== General Goals ==
* Monitor Apache for error 500, target 0.2% a month.
* Monitor Apache for error 500, target 0.2% a month.
* No more than 2 data [http://genecats.cse.ucsc.edu/qa/repush.html repushes] a month.
* No more than 2 data [http://genecats.soe.ucsc.edu/qa/repush.html repushes] a month.
* No more than 1 hour [http://genecats.cse.ucsc.edu/qa/sla.html downtime] during normal business hours.
* No more than 1 hour [http://genecats.soe.ucsc.edu/qa/sla.html downtime] during normal business hours.


==Genome Browser Setup==
==Genome Browser Setup==
* See Jorge's Presentation on the [http://genomewiki.ucsc.edu/images/d/d5/Browsermap.pdf server setup].
* See Jorge's Presentation on the [http://genomewiki.ucsc.edu/images/d/d5/Browsermap.pdf server setup].
* External site about our architecture: http://oliverelliott.org/article/bioinformatics/tut_genomebrowser/
==GIT (Source Code Management System)==
*[http://genomewiki.ucsc.edu/index.php/Getting_Started_With_Git Getting_Started_With_Git]
*[http://genomewiki.ucsc.edu/index.php/Working_with_Git Working_with_Git]
* Once you've read up...ask for git [[commit access]].
==Editing Static Docs==
* Editing [[Static_Page_Protocol | static pages]] that are destined for the RR (Round Robin), hgdownload, or linked to genomewiki.
* Need to have links hard coded to the RR, but need to test them on the development machines? Take a look at how you can use [[Static_Page_JS_Protocol | javaScript]] with the static pages.
==CGI Build Process & Testing ==
* Currently we are on a 3 week CGI software release schedule. See [[CGI_Build_Schedule]] for more details.
**The google calendar version should be added to your own google calendar. More [[Welcome_to_Browser_Staff#Computer_Accounts.2C_Email_and_Google_Apps | information.]]
* The buildmeister follows this [[CGI_Build_Process | process]].
* When the CGIs are loaded on hgwbeta, the QA'er tests their [[CGI_testing_responsibilities | assigned CGIs]]. The general CGI testing instructions can be found [[CGI_Testing |here]].
* Currently we try to test our CGI's in Internet Explorer & Firefox due to the high [[Internet_browser_testing | browser usage]].
** Brand new CGIs should be tested on the latest version of IE and FF.
** All CGIs should be tested using the latest version of IE after they are built on hgwbeta.
** On release day QA'ers test using their browser of choice, except the designated IE tester.
* If you don't have access to a Windows machine with Internet Explorer, there is a [[Windows_testing_machine | machine]] you can log into.
==Cell Browser release process==
Instructions for releasing the Cell Browser are found [[Cell Browser Release Process]]
==GBiB and GBiC release process==
The GBiB and GBiC release process are documented here [[GBi* Release Process]].
To see how the [http://genomewiki.ucsc.edu/genecats/index.php/GBiB_Testing#Official_GBiB_Tester GBiB] and [http://genomewiki.ucsc.edu/genecats/index.php/GBiC_Testing GBiC] files are tested start at [http://genomewiki.ucsc.edu/genecats/index.php/CGI_Testing#GBiB the CGI_Testing page.]


==QAing tracks/assemblies ==
==QAing tracks/assemblies ==
* Browser QA process:
* Browser QA process:
** [[Releasing_an_assembly | New Assemblies]]
** [[Releasing_an_assembly | New Assemblies]]
** [[New_track_checklist | New track checklist]]
** [http://genomewiki.ucsc.edu/genecats/index.php/Category:Browser_QA_tracks Specific Genome Browser Tracks]
** [http://genomewiki.ucsc.edu/genecats/index.php/Category:Browser_QA_tracks Specific Genome Browser Tracks]
* [[ENCODE_QA | Encode QA process]]
* [[ENCODE_QA | Encode QA process]]
==CGI Build Process & Testing ==
* Currently we are on a 3 week CGI software release schedule. See [[CGI_Build_Schedule]] for more details.
* The buildmeister follows this [[CGI_Build_Process | process]].
* When the CGIs are loaded on hgwbeta, the QA'er tests their [[CGI_testing_responsibilities | assigned CGIs]]. The general CGI testing instructions can be found [[CGI_Testing |here]].


==Mailing List Maven==
==Mailing List Maven==
* Mailing list schedule can be found on the [https://kkstore.cse.ucsc.edu/calendar/plans.cgi?active_tab=0 QA group calendar] (Note: where it says '''Calendar:''', you will need to change the drop down from "Main" to "QA" to view.)
* Mailing list schedule can be found on the Genome Browser Mail List soe google calendar. More [[Welcome_to_Browser_Staff#Computer_Accounts.2C_Email_and_Google_Apps | information.]]
* Mailing list procedure can be found on the [http://redmine.soe.ucsc.edu/projects/maillists/wiki redmine wiki]  
* Mailing list procedure can be found on the [http://redmine.soe.ucsc.edu/projects/maillists/wiki redmine wiki]  
* Places to search for answers:
* Places to search for answers:
Line 32: Line 58:
** Ex: w/o session id: http://genome.ucsc.edu/cgi-bin/hgTrackUi?db=hg19&g=geneid (note that links to description pages should include the database: '''db=hg19&''')
** Ex: w/o session id: http://genome.ucsc.edu/cgi-bin/hgTrackUi?db=hg19&g=geneid (note that links to description pages should include the database: '''db=hg19&''')
* Most other links without an hgsid will likely not work.  Instead, create a [http://genome.ucsc.edu/cgi-bin/hgSession?hgS_doMainPage=1 session].
* Most other links without an hgsid will likely not work.  Instead, create a [http://genome.ucsc.edu/cgi-bin/hgSession?hgS_doMainPage=1 session].
* Make sure none of the links you respond with are to our internal servers, such as hgwdev.  Typically we should only send links to genome.ucsc.edu, genome-preview.ucsc.edu, and to hgdownload.cse.ucsc.edu.
* If you click on a link supplied by a user that includes an hgsid, do not change any settings until you reset your cart.
* Make sure none of the links you respond with are to our internal servers, such as hgwdev.  Typically we should only send links to genome.ucsc.edu, genome-preview.ucsc.edu, and to hgdownload.soe.ucsc.edu.
 
==Updating Blat Servers==
See this [[Updating_blat_servers | page]] for more information.
 
==Tools==
*Vi
** Don't have a text editor of choice? Learn how to use vi by typing in "'''vimtutor'''" on the command line on hgwdev.
** Vi Quick Start [[VI_quick_start | Guide]]
** Handy [http://www2.cs.uidaho.edu/~rinker/ed03.pdf Cheat Sheet]


==GIT (Source Code Management System)==
*[[UNIX_Commands | UNIX Commands]]
*[http://genomewiki.ucsc.edu/index.php/Getting_Started_With_Git Getting_Started_With_Git]
*[[MySQL_Commands | MySQL Commands]]
*[http://genomewiki.ucsc.edu/index.php/Working_with_Git Working_with_Git]
*[[QA_scripts| Common Scripts]]
* Once you've read up...ask to take the Git Quiz.
*[http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet Wiki Cheat Sheet]




[[Category: Browser QA]]
[[Category: Browser QA]]
[[Category: Browser QA Training]]
[[Category: Browser QA Training]]

Latest revision as of 21:23, 22 December 2020

General Goals

  • Monitor Apache for error 500, target 0.2% a month.
  • No more than 2 data repushes a month.
  • No more than 1 hour downtime during normal business hours.

Genome Browser Setup

GIT (Source Code Management System)

Editing Static Docs

  • Editing static pages that are destined for the RR (Round Robin), hgdownload, or linked to genomewiki.
  • Need to have links hard coded to the RR, but need to test them on the development machines? Take a look at how you can use javaScript with the static pages.

CGI Build Process & Testing

  • Currently we are on a 3 week CGI software release schedule. See CGI_Build_Schedule for more details.
    • The google calendar version should be added to your own google calendar. More information.
  • The buildmeister follows this process.
  • When the CGIs are loaded on hgwbeta, the QA'er tests their assigned CGIs. The general CGI testing instructions can be found here.
  • Currently we try to test our CGI's in Internet Explorer & Firefox due to the high browser usage.
    • Brand new CGIs should be tested on the latest version of IE and FF.
    • All CGIs should be tested using the latest version of IE after they are built on hgwbeta.
    • On release day QA'ers test using their browser of choice, except the designated IE tester.
  • If you don't have access to a Windows machine with Internet Explorer, there is a machine you can log into.

Cell Browser release process

Instructions for releasing the Cell Browser are found Cell Browser Release Process

GBiB and GBiC release process

The GBiB and GBiC release process are documented here GBi* Release Process.

To see how the GBiB and GBiC files are tested start at the CGI_Testing page.

QAing tracks/assemblies

Mailing List Maven

  • Mailing list schedule can be found on the Genome Browser Mail List soe google calendar. More information.
  • Mailing list procedure can be found on the redmine wiki
  • Places to search for answers:
  • Remember that when you email users, make sure the links don't have session id's.
  • Most other links without an hgsid will likely not work. Instead, create a session.
  • If you click on a link supplied by a user that includes an hgsid, do not change any settings until you reset your cart.
  • Make sure none of the links you respond with are to our internal servers, such as hgwdev. Typically we should only send links to genome.ucsc.edu, genome-preview.ucsc.edu, and to hgdownload.soe.ucsc.edu.

Updating Blat Servers

See this page for more information.

Tools

  • Vi
    • Don't have a text editor of choice? Learn how to use vi by typing in "vimtutor" on the command line on hgwdev.
    • Vi Quick Start Guide
    • Handy Cheat Sheet