Sadly, the WebRTC gtest-based ones (e.g., media/webrtc/signaling/test) do.
On Fri, Oct 3, 2014 at 6:04 AM, Kyle Huey <m...@kylehuey.com> wrote: > On Fri, Oct 3, 2014 at 5:44 AM, Benjamin Smedberg <benja...@smedbergs.us> > wrote: > > > > On 10/3/2014 4:59 AM, Patrick Wang wrote: > >> > >> Hi, > >> > >> I am trying to write a C++ unit test for code that runs in child > >> process, but all c++ tests I found run in parent process. Is it possible > >> to write a c++ test case that runs in child process, or is there any > >> example in our code? > > > > > > Could you be more specific? We have the following possible harnesses: > > > > gtest - typically these tests are low-level C++ tests and often don't > > initialize XPCOM at all. Certainly they don't have the concept of > > chrome/content processes. > > xpcshell - typically test the API surface of a component written in JS or > > C++ > > > > Neither of these particularly care about chrome/content: if you're > actually > > testing a C++ component and not doing integration testing, is it possible > > that you don't need to care? > > > > --BDS > > > > _______________________________________________ > > dev-platform mailing list > > dev-platform@lists.mozilla.org > > https://lists.mozilla.org/listinfo/dev-platform > > More importantly, our C++ tests don't start up Gecko. > > - Kyle > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform