QA Home Page: Difference between revisions

From Genecats
Jump to navigationJump to search
(→‎Tools: added wiki cheat sheet link)
(→‎CGI Build Process & Testing: added browser testing guidelines)
Line 21: Line 21:
* 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]].
* 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]].
* 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.
* If you don't have access to a Windows machine with Internet Explorer, there is a [[Windows_testing_machine | machine]] you can log into.



Revision as of 20:41, 30 March 2011

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

QAing tracks/assemblies

Mailing List Maven

  • Mailing list schedule can be found on the QA group calendar (Note: where it says Calendar:, you will need to change the drop down from "Main" to "QA" to view.)
  • 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.cse.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