1221025 - Create a special flavor of mochitests for tests that don't expect to run in content processes

Status: NEW

(Testing :: Mochitest, defect)

Description

[Kan-Ru Chen [:kanru] (UTC+9)]

If the end goal is to run tests in e10s mode only on automation, maybe we could create a mochitest flavor that runs test in parent process. Some tests that don't expect to run in content processes, for example they create new OOP iframes, should be put into this mochitest flavor.

The other option is to rewrite these tests in browser-chrome test but that would prevent them to be run on b2g.

Comment 1

[Andrew McCreight (out of office until 8/21) [:mccr8]]

This sounds like a good idea to me.

Comment 2

[Andrew McCreight (out of office until 8/21) [:mccr8]]

There's no huge hurry on this, but we'd want to do this before we disable non-e10s Mochitests.

Comment 3

[Blake Kaplan (:mrbkap) (inactive)]

Hey Jonathan, what are the steps to make this happen?

Comment 4

[Jonathan Griffin (:jgriffin)]

The first step is to clarify scope.

Is this to replace the existing mochitest-chrome suite for e10s, or to handle special cases of mochitest-plain?

Comment 5

[Blake Kaplan (:mrbkap) (inactive)]

This is to handle special cases of mochitest-plain. I suspect that we'll end up with a much smaller (hopefully only one chunk if my eyeballing is correct) set of tests that we'll have to continue running.

Comment 6

[Jonathan Griffin (:jgriffin)]

Can anyone describe how we would run these tests in the parent process? They mostly are written in HTML/js; how can we load those without winding up in a content process?

Comment 7

[Andrew McCreight (out of office until 8/21) [:mccr8]]

(In reply to Jonathan Griffin (:jgriffin) from comment #6)
> Can anyone describe how we would run these tests in the parent process? They
> mostly are written in HTML/js; how can we load those without winding up in a
> content process?

They just need to be run in exactly the same way as non-e10s Mochitest-plain tests are run now.

Comment 8

[Blake Kaplan (:mrbkap) (inactive)]

The new test suite would be the current mochitest-plain, but not running tests that are not skip-if=e10s. We could mark these tests in other ways in their manifest files if that would make it easier, too.

Comment 9

[Jonathan Griffin (:jgriffin)]

(In reply to Blake Kaplan (:mrbkap) (please use needinfo!) from comment #8)
> The new test suite would be the current mochitest-plain, but not running
> tests that are not skip-if=e10s. We could mark these tests in other ways in
> their manifest files if that would make it easier, too.

Yes, I think what we'll do is to tag these tests in the manifest and then enable them as a separate suite. I don't think we need to do this until we're getting close to the point where we intend to turn the non-e10s suites off.