Our unit tests generally assume that all the XPCOM cruft that we have exist. We run our usual test suite, including xpcshell tests, on B2G. Some of the XPCOM cruft is dead code except for unit tests on B2G.
Should be stop building unit test-only XPCOM components on B2G? For example, do we believe that compilers work well enough that if encoding converters test OK outside B2G via XPCOM testing and the Web API entry points to encoding converters are tested on B2G, we can believe that the encoding converters work OK on B2G even without testing them via XPCOM? -- Henri Sivonen hsivo...@hsivonen.fi https://hsivonen.fi/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
