mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-23 10:15:41 +00:00
573782c2eb
It turns out bug 1489100 regressed the ability to specify test paths for most suites by naively assuming that mozharness uses suite names that look like: <flavor>-<subsuite> In reality, there is no consistency to how suite names are generated. This test does a few things: 1) Patches the moztest.TestResolver to return a list of all possible suites/subsuites (assuming the lists in moztest.resolve are up to date). 2) Finds all the suites defined in the mozharness configs (e.g linux_unittest.py), and uses these are parametrized inputs. 3) Checks that for each test suite, DesktopUnittest._get_mozharness_test_paths() returns something. I've marked all of the test suites that currently fail as expected. This way I have a good sense of what needs to be fixed, and can validate my changes as I move through the list. Differential Revision: https://phabricator.services.mozilla.com/D25014 --HG-- extra : moz-landing-system : lando
13 lines
249 B
INI
13 lines
249 B
INI
[DEFAULT]
|
|
subsuite=try
|
|
skip-if = python == 3
|
|
|
|
[test_again.py]
|
|
[test_chooser.py]
|
|
requirements = tools/tryselect/selectors/chooser/requirements.txt
|
|
[test_fuzzy.py]
|
|
[test_mozharness_integration.py]
|
|
[test_presets.py]
|
|
[test_tasks.py]
|
|
[test_templates.py]
|