gecko-dev/testing/mozharness
Narcis Beleuzu 9b1cd3b0bd Backed out 4 changesets (bug 1492362) for android wpt failures. CLOSED TREE
Backed out changeset ac0fdd0c661e (bug 1492362)
Backed out changeset 89ecd6ee8edd (bug 1492362)
Backed out changeset ae17b683bf71 (bug 1492362)
Backed out changeset 485f333bc3b7 (bug 1492362)
2020-08-19 13:54:36 +03:00
..
configs Backed out 4 changesets (bug 1492362) for android wpt failures. CLOSED TREE 2020-08-19 13:54:36 +03:00
docs
examples
external_tools Bug 1408051 - Remove mozharness' copy of virtualenv and use the one under /third_party/python instead r=ahal,rail 2020-08-05 19:52:24 +00:00
mozharness Bug 1408051 - Remove mozharness' copy of virtualenv and use the one under /third_party/python instead r=ahal,rail 2020-08-05 19:52:24 +00:00
scripts Backed out 4 changesets (bug 1492362) for android wpt failures. CLOSED TREE 2020-08-19 13:54:36 +03:00
test
LICENSE
mach_commands.py
moz.build
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! =)