pytest-devant-cloud

pytest plugin that streams runs, results, and per-test step trees into Devant as your suite executes — the Python sibling of @devant-net/playwright-reporter.

Install

pip install pytest-devant-cloud

The plugin auto-registers via the pytest11 entry-point group. No conftest.py changes are needed.

Configure

Set env vars before invoking pytest:

Or with CLI flags:

pytest \
  --devant-api-url=https://acme.devq.cloud \
  --devant-token=$DEVANT_TOKEN \
  --devant-project-id=1

To disable the plugin for one run without uninstalling:

pytest -p no:devant_cloud

How tests bind to test cases

Each pytest item resolves to a Devant test_case row in this order:

1. @pytest.mark.devant("DEF-AB12") marker on the test — looked up via GET /v1/test-cases/by-key/DEF-AB12.
2. Exact name match (<file>::<test> nodeid) in the project → GET /v1/test-cases?search=….
3. Auto-create → POST /v1/test-cases. The plugin prints the new key:

   [devant] minted DEF-XYZ9 for "tests/test_auth.py::test_login"
            — add @pytest.mark.devant("DEF-XYZ9") to bind it
   

Bind the key in source once and future runs (even with renames) reuse the same case.

What gets sent

The step tree includes one node per phase (setup / call / teardown) with status, duration, and longrepr captured as error_message.

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

Tests are grouped into Devant's nestable suite hierarchy. The nodeid is split into a suite chain (directories + module stem + class chain) and a leaf name (the test function plus its parametrize id):

The segments are sent on both test-case resolution (POST /v1/test-cases, which find-or-creates the suite chain) and result submission (POST /v1/runs/:id/results, which stamps suite_id when still unset). Manual re-parenting in the UI is never overwritten.

CI metadata

Auto-detected for GitHub Actions, GitLab CI, CircleCI, Jenkins, and Azure DevOps, plus a generic CI=true fallback. Populates the ci_* columns on the run so the dashboard can deep-link to commits and PRs.