gecko-dev/testing/mozharness
Joel Maher f5a7cdf691 Bug 1348754 - stylo reftests appear to be running as non-e10s but are reported as e10s. r=kmoir
MozReview-Commit-ID: GXLNJrzZIL3
2017-03-24 09:50:49 -04:00
..
configs Bug 1348754 - stylo reftests appear to be running as non-e10s but are reported as e10s. r=kmoir 2017-03-24 09:50:49 -04:00
docs
examples
external_tools
mozfile
mozharness Bug 1340584 - Remove devicemanagerSUT and references to sutagent; r=wlach 2017-03-21 12:20:01 -06:00
mozinfo
mozprocess
scripts merge mozilla-inbound to mozilla-central a=merge 2017-03-22 14:26:27 +01:00
test Bug 1346359 - Script to submit transparency certs to CT r=rail 2017-03-10 17:48:37 -05:00
LICENSE
README.txt
mach_commands.py
requirements.txt
setup.cfg
setup.py
tox.ini
unit.sh

README.txt

# 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! =)