Mangono runbot (Odoo tester)

This project all the source code relative to the process to test Odoo in the mangono way.

This project support Odoo version 12.0 to 18.0.

The complete documentation is available on atlas

Use it as a GitLab CI Components

include:
  - component: $CI_SERVER_FQDN/gitlab-ci/odoo-quality/runbot@1
    inputs:
      odoo-version: "18.0"

See this component page for more information

Run tests

You can simply run test with

hatch -e test test

If you want to run the runbot on a particular version you can

docker compose run --rm -it runbot18

Build lib

hatch build

Use it with mise (without Docker Odoo image)

Use the runbot-mise component if your runner already has mise available and you prefer not to depend on a pre-built Odoo Docker image:

include:
  - component: $CI_SERVER_FQDN/gitlab-ci/odoo-quality/runbot-mise@1
    inputs:
      odoo-version: "18.0"
      tag: "my-runner"

The component uses registry.mangono.io/dockers/clevertools-batteries as the base image. It calls mise run build to set up the Odoo venv, then delegates to mise run odoo:runbot.

Required mise tasks (in the consuming project)

The consuming project must expose two tasks in its mise.toml / tasks/ directory:

build — downloads Odoo and sets up the Python venv
odoo:runbot — runs the full runbot sequence (diag → init → run → report)

To create odoo:runbot as a file-based task (recommended), add tasks/odoo/runbot to the consuming project (see odoo-mise-linux):

#!/usr/bin/env bash
# mise description="Lance le runbot Odoo (diag → init → run → report)"
set -e
odoo-runbot --verbose --workdir="${RUNBOT_WORKDIR:-.}" --config="${RUNBOT_CONFIG:-}" diag
export DB_HOST="${DB_HOST:-database}"
odoo-runbot --verbose --workdir="${RUNBOT_WORKDIR:-.}" --config="${RUNBOT_CONFIG:-}" init
odoo-runbot --workdir="${RUNBOT_WORKDIR:-.}" --config="${RUNBOT_CONFIG:-}" run ${RUNBOT_ARGS:-} || EXIT=$?
echo "Execute coverage report in ${RUNBOT_WORKDIR:-.}/runbot_result"
odoo-runbot --workdir="${RUNBOT_WORKDIR:-.}" --config="${RUNBOT_CONFIG:-}" report
exit ${EXIT:-0}

Configuration is done via [env] in mise.toml:

[env]
RUNBOT_WORKDIR = "odoo_project"
RUNBOT_CONFIG  = "odoo_project/pyproject.toml"

Build Doc

You can build python code as doc with mkdoc, you only need to run

hatch -e doc run mkdocs build # or server

Metadata

Release files for odoo-runbot 1.11.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for odoo-runbot 1.11.1
File	Size	Uploaded	Provenance
odoo_runbot-1.11.1.tar.gz	176.3 kB	Oct 19, 2026	Without provenance	Details

Built distribution (wheel)

Table of built distributions (wheels) for odoo-runbot 1.11.1
File	Interpreter	ABI	Platform	Reset
odoo_runbot-1.11.1-py3-none-any.whl 33.3 kB Oct 19, 2026 Without provenance	Python 3	none	any	Details

Total release size: 209.6 kB

Release files / odoo_runbot-1.11.1.tar.gz

Download URL	odoo_runbot-1.11.1.tar.gz
Size	176.3 kB
Tags	Source
SHA-256 checksum How to use checksums	`357ecbf57028003135ebcd3c936dc6adbd4517f0c59d88b5329bc9c699551c10`
BLAKE2b-256 checksum How to use checksums	`9202cc46abe4baa6d145e5b45069c61430f6bdb4ed4c2881e8bb24fe909b850a`
Upload date	Oct 19, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.15.0`

Release files / odoo_runbot-1.11.1-py3-none-any.whl

Download URL	odoo_runbot-1.11.1-py3-none-any.whl
Size	33.3 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`94e572b4c558e4f1ce35cb9ad145c81cd0b7e5a38f42cfa52822aabecfa7fa8e`
BLAKE2b-256 checksum How to use checksums	`758e817023d6b1951b9493cf1ac75eeb0fe64f836115f51ca2cf19ad12f31904`
Upload date	Oct 19, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.15.0`

Security for odoo-runbot 1.11.1

Report project as malware

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.