mirror of
https://github.com/odoo/runbot.git
synced 2025-03-19 09:25:46 +07:00
76c4d24bf5
Previously when splitting staging we'd create two never-staged stagings. In a system where the stagings get deleted once done with (succeeeded or failed) that's not really important, but now that we want to keep stagings around inactive things get problematic as this method gunks up the stagings table, plus the post-split stagings would "steal" the original's batches, losing information (relation between stagings and batches). Replace these empty stagings with dedicated *split* objects. A batch can belong to both a staging and a split, the split is deleted once a new staging has been created from it. Eventually we may want to make batches shared between stagings (so we can track the entire history of a batch) but currently that's only PR-level. |
||
|---|---|---|
| .. | ||
| fake_github | ||
| conftest.py | ||
| local.py | ||
| README.txt | ||
| remote.py | ||
| test_basic.py | ||
| test_multirepo.py | ||
Execute this test suite using pytest. The default mode is to run tests locally using mock objects in place of github, see the docstring of remote.py for additional instructions to run against github "actual". 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.