Training new Browser Staff: Difference between revisions

From genomewiki
Jump to navigationJump to search
No edit summary
Line 1: Line 1:
Some ideas about how to train new QA Engineers...
(see also: [http://hgwdev.cse.ucsc.edu/qa/newQaHire.html Getting Started for Browser QA Engineers] and [http://hgwdev.cse.ucsc.edu/eng/index.html| Getting Started for Browser Dev Engineers])
 
(see also: [http://hgwdev.cse.ucsc.edu/qa/newQaHire.html Getting Started])
[[Category:Browser QA]]
[[Category:Browser QA]]


Line 36: Line 34:
# make docs
# make docs
# pushQ
# pushQ
# QAing a "normal" track (using the [http://hgwdev.cse.ucsc.edu/qa/test-protocols/checklist.html checklist], perhaps)
# (for Q/A only) QAing a "normal" track (using the [http://hgwdev.cse.ucsc.edu/qa/test-protocols/checklist.html checklist], perhaps)
##joinerCheck
##joinerCheck
# static docs
# static docs

Revision as of 20:57, 6 April 2010

(see also: Getting Started for Browser QA Engineers and Getting Started for Browser Dev Engineers)

Logistics

  • get a computer
  • get a login
  • email for UCSC and SOE
  • key card
  • add your contact information to your .plan file
  • copy .tcshrc and .bashrc from one of us (both are needed to run scripts)
  • copy .hg.conf and .hg.conf.beta from someone, so you can run hgsql and scripts that use it.
  • set up ssh authentication among dev, beta and your linux box
  • check out a copy of the kent source tree
  • set up nightly cron to update kent source tree
  • build your own sandbox

Tools

Browser

  • Open Helix tutorials
  • ASHG hands-on tutorial

Data

Training person-to-person (in rough chronological order)

  1. machine layout
  2. data flow
  3. using cvs: day to day commands, and cvs reports/pair review process
  4. trackDb.ra and trackDb table
  5. make docs
  6. pushQ
  7. (for Q/A only) QAing a "normal" track (using the checklist, perhaps)
    1. joinerCheck
  8. static docs
  9. makefiles
  10. /usr/local/apache vs. the cvs tree
  11. hgcentral