Closed Bug 560743 Opened 14 years ago Closed 14 years ago

expose mozrunner's -a option in cfx, so developers can easily test their generated XPIs

Categories

(Add-on SDK Graveyard :: General, defect)

Product:
Add-on SDK Graveyard
Component:
General
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: dietrich, Unassigned)

Details

we should add support for the -a parameter to cfx, basically doing just what mozrunner does but allowing users to use a single tool, instead of having to kick them over to mozrunner.

usage would be something like:

cfx run -a /path/to/my.xpi

which would load an instance of the default application, with the specified xpi installed.

mozrunner supports this, so the change is basically passing the -a parameter on to mozrunner instead of doing the usual stuff |run| does.
Summary: expose mozrunners -a option in cfx, so developers can easily test their generated XPIs → expose mozrunner's -a option in cfx, so developers can easily test their generated XPIs
the typical/ideal workflow uses packageless install for testing, so this shouldn't be necessary.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product.

To filter bugmail related to this change, filter on the word "looptid".
Component: Jetpack SDK → General
Product: Mozilla Labs → Add-on SDK
QA Contact: jetpack-sdk → general
You need to log in before you can comment on or make changes to this bug.