mirror of
https://github.com/odoo/runbot.git
synced 2025-03-20 18:05:46 +07:00
c67bb64537
Skipmerge creates forward-ports before the source PR is even merged. - In a break from the norm, skipmerge will create forwardports even in the face of conflicts. - It will also not *detach* pull requests in case of conflicts, this is so the source PR can be updated and the update correctly cascades through the stack (likewise for any intermediate PR though *that* will detach as usual). Note that this doesn't really look at outstandings, especially as they were recently updated, so it might need to be fixed up in case of freakout, but I feel like that should not be too much of an issue, the authors will just get their FW reminders earlier than usual. If that's a hassle we can always update the reminder job to ignore forward ports whose source is not merged I guess. Fixes #418 |
||
|---|---|---|
| .. | ||
| conftest.py | ||
| README.rst | ||
| test_basic.py | ||
| test_batch_consistency.py | ||
| test_by_branch.py | ||
| test_dfm.py | ||
| test_disabled_branch.py | ||
| test_multirepo.py | ||
| test_nondeterministic_failures.py | ||
| test_oddities.py | ||
| test_patching.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