this might be a factor of the extensions we are installing, but throwing an exception is not a clean way to handle this. There are two test cases which produce this exception: test_428341.js test_299716.js The exception we get is: Exception installing add-on test_bug428341_2 [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIStringBundle.GetStringFromName]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: file:///home/mozilla/mozilla/mobile_debug/xulrunner/dist/bin/components/nsExtensionManager.js :: anonymous :: line 267" data: no]

moving to toolkit/addonmanager as this is specific to a couple tests: http://mxr.mozilla.org/mozilla-central/source/toolkit/mozapps/extensions/test/unit/test_bug299716.js http://mxr.mozilla.org/mozilla-central/source/toolkit/mozapps/extensions/test/unit/test_bug428341.js

The problem here is that at the point you are running the tests (presumably a plain XULRunner build without fennec or anything?) there is no application branding defined. As it stands some of the tests will likely only pass if the surrounding application is present in some way, not sure whether that needs to change or not though.

This is fixed in the new extension manager

These tests do no exist anymore in mozilla-central. Just marking as verified fixed based on the prior check-in.