runbot

mirror of https://github.com/odoo/runbot.git synced 2025-03-19 01:15:48 +07:00

History

Xavier Morel 318803d7bb [IMP] runbot_merge: tag PRs with a pseudo-branch on merge to master If a PR got merged to master (or whatever the current development branch is), there's no easy way to know what maintenance branch it ended up landing in, except by asking git which branches contain the commit (which can be rather slow). Add a special case on merge which labels the PR with a pseudo-branch patterned after the second-to-last branch of the project: * if the branch ends with a number, increment the number by one e.g. 2.0 -> 2.1, 5 -> 5.1 * otherwise, just prefix with `post-` e.g. "maint" -> "post-maint" (that one doesn't sound very helpful, but I guess it's nice for the weirdoes who call their branches "natty narwhal" and shit) Fixes #450		2021-03-02 14:28:32 +01: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: incorrect processing of rebased commit messages	2021-01-21 13:15:32 +01:00
test_by_branch.py	[IMP] runbot_merge: tag PRs with a pseudo-branch on merge to master	2021-03-02 14:28:32 +01:00
test_disabled_branch.py	[CHG] runbot_merge, forwardport: remove labelling	2020-11-20 07:41:54 +01:00
test_multirepo.py	[CHG] runbot_merge, forwardport: remove labelling	2020-11-20 07:41:54 +01:00
test_oddities.py	[IMP] runbot_merge: add name_search override to PRs	2021-03-02 14:28:32 +01:00
test_status_overrides.py	[FIX] mergebot: handle multiples of each command	2021-01-12 09:54:45 +01: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