mirror of
https://github.com/odoo/runbot.git
synced 2025-03-19 09:25:46 +07:00
4a4252b4b9
- github logins are case-insensitive while the db field is CI the dict in which partners are stored for matching is not, And the caller may not preserve casing. Thus it's necessary to check the casefolded database values against casefolded parameters, rather than exactly. - users may get disabled by mistake or when one leaves the project, they may also get switched from internal to portal, therefore it is necessary to re-enable and re-enroll them if they come back. - while at it remove the user's email when they depart, as they likely use an organisational email which they don't have access to anymore Side-note, but remove the limit on the number of users / partners being created at once: because there are almost no modules in the mergebot's instance, creating partner goes quite fast (compared to a full instance), thus the limitation is almost certainly unnecessary (creating ~300 users seems to take ~450ms). Fixes ##776 |
||
|---|---|---|
| .. | ||
| conftest.py | ||
| README.rst | ||
| test_basic.py | ||
| test_by_branch.py | ||
| test_disabled_branch.py | ||
| test_multirepo.py | ||
| test_oddities.py | ||
| test_provisioning.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