Update external docs

Author: garrett

external/bots/README.md

@@ -32,8 +32,8 @@ For managing these images:
 
  - `image-download`: Download selected or all test images
  - `image-create`: Create test machine images from scratch (usually through
-   virt-install or downloading a cloud image), with common build and test
-   dependencies for Cockpit projects preinstalled
+   downloading a cloud image), with common build and test dependencies for
+   Cockpit projects preinstalled
  - `image-upload`: Upload a locally built test image to the official image servers
 
 For running and debugging the images:

external/source/HACKING.md

@@ -152,10 +152,26 @@ which will output a URL to connect to with a browser, such as
 <http://localhost:8765/qunit/base1/test-dbus.html>. Adjust the path for different
 tests and inspect the results there.
 
-You can also run individual tests by specifying the `TESTS` environment
-variable:
+QUnit tests are run as part of a pytest test called `test_browser`.  You can
+run individual tests via `pytest -k`, like so:
 
-    make check TESTS=qunit/base1/test-chan.html
+    pytest -k test-fsinfo.html
+
+You can see JavaScript code coverage information for QUnit tests.  For a
+summary table:
+
+    pytest -k test_browser --js-cov
+
+And for detailed output on uncovered sections in a specific file, something
+like:
+
+    pytest -k test-fsinfo.html --js-cov-files='*/fsinfo.ts'
+
+Coverage information is gathered into the pytest tmpdir, regardless of which
+coverage-related commandline flags are given, so it's also possible to drill
+down after the fact — without re-running tests — using something like:
+
+    test/common/js_coverage.py -m '*/fsinfo.ts' /tmp/pytest-of-*/pytest-current/js-coverage/*
 
 There are also static code and syntax checks which you should run often:
 

external/source/test/README.md

@@ -172,21 +172,15 @@ You can set these environment variables to configure the test suite:
                   "centos-10"
                   "debian-stable"
                   "debian-testing"
-                  "fedora-39"
                   "fedora-40"
                   "fedora-coreos"
                   "rhel-9-4"
-                  "rhel4edge",
                   "ubuntu-2204"
                   "ubuntu-stable"
-               "fedora-39" is the default (TEST_OS_DEFAULT in bots/lib/constants.py)
+               "fedora-40" is the default (TEST_OS_DEFAULT in bots/lib/constants.py)
 
     TEST_JOBS  How many tests to run in parallel.  The default is 1.
 
-    TEST_CDP_PORT  Attach to an actually running browser that is compatible with
-                   the Chrome Debug Protocol, on the given port. Don't use this
-                   with parallel tests.
-
     TEST_BROWSER  What browser should be used for testing. Currently supported values:
                      "chromium"
                      "firefox"