pytest-devant-cloud

pytest plugin that streams runs, results, and per-test step trees into Devant.net while your suite runs.

Requirements

Python 3.10 or newer, and pytest 7 or newer.

Quick start

Install the plugin:

pip install pytest-devant-cloud

Point it at your project. Copy the token and project id from your Devant CI/CD settings:

export DEVANT_API_URL=https://acme.devant.net
export DEVANT_TOKEN=your-ci-token
export DEVANT_PROJECT_ID=42

Run pytest as you normally would:

pytest

Results show up in Devant while the suite is still running. There is nothing to add to conftest.py; the plugin registers itself through pytest's pytest11 entry-point group.

Upgrading from 0.1.x

Every environment variable was renamed, and all config defaults were removed. Upgrade without changing your CI and the plugin disables itself — your suite still passes, so reporting stops without anything failing.

0.1.x silently fell back to http://localhost:32124, the token dev-admin-token, and project 1. A misconfigured CI job therefore either 401'd against a real tenant or filed its results under whatever project happened to be id 1. There are no fallbacks now.

When configuration is missing or unusable, the plugin writes one JSON line to stderr and does nothing further:

{"level":"error","source":"pytest-devant-cloud","msg":"not configured","missing":["DEVANT_TOKEN"]}

After upgrading, grep your CI logs for "msg":"not configured".

Configuration

Configure with environment variables:

The same settings work as CLI flags, which win over the environment:

pytest \
  --devant-api-url=https://acme.devant.net \
  --devant-token=$DEVANT_TOKEN \
  --devant-project-id=42

Turn the plugin off for a single run without uninstalling it:

pytest -p no:devant_cloud

Binding tests to cases

Each test maps to one case in Devant. The plugin chooses the case in this order:

1. The @pytest.mark.devant("DEF-AB12") marker on the test, if present.
2. An existing case whose name matches the test.
3. A new case, created on the spot, with a key like DEF-XYZ9.

An auto-created case is tied to the test's name and its place in the suite tree, so renaming or moving the test starts a fresh case. To keep a test's history across renames, copy its key from your Devant dashboard and pin it in source:

@pytest.mark.devant("DEF-XYZ9")
def test_login(): ...

Coverage

Coverage is read from the Cobertura XML pytest-cov writes, so you need --cov-report=xml — an HTML-only report produces no XML and the upload silently no-ops:

pytest --cov=myapp --cov-report=xml --cov-report=html

The plugin picks up coverage.xml from the working directory (then rootdir) by default; point it elsewhere with --devant-coverage path/to/coverage.xml or DEVANT_COVERAGE. Line and branch percentages are sent; Cobertura carries no function metric, and coverage.py's lines are its statements, so those two fields stay null. A missing or unparseable report is warned-and-skipped, never fatal.

Suites

The plugin turns each test's location into a nested suite tree, built from the directories, module, and class around it. The leaf is the test function plus any parametrize id.

If you re-parent a suite by hand in the dashboard, the plugin leaves your change alone on later runs.

CI metadata

On GitHub Actions, GitLab CI, CircleCI, Jenkins, and Azure DevOps (or any runner that sets CI=true), the plugin attaches the commit, branch, and pull request to each run, so Devant can link a run back to the code that triggered it.