To verify that during the implementation of parent process event dispatching the risk for regressions is low we need to run a small set of webdriver tests in CI: * Use a second configuration for wdspec jobs in Taskcluster with the “remote.events.parent.enabled” preference set to true * Run these tests only for debug, non-headless, and Fission builds across all supported platforms (we may have to initially exclude Android if needed) * Make sure to set a new property in the `runinfo` struct so that test failures can be easily classified in the manifest files.
Bug 1904671 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
To verify that during the implementation of parent process event dispatching the risk for regressions is low we need to run a small set of webdriver tests in CI: * Allow to enable and disable the feature by creating a new hidden preference (“remote.events.parent.enabled”) which defaults to “false”. * Use a second configuration for wdspec jobs in Taskcluster with the “remote.events.parent.enabled” preference set to true * Run these tests only for debug, non-headless, and Fission builds across all supported platforms (we may have to initially exclude Android if needed) * Make sure to set a new property in the `runinfo` struct so that test failures can be easily classified in the manifest files.