weblate/docs/contributing/tests.rst
2025-06-09 09:46:22 +02:00

117 lines
3.2 KiB
ReStructuredText

Weblate testsuite and continuous integration
--------------------------------------------
Testsuites exist for most of the current code, increase coverage by adding testcases for any new
functionality, and verify that it works.
.. _ci-tests:
Continuous integration
++++++++++++++++++++++
Weblate relies on `GitHub Actions`_ to run tests, build documentation, code
linting, and other tasks to ensure code quality.
`Codecov`_ collects the code coverage information from the tests that were run.
.. _GitHub Actions: https://github.com/WeblateOrg/weblate/actions
.. _Codecov: https://app.codecov.io/gh/WeblateOrg/weblate/
There are several jobs to verify different aspects:
* Unit tests
* Documentation build and external links
* Migration testing from all supported releases
* Code linting
* Setup verification (ensures that generated dist files do not miss anything and can be tested)
The configuration for the CI is in :file:`.github/workflows` directory. It
heavily uses helper scripts stored in :file:`ci` directory. The scripts can be
also executed manually, but they require several environment variables, mostly
defining Django settings file to use and test database connection. The example
definition of that is in :file:`scripts/test-database.sh`:
.. literalinclude:: ../../scripts/test-database.sh
:language: sh
The simple execution can look like:
.. code-block:: sh
source scripts/test-database.sh
./ci/run-migrate
./ci/run-test
./ci/run-docs
.. _local-tests:
Local testing of Weblate
+++++++++++++++++++++++++
Before running test, please ensure test dependencies are installed. This can be done by ``pip install -e .[test]``.
Testing using pytest
~~~~~~~~~~~~~~~~~~~~
Prior to running tests you should collect static files as some tests rely on them being present:
.. code-block:: sh
DJANGO_SETTINGS_MODULE=weblate.settings_test ./manage.py collectstatic
You can use `pytest` to run a testsuite locally:
.. code-block:: sh
pytest weblate
Running an individual test file:
.. code-block:: sh
pytest weblate/utils/tests/test_search.py
.. hint::
You will need a database (PostgreSQL) server to be used for tests. By
default Django creates separate database to run tests with ``test_`` prefix,
so in case your settings is configured to use ``weblate``, the tests will
use ``test_weblate`` database. See :ref:`database-setup` for setup
instructions.
The :file:`weblate/settings_test.py` is used in CI environment as well (see
:ref:`ci-tests`) and can be tuned using environment variables:
.. code-block:: sh
export CI_DATABASE=postgresql
export CI_DB_USER=weblate
export CI_DB_PASSWORD=weblate
export CI_DB_HOST=127.0.0.1
export CI_DB_PORT=60000
export DJANGO_SETTINGS_MODULE=weblate.settings_test
.. hint::
The tests can also be executed inside developer docker container, see :ref:`dev-docker`.
.. seealso::
See :doc:`django:topics/testing/index` for more info on running and
writing tests for Django.
Local testing of Weblate modules
--------------------------------
The tests are executed using :program:`py.test`. First you need to install test requirements:
.. code-block:: sh
uv pip install -e '.[dev]'
You can then execute the testsuite in the repository checkout:
.. code-block:: sh
py.test