mirror of
https://github.com/odoo/runbot.git
synced 2025-03-19 09:25:46 +07:00
bbce5f8f46
Initially wanted to skip this only for FW PRs, but after some thinking I feel this info could still be valuable even for non-fw PRs which were never merged in the first place. Requires a few adjustments to not break *everything*: `batch.prs` excludes closed PRs by default as most processes only expect to be faced by a closed PR inside a batch, and we *especially* want to avoid that before the batch is merged (as we'd risk staging a closed PR). However since PRs don't get removed from batches anymore (and batches don't get deleted when they have no PRs) we now may have a bunch of batches whose PRs (usually a single one) are all closed, this has two major side-effects: - a new PR may get attached to an old batch full of closed PRs (as batches are filtered out on being *merged*), which is weird - the eventual list of batches gets polluted with a bunch of irrelevant batches which are hard to filter out The solution is to reintroduce an `active` field, as a stored compute field based on the state of batch PRs. This way if all PRs of a batch are closed it switches to inactive, and is automatically filtered out by search which solves both issues. |
||
|---|---|---|
| .. | ||
| conftest.py | ||
| README.rst | ||
| test_basic.py | ||
| test_batch_consistency.py | ||
| test_by_branch.py | ||
| test_disabled_branch.py | ||
| test_multirepo.py | ||
| test_oddities.py | ||
| test_project_toggles.py | ||
| test_provisioning.py | ||
| test_staging.py | ||
| test_status_overrides.py | ||
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