gecko-dev/testing/mozharness
2018-02-17 00:13:16 +02:00
..
configs Merge mozilla-central to inbound. a=merge CLOSED TREE 2018-02-17 00:13:16 +02:00
docs
examples
external_tools Bug 1435729 - Always use vendored tooltool.py; r=jlund 2018-02-07 14:37:48 -08:00
manifestparser
mozfile
mozharness Merge mozilla-central to inbound. a=merge CLOSED TREE 2018-02-17 00:13:16 +02:00
mozinfo Bug 1428461 - Update mozharness' mozinfo from mozbase; r=jmaher 2018-01-08 07:41:09 -07:00
mozprocess
scripts Bug 1398796 - Do uptake monitoring in TC r=mtabara 2018-02-15 08:49:45 -05:00
test Bug 1434365: Specify mozconfig in L10N repacks by using parts; r=Callek 2018-01-23 15:18:32 -07:00
LICENSE
mach_commands.py
README.txt
requirements.txt
setup.cfg
setup.py
tox.ini
unit.sh

# Mozharness

## Docs
* https://developer.mozilla.org/en-US/docs/Mozharness_FAQ
* https://wiki.mozilla.org/ReleaseEngineering/Mozharness
* http://moz-releng-mozharness.readthedocs.org/en/latest/mozharness.mozilla.html
* http://moz-releng-docs.readthedocs.org/en/latest/software.html#mozharness

## Submitting changes
Like any Gecko change, please create a patch or submit to Mozreview and
open a Bugzilla ticket under the Mozharness component:
https://bugzilla.mozilla.org/enter_bug.cgi?product=Release%20Engineering&component=Mozharness

This bug will get triaged by Release Engineering

## Run unit tests
To run the unit tests of mozharness the `tox` package needs to be installed:

```
pip install tox
```

There are various ways to run the unit tests. Just make sure you are within the `$gecko_repo/testing/mozharness` directory before running one of the commands below:

```
tox                            # run all unit tests
tox -- -x                      # run all unit tests but stop after first failure
tox -- test/test_base_log.py   # only run the base log unit test
```

Happy contributing! =)