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/rm37388.docent.yaml src/hg/utils/docent/tests/regress/rm37388.docent.yaml
new file mode 100644
index 00000000000..c9e573bf553
--- /dev/null
+++ src/hg/utils/docent/tests/regress/rm37388.docent.yaml
@@ -0,0 +1,30 @@
+# #37388 -- clicking an item in a QuickLifted hub track sent hgc looking for a MySQL
+# database named after the source assembly:
+#
+#     Couldn't set connection database to GCA_018466835.2
+#
+# The session is kept for this one. It is braney/crash1 on genome-test, and it pins a
+# state that is genuinely awkward to build: hg38 at chrM:577-16569 with a quickLift hub
+# active, its chain from GCA_018466835.2, and an xenoRefGene track from that hub. Building
+# that in steps would mean attaching a hub and running a convert whose target is a
+# GenArk assembly, which is more moving parts than the bug needs.
+#
+# click: {track:, item:} follows the item's own map-box link, which is how hgc is reached.
+# A raw click on the image is swallowed by hgTracks' drag-select handler.
+target: genome-test
+db: hg38
+reset: true
+fast: true
+steps:
+  - loadSession: {user: braney, name: crash1}
+
+  # The guard. A session that has been renamed or deleted is not an error: hgTracks
+  # answers 200 with an early-error page carrying no track image, and every noText check
+  # on that page passes. Without this line a deleted session turns this test green.
+  - expect: {noText: "Could not find session"}
+
+  - click: {track: xenoRefGene, item: "NM_126741.2"}
+
+  # hgc has no track image, so there is no row to assert on here: the whole check is that
+  # the page is the details page and not the early-error page the bug produced.
+  - expect: {noText: "Couldn't set connection database"}