Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/MozillaSecurity/prefpicker
Manage & generate prefs.js files
https://github.com/MozillaSecurity/prefpicker
automated-testing automation firefox fuzz fuzzing test testing
Last synced: 4 days ago
JSON representation
Manage & generate prefs.js files
- Host: GitHub
- URL: https://github.com/MozillaSecurity/prefpicker
- Owner: MozillaSecurity
- License: mpl-2.0
- Created: 2020-02-07T20:56:41.000Z (over 4 years ago)
- Default Branch: master
- Last Pushed: 2024-04-02T17:49:07.000Z (7 months ago)
- Last Synced: 2024-04-14T06:38:19.431Z (7 months ago)
- Topics: automated-testing, automation, firefox, fuzz, fuzzing, test, testing
- Language: Python
- Homepage:
- Size: 155 KB
- Stars: 9
- Watchers: 10
- Forks: 4
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Codeowners: .github/CODEOWNERS
Awesome Lists containing this project
README
PrefPicker
==========
[](https://community-tc.services.mozilla.com/api/github/v1/repository/MozillaSecurity/prefpicker/master/latest)
[](https://codecov.io/gh/MozillaSecurity/prefpicker)
[].num_joined_members&suffix=%20users&url=https%3A%2F%2Fmozilla.modular.im%2F_matrix%2Fclient%2Fr0%2FpublicRooms&style=flat&logo=matrix)](https://riot.im/app/#/room/#fuzzing:mozilla.org)
[](https://pypi.org/project/prefpicker)
Manage & generate prefs.js files for use when testing Firefox. This tool is intended to simplify the use and tracking of prefs used by
our fuzzing tools. The template files can be modified to allow the creation of custom prefs.js files without
the need to maintain a separate mostly duplicate version of a prefs file.
YAML Template Structure
-----------------------
The template document is made up of variants, prefs and values.
_**pref**_ is the name of the preference that will be added to the prefs.js file. This is an unquoted string.
Valid prefs can be found in [all.js](https://hg.mozilla.org/mozilla-central/file/tip/modules/libpref/init/all.js) or in [StaticPrefList.yml](https://hg.mozilla.org/mozilla-central/file/tip/modules/libpref/init/StaticPrefList.yaml).
__**review_on_close**__ is optional. It is a list of relevant Bugzilla IDs used to help avoid obsolete entries. When all bugs in the list are closed the entry will be reviewed and removed if appropriate.
_**value**_ can be a `bool`, `int`, `string` or `null`. Adding multiple potential values is possible.
When multiple values are present one is chosen at random when generating the output.
Using a value of `null` will exclude the pref from the prefs.js file (acts as browser default).
_**variant**_ is a subset of values to be used in place of the default values.
The default variant is used unless a variant is specified.
There are a few mechanisms in place to help keep the file in order:
- All prefs must have a default variant
- All variants must be defined in the variant list
- All variants in the variant list must be used
- All variants must be a list and contain values
```yml
# example.yml
variant: # list of extra variants, default is implied
- alt # name of variant
pref:
pref.name: # unquoted name of the pref used in prefs.js
review_on_close: # optional
- 123456
variants:
default: # variant definition, default is required
- 0 # potential value
alt: # extra optional variant
- 1 # if multiple values are defined one is chosen randomly
- null # null is a special case meaning exclude the pref
```
Updating Templates and Adding Prefs
-----------------------------------
Prefs are found in the `.yml` files in the [template](/src/prefpicker/templates) directory.
Only prefs that are ready to be tested should be added.
When adding a pref to a template it is encouraged to add a comment that provides justification and points to a bug in Bugzilla for additional context.
If a pref does not already exist and is only used with non-default variants a `null` entry must be added to the default variant.
Quick Setup
-----------
Use pip to install prefpicker.
```bash
pip install prefpicker
```
Examples
--------
Use a built-in [template](/src/prefpicker/templates) to generate an up-to-date `prefs.js` file.
```bash
prefpicker browser-fuzzing.yml prefs.js
```
Or generate a `prefs.js` file from a custom template using the `webrender` variant:
```bash
user@machine:~/prefpicker$ prefpicker custom/template.yml ~/Desktop/prefs.js --variant webrender
Loading 'template.yml'...
Loaded 255 prefs and 5 variants
Generating 'prefs.js' using variant 'webrender'...
Done.
```
The resulting `prefs.js` file is ready to be used with Firefox. It will look something like this:
```js
// Generated with PrefPicker @ 2020-02-08 00:50:29 UTC
// Variant 'webrender'
/// ... snip
user_pref("fuzzing.enabled", true);
/// ... snip
// 'gfx.webrender.all' defined by variant 'webrender'
user_pref("gfx.webrender.all", true);
/// ... snip
```