[EMAIL PROTECTED] wrote: > I see an opportunity here to help the testing task. I am new to Mozilla > technologies but the XPCOM layer looks like a good place to stand and > reach down into other layers to test them.
XPCOM is a good way to define API interfaces and test them, but I don't think this means that *standalone* XPCOM will be useful for testing. Most of our component have interdependencies in implementation; many component require the networking stack to be available, for instance. Any gecko component that is localizable ends up with a dependency on the chrome registry, which has dependencies on the security system (CAPS). I think that we should test and treat "the toolkit" as a monolith, which includes XPCOM, networking, etc. For some thoughts on this, see http://benjamin.smedbergs.us/blog/2005-07-29/the-testing-matrix/ --BDS _______________________________________________ dev-tech-xpcom mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-xpcom
