Training new Browser Staff: Difference between revisions
From genomewiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 32: | Line 32: | ||
# pushQ | # pushQ | ||
# QAing a "normal" track (using the [http://hgwdev.cse.ucsc.edu/qa/test-protocols/checklist.html checklist], perhaps) | # QAing a "normal" track (using the [http://hgwdev.cse.ucsc.edu/qa/test-protocols/checklist.html checklist], perhaps) | ||
# static docs | |||
# makefiles | |||
# /usr/local/apache vs. the cvs tree | |||
# hgcentral | # hgcentral | ||
Revision as of 23:56, 11 February 2010
Some ideas about how to train new QA Engineers...
(see also: Getting Started)
Logistics
- get a computer
- get a login
- email for UCSC and SOE
- key card
- copy .tcshrc or .bashrc from one of us
- check out a copy of the kent source tree
- build your own sandbox
Tools
- vi (vimtutorial) -- or other editor
- mysql
- CVS (or git, if we get it)
Browser
- Open Helix tutorials
- ASHG hands on tutorial
Data
- Jorge's data flow PowerPoint presentation
Training person-to-person (in rough chronological order)
- machine layout
- data flow
- trackDb.ra and trackDb table
- make docs
- pushQ
- QAing a "normal" track (using the checklist, perhaps)
- static docs
- makefiles
- /usr/local/apache vs. the cvs tree
- hgcentral
