As part of the refactoring on bug 1313591 we want to separate out the Marionette unit tests from the product specific tests as located in browser, dom, layout, and toolkit. Therefore we should at least create one new job to cover the above components. Maybe even different ones. The details will have to be sorted out with peers and module owners. The same for Treeherder job names. Regarding Treeherder a separate group named Mn might be ideal, so all jobs would appear inside this group. At the same time we could also integrate the Marionette harness unit tests into that group. It could look something like: Mn(h, u, bc) Mn-e10s(u, bc) To allow that we will have to do the following: * Figure out how testcase data can be located close to the test * Update Mozharness to run Marionette test suites as separate jobs * Update Taskcluster and Buildbot definitions appropriately