runbot

mirror of https://github.com/odoo/runbot.git synced 2025-03-15 23:45:44 +07:00

History

Xavier Morel 5441ba12ae [FIX] runbot_merge: format_patch if `--no-prefix` Turns out you can configure format-patch with `--no-prefix` and some people (cough cough mat) have that in their standard setup, so the assumption of needing to strip 1 level of prefix does not necessarily hold. Also fix a few more issues: - some people (cough cough still mat) also use `-n` by default, which adds the series sequence (`n/m`) even for a single patch, handle that correctly - logging patch application errors is pretty useful when patching fails and I'm trying to get the information via logs, do that - especially when I decide to add error messages to tracking but forgot to show the chatter by default, fix that as well The commit-based patcher worked first try, and patch-based would have worked too if not for those meddling kids. In the future it might be a good idea to reify the stripping level (`-p`) on the patch object though, and maybe provide a computed preview of the list of files to patch, so issues are easier for the operator to diagnose.		2024-11-18 12:37:44 +01:00
..
conftest.py	[REM] *: default_crons fixture	2024-08-02 15:14:50 +02:00
README.rst	[IMP] runbot_merge: test readme & remove leftover pass	2018-09-03 13:16:36 +02:00
test_basic.py	[CHG] runbot_merge: make merge method non-blocking	2024-10-07 08:07:59 +02:00
test_batch_consistency.py	[FIX] runbot_merge: flaky test	2024-08-05 08:58:05 +02:00
test_by_branch.py	[CHG] runbot_merge: move labels cron to triggered	2024-10-22 10:50:09 +02:00
test_dfm.py	[ADD] runbot_merge: rendering of PR descriptions	2024-07-15 10:28:28 +02:00
test_disabled_branch.py	[IMP] runbot_merge: add notifications on inactive branch interactions	2024-09-24 10:22:07 +02:00
test_multirepo.py	[CHG] runbot_merge: make merge method non-blocking	2024-10-07 08:07:59 +02:00
test_oddities.py	[FIX] *: UX around fw=no	2024-09-17 11:31:20 +02:00
test_patching.py	[FIX] runbot_merge: format_patch if `--no-prefix`	2024-11-18 12:37:44 +01:00
test_project_toggles.py	[IMP] *: trigger-ify staging cron	2024-08-02 15:14:50 +02:00
test_provisioning.py	[IMP] runbot_merge, forwardport: minor cleanups	2023-08-10 13:33:16 +02:00
test_staging.py	[FIX] *: unstage on status going from success to failure	2024-09-18 15:19:13 +02:00
test_status_overrides.py	[ADD] *: per-repository webhook secret	2024-06-06 11:07:57 +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