runbot

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

History

Xavier Morel 2ab06ca96b [IMP] *: require explicitly specifying whether exceptions in logs are valid Seems like a good idea to better keep track of the log of an Odoo used to testing, and avoid silently ignoring logged errors. - intercept odoo's stderr via a pipe, that way we can still write it back out and pytest is able to read & buffer it, pytest's capfd would not work correctly: it breaks output capturing (and printing on failure); and because of the way it hooks in it's unable to capture from subprocesses inheriting the standard stream, cf pytest-dev/pytest#4428 - update the env fixture to check that the odoo log doesn't have any exception on failure - make that check conditional on the `expect_log_errors` marker, this way we can mark tests for which we expect errors to be logged, and assert that that does happen		2024-06-12 15:09:42 +02:00
..
conftest.py	[ADD] *: per-repository webhook secret	2024-06-06 11:07:57 +02:00
README.rst	[IMP] runbot_merge: test readme & remove leftover pass	2018-09-03 13:16:36 +02:00
test_basic.py	[IMP] *: require explicitly specifying whether exceptions in logs are valid	2024-06-12 15:09:42 +02:00
test_batch_consistency.py	[ADD] *: per-repository webhook secret	2024-06-06 11:07:57 +02:00
test_by_branch.py	[ADD] *: per-repository webhook secret	2024-06-06 11:07:57 +02:00
test_disabled_branch.py	[ADD] *: per-repository webhook secret	2024-06-06 11:07:57 +02:00
test_multirepo.py	[IMP] *: require explicitly specifying whether exceptions in logs are valid	2024-06-12 15:09:42 +02:00
test_oddities.py	[IMP] *: require explicitly specifying whether exceptions in logs are valid	2024-06-12 15:09:42 +02:00
test_project_toggles.py	[ADD] *: per-repository webhook secret	2024-06-06 11:07:57 +02:00
test_provisioning.py	[IMP] runbot_merge, forwardport: minor cleanups	2023-08-10 13:33:16 +02:00
test_staging.py	[ADD] *: per-repository webhook secret	2024-06-06 11:07:57 +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