443d7aad57553f2606be41a934cb4dab46019e09 braney Fri Sep 4 12:10:00 2026 -0700 docent: first eleven regression tests, one per fixed bug, refs #38252 Ten assert the behavior their ticket says is correct; the eleventh is an xfail. All eleven pass against genome-test, 40s for the set. rm35333 bigBed schema vs trackDb type mismatch, no SEGFAULT rm35920 wrong bigBed type in a hub, no crash and no garbage item label rm36029 a MAF displays after several phyloP tracks are on rm36331 quickLift of the GENCODE Archive container, no "Unknown database" rm36514 a chromosome search after a quickLift hop rm36702 quickLift hg19 to hs1, no "Unknown database" rm36798 the two OMIM tracks survive a configure submit rm37388 hgc on a quickLifted hub item, no connect to the source assembly rm37520 lifted tracks survive a hop to another genome and back rm37906 Neandertal tracks draw data in a narrow window on hg18 rm36540 is the xfail, and it is worth reading. The ticket is Closed, but the symptom is present on genome.ucsc.edu (v502), hgwbeta (v503) and genome-test (v503), measured with the reporter's own hub URL as well as with our copy of it: genome= instead of db= for a hub-backed assembly still reaches a query against a chromInfo table that does not exist. There is no fixed behavior to assert, so it is pinned as an xfail and the run fails if it ever starts passing. Six of these build their own state rather than loading the session their ticket names, which is deliberate: a session on someone's account can be renamed or deleted, and hgTracks answers a missing session with a 200 and an early-error page that every noText: assertion passes on. Where a session is genuinely the cheapest way to a state (rm37388), the script also asserts noText: "Could not find session" so that a deleted session fails loudly instead of quietly. Four traps cost a run each and are written into the scripts that hit them, since the next twenty-nine will hit them too: a container never gets an img_data_ row (the rows carry its children's names); a leaf track with no features at the ticket's position has no row either, so a lifted view is better checked by its own quickLiftChain; `track:` sends a plain name and cannot turn on a track in an ATTACHED hub, whose cart variable carries the hub prefix; and asking for one view of a composite turns its sibling views on as well. diff --git src/hg/utils/docent/tests/regress/rm36514.docent.yaml src/hg/utils/docent/tests/regress/rm36514.docent.yaml new file mode 100644 index 00000000000..ebf52bff163 --- /dev/null +++ src/hg/utils/docent/tests/regress/rm36514.docent.yaml @@ -0,0 +1,31 @@ +# #36514 -- after a QuickLift from hg38 to hs1, typing a chromosome name into the +# position box returned an error instead of navigating. +# +# The ticket's steps are: reset, hg38, convert to hs1 with QuickLift, go to +# chr7:156982676-156996015, then enter "chr7" as a search query. +# +# goShow: is used rather than go: on purpose. go: navigates straight to a position; +# goShow: puts the term in the position box and lets the page submit it, which is the +# path the user took and the one the bug was on. +# Asserts on quickLiftChain, the chain track the lift itself adds. A data track is no +# good here: at the ticket's position (chr7:156,982,676-156,996,015) mane has no +# features, so its row is legitimately absent and the assertion would fail for a reason +# unconnected to the bug. The chain is always drawn in a lifted view, so it is the right +# way to say "we are on a drawn lifted page and not on an error page". +target: genome-test +db: hg38 +position: chr7:156982676-156996015 +reset: true +fast: true +steps: + - go: chr7:156982676-156996015 + - hide: all + - track: {mane: pack} + - convert: {to: hs1, quicklift: true} + - open: lift + - expect: {rows: [quickLiftChain], noText: "Warning/Error"} + + - goShow: chr7 + # A search that fails renders a perfectly good page carrying the message, so the row + # check is what proves we are on a drawn view and not on an error page. + - expect: {rows: [quickLiftChain], noText: "Warning/Error"}