runbot

mirror of https://github.com/odoo/runbot.git synced 2025-03-19 09:25:46 +07:00

History

Xavier Morel 3b28d7801d [IMP] runbot_merge: be more optimistic about PR mergeability If we can't stage a PR, rather than immediately put them in error wait until they were the first we tried staging, otherwise they might have been conflicting with the previous batch which ultimately won't be merged for other reason and they would have worked as part of the next batch. Note: this commit will lead to false negatives because it's batch-based rather than repo-based, so if the first batch only affects repo A and the second batch only affects repo B, if the second batch triggers a merge error it should be rejected immediately (as it's applied on a "pristine" repo B) but this change will just bump it to the next staging. fixes #209		2020-10-02 15:28:36 +02:00
..
conftest.py	[IMP] runbot_merge: split staging cron in two	2020-02-11 08:07:57 +01:00
README.rst	[IMP] runbot_merge: test readme & remove leftover pass	2018-09-03 13:16:36 +02:00
test_basic.py	[IMP] runbot_merge: be more optimistic about PR mergeability	2020-10-02 15:28:36 +02:00
test_by_branch.py	[CHG] runbot_merge: branch_ids -> branch_filter	2020-10-02 15:28:36 +02:00
test_multirepo.py	[FIX] runbot_merge: blocked flag false positive	2020-10-02 15:28:36 +02:00
test_oddities.py	[FIX] runbot_merge: attempt to stage PRs on disabled branches	2020-10-02 15:28:36 +02:00
test_utils.py	[IMP] *: unify gh test API between runbot and fw-bot	2019-10-10 10:11:48 +02:00

README.rst

Execute this test suite using pytest.

The default mode is to run tests locally using a mock github.com.

See the docstring of remote.py for instructions to run against github "actual"
(including remote-specific options) and the end of this file for a sample.

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.

``pytest.ini`` sample
---------------------

.. code:: ini

    [github]
    owner = test-org
    token = aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

    [role_reviewer]
    name = Dick Bong
    user = loginb
    token = bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb

    [role_self_reviewer]
    name = Fanny Chmelar
    user = loginc
    token = cccccccccccccccccccccccccccccccccccccccc

    [role_other]
    name = Harry Baals
    user = logind
    token = dddddddddddddddddddddddddddddddddddddddd