$ npm install -g shield-study-cli
$ shield -h
Usage: shield [options] [command]
Commands:
run [options] <addonDir> [variation]
profile [options] <dir>
init [options] <name>
lint <dir>
Options:
-h, --help output usage information
-V, --version output the version number
Run with a branch at random
$ shield run ~/aStudyAddon/ some-branch-name --prefs some.prefs.json -- -v -b Aurora
Choose a branch, add some prefs
$ shield run ~/aStudyAddon/ some-branch-name
Add a firstrun time, and some extra prefs
$ shield run ~/aStudyAddon/ some-branch-name --firstrun 123214232 --prefs some.prefs.json -- -v -b Aurora
Add some arguments to passed to jpm.
$ shield run ~/aStudyAddon/ some-branch-name --prefs some.prefs.json -- -v -b Aurora
- '+' prefs are treated as 'addon' prefs
- all other prefs are passed through
- prefs can be called more than once
{
"+some.addon.pref": "abcded",
"browser.pref": 4
}
Make a new blank-ish profile, with some useful prefs.
$ shield profile some/path
Overwrite if needful.
$ shield profile --force some/path
Add some prefs
$ shield profile --prefs some.prefs --prefs some.prefs
These are useful base profiles for debugging runs, qa, jpm
, etc.
$ shield init -h
Usage: init [options] <name>
Options:
-h, --help output usage information
-f --force remove dir if exists
Clone out the template, overrwriting if needful.
$ shield init my-feature-study-addon --force
TBD - lint an existing project study
inspired by: