|
|
| (18 intermediate revisions by 5 users not shown) |
| Line 1: |
Line 1: |
| Some ideas about how to train new QA Engineers...
| | This page is no longer maintained. |
| | |
| (see also: [http://hgwdev.cse.ucsc.edu/qa/newQaHire.html Getting Started])
| |
| [[Category:Browser QA]]
| |
| | |
| == 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
| |
| # hgcentral
| |
| # pushQ
| |
| # QAing a "normal" track (using the [http://hgwdev.cse.ucsc.edu/qa/test-protocols/checklist.html checklist], perhaps)
| |
Latest revision as of 19:25, 10 March 2011
This page is no longer maintained.
