Seems to be the case even if I don't use `--start-at` or `--end-at`. STR (this just does some chrome mochitests since it's not the actual tests that we care about) 1. Open mozilla-central/toolkit/content/tests/widgets/chrome.ini, and note the order of the listed tests. In particular, notice that `test_contextmenu_nested.xhtml` is listed first. 2. Run the chrome mochitests but keep the window open afterwards, like this: ``` ./mach mochitest --flavor=chrome toolkit/content/tests/widgets/ --keep-open ``` 3. Note the tests as listed in the test runner UI ER: Ideally, the tests would run in the same order that they're in in the chrome.ini file AR: They're run in alphabetical order.
Bug 1756878 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Seems to be the case even if I don't use `--start-at` or `--end-at`. STR (this just does some chrome mochitests since it's not the actual tests that we care about) 1. Open mozilla-central/toolkit/content/tests/widgets/chrome.ini, and note the order of the listed tests. In particular, notice that `test_contextmenu_nested.xhtml` is listed first. 2. Run the chrome mochitests but keep the window open afterwards, like this: ``` ./mach mochitest --flavor=chrome toolkit/content/tests/widgets/ --keep-open ``` 3. Note the tests as listed in the test runner UI ER: Ideally, the tests would run in the same order that they're in in the chrome.ini file AR: They're run in alphabetical order. `test_contextmenu_menugroup.xhtml` is run first.