e497eccfb431be6af38d22c5bc2bb0e745c89b2d
braney
  Sat Sep 5 09:22:17 2026 -0700
docent: eight more regression scripts, one per fixed bug

rm35580  "Show <alt> placed on its chromosome" errored on the window
rm36061  DECIPHER SNVs details missing after a quickLift
rm36335  a quickLifted GIAB item click printed a garbled "can't port"
rm36340  a search-result click carried the source coordinate
rm37491  hgConvert named subtracks the user never showed as not liftable
rm37562  a stale lastPosition banner on the lifted search-results page
rm37615  a quickLifted bigBed tooltip reported pre-lift coordinates
rm37785  a squishyPack track stole a neighbouring track's center label

Each asserts the behavior its ticket says is correct, on genome-test, and names
in noText:/noUrl: the exact string the buggy build produced rather than a generic
"Error". Where the last page has no track image the noText: is paired with a
positive text: or url: check, because a bare noText: passes just as happily on a
blank page or an early error.

Four things found writing these, all of them recorded in the scripts:

A ticket's stated position and its stated item can disagree. #36061 says to go to
chr7:156,982,676-156,996,015 and click item 517898; that item is at
chr7:155,803,191, and decipherSnvs draws nothing at all in the ticket's window.

hideKids cannot express "the user deselected this subtrack". It writes a
<track>=hide cart variable, and isSubtrackVisible() (hg/lib/trackHub.c) begins
with overrideComposite = (NULL != cartOptionalString(cart, tdb->track)) and then
forces enabled = TRUE, so the sibling counts as visible to hgConvert and lands
back in the "failed to lift" warning. A first rm37491 failed on exactly that and
looked like the bug being back. A deselected subtrack is <track>_sel=0 with no
visibility variable, which is what hgTrackUi's checkbox writes and what the goto:
in that script sets.

#37615's fix is not the one the plan for this suite described. The first commit
appended a note saying the coordinates came from the source assembly; the second
replaced it with the real fix, which puts the TARGET coordinates in the tooltip.
A test for the note would fail.

decipherSnvs (SNVs) and decipher (CNVs) are two different members of the
superTrack decipherContainer, and the row that turns up when the SNVs track draws
nothing is the CNVs one, which reads like the same track under a shorter id.

refs #38252

diff --git src/hg/utils/docent/tests/regress/rm37615.docent.yaml src/hg/utils/docent/tests/regress/rm37615.docent.yaml
new file mode 100644
index 00000000000..3c4e1831a9c
--- /dev/null
+++ src/hg/utils/docent/tests/regress/rm37615.docent.yaml
@@ -0,0 +1,45 @@
+# #37615 -- a quickLifted bigBed tooltip reported pre-lift coordinates.
+#
+# Under quickLift the bedRow used for mouseOver substitution is loaded from the SOURCE
+# assembly's interval, so $chrom/${chromStart}/${chromEnd} printed the hg38 position while
+# the position bar showed the lifted one. Two commits: 05c41aa8b79 first appended a note
+# saying the coordinates came from the source assembly, then 98572a57d65 replaced that with
+# the real fix -- overwrite those three fields with the lifted bed's target coordinates
+# before substituting, so the tooltip matches where the item is drawn.
+#
+# So the behavior to assert is the SECOND one. The plan for this suite still said to look
+# for the disclaimer note; that note is gone from the tree and a test for it would fail.
+#
+# The track is gnomAD v3.1.1, the same one rm37805 uses natively, because its mouseOver
+# pattern is exactly the coordinate substitution this bug was about:
+#
+#     <b>Position</b>: $chrom:${chromStart}-${chromEnd} ($ref/$alt)
+#
+# and the same window and variant are reachable, which makes the two scripts easy to read
+# together. gnomadVariants is a superTrack, so hideKids keeps its siblings off.
+target: genome-test
+db: hg38
+position: chr17:43091000-43092000
+reset: true
+fast: true
+steps:
+  - go: chr17:43091000-43092000
+  - hide: all
+  - track: {gnomadVariants: hideKids, gnomadGenomesVariantsV3_1_1: pack}
+  - expect: {rows: [gnomadGenomesVariantsV3_1_1], noText: "Warning/Error"}
+
+  - convert: {to: hs1, quicklift: true}
+  - open: lift
+  - expect: {rows: [gnomadGenomesVariantsV3_1_1], noText: "Warning/Error"}
+
+  - mouseover: {track: gnomadGenomesVariantsV3_1_1, title: "rs80357218"}
+
+  # Both halves, and both numbers were measured on the lifted view rather than worked out.
+  # rs80357218 is at chr17:43,091,449-43,091,450 on hg38 and lifts to chr17:43,950,032 on
+  # hs1, so the fixed tooltip reads the second and the buggy one read the first. Naming the
+  # source coordinate in noText: is what makes this test about the bug: a tip: check alone
+  # would also pass if the tooltip stopped substituting coordinates at all.
+  - expect:
+      tip: "chr17:43950032-43950033 (T/G)"
+      noText: "43091449"
+