Skip to content

Bug 44130: Run python tests in CI

brizentalrequested to merge
brizental/tor-browser:44130-python-test-ci into tor-browser-140.2.0esr-15.0-1

Merge Info

Issues

Resolves

Merging

Target Branches

  • tor-browser - !fixups to tor-browser-specific commits, new features, security backports
  • base-browser and mullvad-browser - !fixups to base-browser-specific commits, new features to be shared with mullvad-browser, and security backports
    • ⚠️ IMPORTANT: Please list the base-browser-specific commits which need to be cherry-picked to the base-browser and mullvad-browser branches here

Target Channels

  • Alpha: esr140-15.0
  • Stable: esr128-14.5
  • Legacy: esr115-13.5

Backporting

Timeline

  • No Backport (preferred): patchset for the next major stable
  • Immediate: patchset needed as soon as possible (fixes CVEs, 0-days, etc)
  • Next Minor Stable Release: patchset that needs to be verified in nightly before backport
  • Eventually: patchset that needs to be verified in alpha before backport

Review

Change Description

Makes the base-browser/tools python test runnable with ./mach python-test and adds CI job to run python tests.

Will only run them in merge requests that change Python test files, but will always run them on merge.

Note that I had to rename the tools/base-browser folder to tools/base_browser because python was not happy with a module that has a - in the name.

How Tested

If CI passes we are good, but I have also tested this locally.

Related to #44130 (closed)

Edited by brizental

Merge request reports