On Wed, Nov 7, 2012 at 12:00 PM, Honza Bambas <hbam...@mozilla.com> wrote:
> Hi all. I'd like to ask for help. > > tl;dr: a new JS component needs to be accessible by xpcshell and > mochitest, how to do that? > > > Details: > I'm introducing a new JS implemented component that is used to control > ssltunnel (a part of our testing infrastructure). I want test harnesses > use it. > > Here is a patch that introduces the component: https://hg.mozilla.org/try/ > **rev/1dad84dbae81 <https://hg.mozilla.org/try/rev/1dad84dbae81>, works > locally of course... > > This is the complete try run: https://tbpl.mozilla.org/?** > tree=Try&rev=352b6716d008<https://tbpl.mozilla.org/?tree=Try&rev=352b6716d008>, > it fails with: > > "Cc['@mozilla.org/ssltunnel-**control;1<http://mozilla.org/ssltunnel-control;1>'] > is undefined." > > > Benjamin Smedberg told me I need to _ship the component as part of the > test package and getting the test framework to register it somehow_ and > that it is complicated. > > How will I do that? E.g. httpd.js is also a component, but it is not > actually instantiated by test harness through xpcom but just by calling new > on the class or run directly in xpcshell. > > For info, ssltunnel and my new component doesn't build when testing is > disabled (no --enable-testing in mozconfig). That could make few things > easier. > > Thanks for help, > -hb- > ______________________________**_________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/**listinfo/dev-platform<https://lists.mozilla.org/listinfo/dev-platform> > My semi-educated guess is that the easiest way to do this will be to package the testing component as an extension and install the extension in the testing profile. - Kyle _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
