Closed Bug 846143 Opened 7 years ago Closed 3 years ago

Create harness for running native-code tests in content processes

Categories

(Core :: General, defect)

x86_64
Linux
defect
Not set

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: cjones, Unassigned)

References

Details

We've long debated how to integrate native-code tests into builds, since libxul makes it a massive PITA.  I have a working solution in hand for IPDL native-code tests [1] that I'm always happy to fall back on.  Don't want to derail on those details here though.

What we need to use this harness for is poking at process-isolation bugs.  For example,
 - launch content process
 - invoke native-code test in content process that tries to directly manipulate SMS through IPDL
 - ensure content process is killed off

There are lots of similar issues we want to test with this, for example ensuring that content processes that send garbage IPC data are killed off.  We can (and do! though not enough) use the native-code IPDL tests for general datatypes, but we can't test sending a garbage PBlobParams with those, for example.

[1] http://mxr.mozilla.org/mozilla-central/source/ipc/ipdl/test/cxx/Makefile.in
(And we would obviously not want to ship this code in production builds.)
Note that we have a first pass for Google Test C++ tests, bug 767231. The next step there is linking it into a separate libxul-test.so instead of just libxul.so, so we can enable it in tinderbox builds.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.