It would really help to have all the remoted test harness utilities share the same core set of remote options. To do this, we'd simply need to factor out the remoteoptions class, and allow each of the test harnesses to add any specialized things they need to the options array. But this way, we could ensure that all the options classes are maintained in one place and the set of command line parameters across the different tools are kept consistent. We should look into doing this for the non-remote case as well because there too, many options are shared. Perhaps one big options class to rule them all? Spun off from review comments in bug 573263 (https://bugzilla.mozilla.org/show_bug.cgi?id=573263#c3)
Component: New Frameworks → General
Product: Testing → Testing
There's been lots of refactoring around this / happy with the way it is now.
Assignee: nobody → gbrown
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.