TalosError: Missing required environment variable MOZILLA_OFFICIAL when running integration tests
0 reputation · 01 Aug 2026, 11:17 UTC
When running Talos integration tests without production credentials, the goal is to execute the test suite locally while avoiding any dependence on external API keys for result upload.
The harness currently requires the MOZILLA_OFFICIAL environment variable; if it is unset, Talos fails with the error TalosError: Missing required environment variable MOZILLA_OFFICIAL and stops execution.
If MOZILLA_OFFICIAL is set but MOZ_API_KEY is missing, Talos logs a warning WARNING: No MOZ_API_KEY set; results will not be uploaded. and continues the test run.
A TODO comment in the source indicates uncertainty about whether the harness should automatically generate a temporary API key for local executions, leading to inconsistent behavior across branches.
Should Talos auto‑generate a temporary API key for local runs? If so, how should the key be scoped, stored, and cleaned up after the test? What impact would this have on result verification and downstream processes that expect uploaded data?
talos