runbot

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

History

Xavier Morel 985aaa5798 [FIX] runbot_merge: lock-in statuses after a staging has finished The `statuses` field of a staging is always "live" because it's a computed non-stored field. This is an issue when a staging finishes in whatever state, then someone gets new statuses sent on one of the head commits, either by rebuilding (part of) the staging or by just using the same commit for one of their branches. This makes the reporting of the main dashboard confusing, as one might look at a failed staging and see all the required statuses successful. It also makes post-mortem analysis more complicated as the logs have to be trawled for what the statuses used to be (and they don't always tell). Solve this by storing a snapshot of the statuses the first time a staging moves away from `pending`, whether it's to success or failure. Fixes #667		2022-12-01 10:57:32 +01:00
..
conftest.py	[IMP] runbot_merge: small reorg of main models file	2021-11-10 13:13:34 +01:00
README.rst	[IMP] runbot_merge: test readme & remove leftover pass	2018-09-03 13:16:36 +02:00
test_basic.py	[ADD] runbot_merge: multi-commit squash mode	2022-12-01 10:57:32 +01:00
test_by_branch.py	[IMP] runbot_merge: small reorg of main models file	2021-11-10 13:13:34 +01:00
test_disabled_branch.py	[REV] runbot_merge: don't close PRs when deactivating branches	2022-12-01 10:57:32 +01:00
test_multirepo.py	[IMP] *: freeze wizard v3, freezer and wizarder	2022-08-05 15:35:51 +02:00
test_oddities.py	[FIX] runbot_merge: lock-in statuses after a staging has finished	2022-12-01 10:57:32 +01:00
test_provisioning.py	[IMP] runbot_merge: provisioning features	2022-06-30 15:07:49 +02:00
test_status_overrides.py	[IMP] *: review mergebot & forwardbot messages for pinging	2022-06-30 15:07:49 +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