Search results

== Why use a demo browser? == ...ld this trackDb into alpha yet. Keeping these features static in your own sandbox is the simplest solution. However, that is not always practical as we all

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

...ount has a VM called browserboxBeta. It is the beta testing VM and used by QA. A developer can also copy the binaries from their own sandbox, e.g. if user braney wants to test braney's binaries on his gbib

* ('''QA'''): Find an error in the binaries, determine if it needs to be patched, an ...or (and get a second opinion on your fix from another developer). Let the QA person know that it is fixed.

...ers] and [http://genecats.cse.ucsc.edu/eng/index.html Getting Started for Browser Dev Engineers]) [[Category:Browser QA]]

[[Category:Browser QA]] [[Category:Browser QA New Assembly]]

...wn copies of the binaries and your own sandbox or hgwdev-user.soe.ucsc.edu browser? Here is a walkthrough:=== browser.style=/style/myusername.css

[[Category:Browser QA]][[Category:Browser Development]] ...of the html elements you will need to create or update pages on the Genome Browser website.

...is ambiguous term that refers to either an individual line in the browser or a composite track which is a collection of such sub-tracks. Often peopl ** User sandbox - http://hgwdev-*YOUR_USER_NAME_HERE*.soe.ucsc.edu/

* During the first week, any changes by QA or developers are added to the tree * During the 2nd week, just like in week1, any changes by QA or developers are added to the tree

::[[Assembly QA Part 1 DEV Steps | Assembly QA Part 1: DEV Steps]] ::[[Assembly QA Part 2 Track Steps | Assembly QA Part 2: Track Steps]]

Note: see the [[Old ENCODE QA]] page for the pre-bootcamp ENCODE QA process ...her tracks that wrangler currently has in "Reviewing" status (under active QA).

This is the checklist for QA to follow when releasing Genome Browser tracks. ...u/genecats/images/c/c1/Jairos_Into_to_QA_checklist.pdf Jairo's Into to the QA Release Process.]

...e). Larry says that many non-obvious bugs leave behind evidence in the web browser error log, so it can be very useful. # zoom in on an alignment and test "View details of parts of alignment within browser window" (DNA blat)