Closed
Bug 840007
Opened 12 years ago
Closed 12 years ago
Marionette needs a Mach/make target on desktop builds
Categories
(Remote Protocol :: Marionette, defect)
Remote Protocol
Marionette
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 799308
People
(Reporter: bholley, Unassigned)
Details
Now that Marionette is running on tinderbox for desktop Firefox builds, developers need a simple way to reproduce oranges on their local machine. The current setup is pretty inscrutable, and made worse by the fact that most of the documentation for Marionette is about B2G.
Ideally, we'd have some sort of "make marionette" target that could run in the object directory, with optional environmental variables to select a subset of tests and launch a debugger.
A mach target would be good too. :-)
Comment 1•12 years ago
|
||
Fwiw, I don't think we should add make targets at this point.
Reporter | ||
Comment 2•12 years ago
|
||
(In reply to :Ms2ger from comment #1)
> Fwiw, I don't think we should add make targets at this point.
I don't particularly care whether it's a make or a mach target. I just want to be able to run them easily.
Updated•12 years ago
|
Summary: Marionette needs a make target on desktop builds → Marionette needs a Mach/make target on desktop builds
Comment 3•12 years ago
|
||
testsuite-targets.mk is not used by automation and the UX of mach is superior to make. So, my vote is to implement a mach command and omit a make target. If you really want a make target, you could have it call out to mach (i.e do the heavy lifting in Python instead of make).
Anyway, we already have bug 799308 on file for a mach command. And, there is even a PoC patch! The mach API has likely changed since that patch was authored, so watch out!
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Updated•2 years ago
|
Product: Testing → Remote Protocol
You need to log in
before you can comment on or make changes to this bug.
Description
•