mochitest and electrolysis

[jmaher]

Lately I have been working on getting the mochitest harness working
inside of fennec + electrolysis. This project is coming along well
and I am looking forward to landing it on mozilla-central in the near
future. For reference, here is the bug: https://bugzilla.mozilla.org/show_bug.cgi?id=567417

One of the requests for having this is so people can write new
mochitests that exercise IPC specific functionality. There are a few
concerns I have when thinking about running these new tests:
* How will we specify what code runs in chrome and content processes?
* Will these be chrome only tests that inject bits into content?
* Since mochitest relies on the messageManager channel, is there
danger of these tests disabling or crashing this channel?

I would like to see some test examples and conditions if they exist.
This would allow me to make sure my work on the mochitest harness will
work for the new tests.

[Benjamin Smedberg]

Post by jmaher
Lately I have been working on getting the mochitest harness working
inside of fennec + electrolysis. This project is coming along well
and I am looking forward to landing it on mozilla-central in the near
future. For reference, here is the bug: https://bugzilla.mozilla.org/show_bug.cgi?id=567417
One of the requests for having this is so people can write new
mochitests that exercise IPC specific functionality. There are a few
* How will we specify what code runs in chrome and content processes?

mochitest-plain (which is what you're currently working on) are just
content. We basically want to make sure that various pieces of content
functionality work correctly.

Post by jmaher
* Since mochitest relies on the messageManager channel, is there
danger of these tests disabling or crashing this channel?

We will in the future want to have tests which intentionally crash the
content process so that we can test recovery behavior, but that is not
currently the primary focus.

If there are tests which need to run arbitrary testing code in both the
chrome and content processes, they should be chrome tests, and the test
itself can set up a <browser remote="true"> and run whatever specialized
code it wants. I think that should work right now. We may want to add some
JS library support for that kind of thing in the future, but I don't know
exactly what it would do yet.

--BDS