Bug 1940039 - Add documentation for recording the desktop during testing, including on try and on macOS DONTBUILD

Differential Revision: https://phabricator.services.mozilla.com/D233242
This commit is contained in:
Paul Adenot
2025-01-06 10:38:31 +00:00
parent 2fb0712fb4
commit 93023a39b2
2 changed files with 15 additions and 4 deletions

View File

@@ -251,14 +251,16 @@ Need to get more data out of your tests?
---------------------------------------- ----------------------------------------
Most test jobs now expose an environment variable named Most test jobs now expose an environment variable named
``$MOZ_UPLOAD_DIR``. If this variable is set during automated test runs, ``MOZ_UPLOAD_DIR``. If this variable is set during automated test runs,
you can drop additional files into this directory, and they will be you can drop additional files into this directory, and they will be
uploaded to a web server when the test finishes. The URLs to retrieve uploaded to a web server when the test finishes. The URLs to retrieve
the files will be output in the test log. the files will be output in the test log.
Passing ``$MOZ_RECORD_TEST=1`` as an environment variable when running some Passing ``MOZ_RECORD_TEST=1`` as an environment variable when running some
tests (e.g. mochitests) on Linux platform will trigger a recording of the tests (e.g. mochitests) on Linux Desktop and macOS will trigger a recording of the
desktop with GNOME Screencast. desktop with GNOME Screencast. This works on try as well, in which case the video
file will be uploaded as an artifact and available in the
``Artifacts and Debugging Tools`` panel on Treeherder.
.. _Need_to_set_preferences_for_test-suites: .. _Need_to_set_preferences_for_test-suites:

View File

@@ -28,6 +28,15 @@ try:
./mach try fuzzy --env MOZ_LOG=cubeb:4 ./mach try fuzzy --env MOZ_LOG=cubeb:4
On macOS and Linux Desktop, it is also possible to get a screen recording of the test run:
.. code-block:: shell
./mach try fuzzy --env MOZ_RECORD_TEST=1
The screen recording will be in the ``Artifacts and Debugging Tools`` section on Treeherder.
Resolving "<Try build> is damaged and can't be opened" error Resolving "<Try build> is damaged and can't be opened" error
------------------------------------------------------------ ------------------------------------------------------------