Skip to content

test: use gitlab junit support with pytest

Dmitry Rodionov requested to merge dkr/gitlab-pytest-junit into master

Summary

  • test: use gitlab junit support with pytest

The patch makes it possible to view test results directly in gitlab. It shows which ones have failed. Which failed ones have failed on master in past 14 days (in other words it shows which failed tests from your branch are known to be flaky) and much more.

I took a look on integration from cargo side, it is a bit more involved. Builtin test runner doesnt output junit files, but there is an alternative test runner that is faster than the default one and it supports junit output: https://github.com/nextest-rs/nextest so to me this is a valid reason to use it in ci (no need to change local workflow, test runner is compatible with default one).

To see test report with failed tests take a look at this one: https://git.picodata.io/picodata/picodata/picodata/-/pipelines/27031/test_report (dont hesitate to click "view details", its really helpful)

Ensure that

  • New code is covered by tests
  • API is documented
  • Changelog is up to date
  • (if Lua API changed) Lua API version is bumped in luamod.rs
  • (if necessary) A follow-up doc issue is created in picodata/docs and linked here
Edited by Dmitry Rodionov

Merge request reports