mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-18 15:55:36 +00:00
ee6633da5c
For static components, I don't intend to allow removing or replacing CID entries, only contract ID entries. And I would generally prefer, when restoring overrides of those classes, to not create a new dynamic factory entry for the contract ID. We already have the ability to mock components without either of those issues, but registering a new CID entry for the mock (without unregistering the original), and then restoring the original by calling `registerFactory` with a null factory object. This patch updates our existing mocks to behave that way, and paves the way for the rest of the patches. Differential Revision: https://phabricator.services.mozilla.com/D15031 --HG-- extra : rebase_source : 449f37ae8a3cc970e5f864d10e43e88d9e7e4bf6 extra : source : bedaa9c437ad30ea88bdc0e8fc83f4a2e980812e |
||
---|---|---|
.. | ||
example | ||
moz-http2 | ||
node-http2 | ||
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