Open Bug 1299441 Opened 8 years ago Updated 1 year ago

Marionette should setup test environment based on mozrunner.utils.test_environment()

Categories

(Testing :: Marionette Client and Harness, defect, P3)

defect

Tracking

(Not tracked)

People

(Reporter: whimboo, Unassigned)

References

()

Details

Right now Marionette sets up different environment variables on its own. It means that lots others we usually make use of in other test harnesses are missing. One example are variables for ASAN builds.

What we might want to do without having to add all this code again, is to call test_environment() from mozrunner.utils:

https://searchfox.org/mozilla-central/rev/049f3e8d328c4b6bac9bf4b27309541a2e913686/testing/mozbase/mozrunner/mozrunner/utils.py#90

We should check how this works for tests as run in-tree, via test-packages, and for other consumers.

One issue might become the default value for MOZ_DISABLE_NONLOCAL_CONNECTIONS, which we would have to override for now.
Blocks: 1272255
Blocks: 1299383
Priority: -- → P5
No longer blocks: 1272255
Priority: P5 → P3
Whiteboard: [webdriver:triage]

Eventually we should make use of the environment in the Marionette harness so that we don't have to set the required environment variables in different places like mach and mozharness. Previously we weren't able to because the harness was released on PyPI and in use by folks outside of our tree. But this has been changed since we no longer release to PyPI.

One thing to note is that the firefox-ui-functional remote tests would still need the capability to opt-out or override certain environment variables like the MOZ_DISABLE_NONLOCAL_CONNECTIONS one.

For now this is not a priority.

Severity: normal → S3
Product: Testing → Remote Protocol
Component: Marionette → Marionette Client and Harness
Product: Remote Protocol → Testing
You need to log in before you can comment on or make changes to this bug.