aboutsummaryrefslogtreecommitdiff
path: root/scripts/testing/tests/test_config_applied.py
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-07-16 15:56:54 -0500
committerCraig Jennings <c@cjennings.net>2026-07-16 15:56:54 -0500
commit4608084db013c631ea16694cdc1555c20413ae5b (patch)
treebf6eb450bb0ed577d7b6c3f6c390dba6d7033bd0 /scripts/testing/tests/test_config_applied.py
parent722e9f9da69f00b87d99eda0183b0ef333c8744d (diff)
downloadarchsetup-4608084db013c631ea16694cdc1555c20413ae5b.tar.gz
archsetup-4608084db013c631ea16694cdc1555c20413ae5b.zip
fix(test): stop a failing screen-family check orphaning its browser
probe-fams.mjs had no try/finally, so a throw skipped chrome.kill() and left the headless browser alive on its port. The next run connected to that survivor and reported results from a stale page: old widgets.js, chips already clicked. It cost me a debug loop today, insisting a card's default ink was green and another's chips were missing, neither of which was true of the page on disk. A probe that answers from the previous run is worse than one that crashes. Its two siblings already had the guard.
Diffstat (limited to 'scripts/testing/tests/test_config_applied.py')
0 files changed, 0 insertions, 0 deletions