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/rm36029.docent.yaml src/hg/utils/docent/tests/regress/rm36029.docent.yaml
new file mode 100644
index 00000000000..5168f46a3e8
--- /dev/null
+++ src/hg/utils/docent/tests/regress/rm36029.docent.yaml
@@ -0,0 +1,41 @@
+# #36029 -- with several phyloP tracks on and MAF hidden, turning a MAF to full did not
+# display it. The controls showed it as full; the row was not drawn. A cart reset cleared
+# it, and it came back later.
+#
+# The ticket's session is on the RR (/s/Markd/maf-display-bug-36029) and so cannot be
+# loaded from genome-test, and the state it holds is three phyloP tracks, which is a step
+# to build.
+#
+# Track names on hg38: the conservation containers are cons100way (UCSC 100 Vertebrates),
+# cons241way (Zoonomia 241 Placent) and cons470way (Hiller Lab 470 Mammals). Each has a
+# phyloP view and an alignment view. The 241-way MAF the reporter could not display is
+# cactus241wayBM, under cons241wayViewalign.
+#
+# Asking for a phyloP view turns the whole composite on, alignment view included: a first
+# version of this test asserted the MAF was absent after naming only the phyloP views and
+# found multiz100way, cactus241wayBM and multiz470way all drawn. So the alignment views
+# have to be hidden by name to reach the state the report started from. That is the same
+# shape as the views test in the suite next door, where a hideKids has to be aimed at the
+# view that holds the subtrack rather than at the composite.
+target: genome-test
+db: hg38
+position: chr7:155799529-155812871
+reset: true
+fast: true
+steps:
+  - go: chr7:155799529-155812871
+  - hide: all
+
+  # Three phyloP tracks on, all three alignment views off: the state the report began in.
+  - track:
+      cons100wayViewphyloP: full
+      cons241wayViewphyloP: full
+      cons470wayViewphyloP: full
+      cons100wayViewalign: hide
+      cons241wayViewalign: hide
+      cons470wayViewalign: hide
+  - expect: {noRows: [cactus241wayBM, multiz100way, multiz470way], noText: "Warning/Error"}
+
+  # Now ask for the 241-way MAF. This is the step that did nothing.
+  - track: {cactus241wayBM: full}
+  - expect: {rows: [cactus241wayBM], noText: "Warning/Error"}