Open Bug 1893223 Opened 10 days ago Updated 5 days ago

Some marionette manifests are not included by the master manifest

Categories

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

task

Tracking

(Not tracked)

People

(Reporter: gbrown, Unassigned)

References

Details

In bug 1892038 we noticed that some marionette tests could not be run in CI because they were not included in testing/marionette/harness/marionette_harness/tests/unit-tests.toml. It is not clear to me if all marionette manifests should be included there or not, so just noting here for someone to review and consider.

https://searchfox.org/mozilla-central/search?q=&path=marionette**manifest*.toml&case=true&regexp=false

Is this a correct assessment of the issue? It is surprising to learn that the file needs to be listed here. In other test types, listing it in the directory-specific toml file is enough for it to be picked up in CI.

I previously wondered about the test selection behavior (locally) at https://phabricator.services.mozilla.com/D196188#6507426

If it ultimately turns out that the test needs to be listed in unit-tests.toml, then that should be documents.

See Also: → 1892038

As we discussed we do not have the time to change the underlying packaging behavior for Marionette tests. As such we suggest that the unit-test.toml file gets updated so that it contains all the missing references to tests that are not run yet in CI. As suggested we should also document that and maybe this could directly be done in the same file.

Severity: -- → S3
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.