runbot/runbot_merge/tests
Xavier Morel 6d7c728471 [CHG] runbot_merge: toggle default merge method to rebase-and-merge
After discussion with al & rco, conclusion was default PR merging method
should be rebase-and-merge for cleaner history.

Add test for that scenario (w/ test for final DAG) and implement this
change.
2018-09-03 13:16:36 +02:00
..
fake_github [CHG] runbot_merge: toggle default merge method to rebase-and-merge 2018-09-03 13:16:36 +02:00
conftest.py [IMP] runbot_merge: pluginify github mock 2018-09-03 13:16:36 +02:00
local.py [IMP] runbot_merge: PR source branch/label handling 2018-09-03 13:16:36 +02:00
README.txt [ADD] runbot_merge: remote github plugin 2018-09-03 13:16:36 +02:00
remote.py [CHG] runbot_merge: toggle default merge method to rebase-and-merge 2018-09-03 13:16:36 +02:00
test_basic.py [CHG] runbot_merge: toggle default merge method to rebase-and-merge 2018-09-03 13:16:36 +02:00
test_multirepo.py [FIX] runbot_merge: testing of batch contents 2018-09-03 13:16:36 +02:00

Execute this test suite using pytest.

The default mode is to run tests locally using mock objects in place of
github, see the docstring of remote.py for additional instructions to run
against github "actual".

Shared properties running tests, regardless of the github implementation:

* test should be run from the root of the runbot repository providing the
  name of this module aka ``pytest runbot_merge`` or
  ``python -mpytest runbot_merge``
* a database name to use must be provided using ``--db``, the database should
  not exist beforehand
* the addons path must be specified using ``--addons-path``, both "runbot" and
  the standard addons (odoo/addons) must be provided explicitly

See pytest's documentation for other options, I would recommend ``-rXs``,
``-v`` and ``--showlocals``.

When running "remote" tests as they take a very long time (hours) `-x`
(aka ``--maxfail=1``) and ``--ff`` (run previously failed first) is also
recommended unless e.g. you run the tests overnight.