mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-11-24 13:21:05 +00:00
dc33776dd5
Most (all?) mach xpcshell-test calls result in calling install_tests(None) while most mach test calls for the same test/directory result in calling install_tests() with a collection of test objects. Providing test objects allows install_tests() to optimize which tests are installed, but there have been several recent bugs that appear to be related to that optimization. Let's rely less on that optimization and make things consistent between test/xpcshell-test. (There's a parallel consideration for test vs mochitest.) Differential Revision: https://phabricator.services.mozilla.com/D70052 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| dns-packet | ||
| example | ||
| moz-http2 | ||
| node-http2 | ||
| node-ip | ||
| dbg-actors.js | ||
| head.js | ||
| mach_commands.py | ||
| mach_test_package_commands.py | ||
| moz.build | ||
| python.ini | ||
| README | ||
| remotexpcshelltests.py | ||
| runxpcshelltests.py | ||
| selftest.py | ||
| xpcshellcommandline.py | ||
Simple xpcshell-based test harness converted from netwerk/test/unit Some documentation at http://developer.mozilla.org/en/docs/Writing_xpcshell-based_unit_tests See also http://wiki.mozilla.org/SoftwareTesting:Tools:Simple_xpcshell_test_harness