runbot

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

History

Xavier Morel 2fafd5419a [FIX] runbot_merge: attempt to stage PRs on disabled branches Normally opening a PR against a disabled branch is like opening a PR against a branch which is not configured at all: the PR id ignored entirely. However if the PR already exists then the state of the branch isn't normally checked when interacting with the branch, and it is possible to trigger its staging, at which point the staging itself will crash: on a project the branches are `active_test=False` so they're all visible in the form, but when repos go search()-ing for the branch they won't find it and will blow up. Solution: only try staging on branches which are active. Fixes odoo/runbot#408. Also do the same for checking stagings. And while at it, fix #409 by wrapping each checking or staging into a try/except and a savepoint. This way if a staging blows up it should move on to the next branch instead of getting stuck.		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	[FIX] runbot_merge: don't warn on unrecognized commands	2020-07-27 12:56:41 +02:00
test_by_branch.py	[IMP] runbot_merge: provide for statuses being only on PRs or stagings	2020-07-14 13:34:05 +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