зеркало из https://github.com/mozilla/gecko-dev.git
f1fecc26b0
ensuring moz.build files have BUG_COMPONENTS for all files in the testing/ subdirectory is a win. There are a lot of older files and some files used in many harnesses. If the files are primarily used for mochitest, they are associated with the testing::mochitest component, otherwise I chose the testing::general component. There is an exception web-platform-tests, these have many test files that need to be matched to proper components. MozReview-Commit-ID: IIv9W2kEqeN |
||
---|---|---|
.. | ||
example | ||
moz-http2 | ||
node-http2 | ||
README | ||
dbg-actors.js | ||
head.js | ||
mach_commands.py | ||
mach_test_package_commands.py | ||
moz.build | ||
python.ini | ||
remotexpcshelltests.py | ||
runxpcshelltests.py | ||
selftest.py | ||
xpcshell.eslintrc.js | ||
xpcshellcommandline.py |
README
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