# checks..unit -- the Python unit suite from tests/unit/, run against the # package built by nix/package.nix, inside the build sandbox. # # nix/package.nix sets doCheck = false deliberately, so this is the only place # the suite runs in a build. { lib, runCommand, python3, hhstream, }: let pytestEnv = python3.withPackages (ps: [ ps.pytest ]); # Only the suite itself, so an editor's droppings or a local .pytest_cache # cannot change the derivation's hash. testSrc = lib.cleanSourceWith { name = "hhstream-unit-tests"; src = ../tests/unit; filter = path: type: let base = baseNameOf (toString path); in !(type == "directory" && (base == "__pycache__" || base == ".pytest_cache")) && !lib.hasSuffix ".pyc" base; }; in runCommand "hhstream-unit" { nativeBuildInputs = [ pytestEnv ]; passthru.testSrc = testSrc; meta.description = "hhstream unit tests (pytest)"; } '' cp -r ${testSrc} suite chmod -R u+w suite # The package is an application, so its library is not on the default path: # point PYTHONPATH at what nix/package.nix installed. Importing it here rather # than letting pytest do it makes a packaging problem distinguishable from a # test failure. export PYTHONPATH=${hhstream}/${python3.sitePackages} export PYTHONDONTWRITEBYTECODE=1 export HOME=$PWD python3 -c 'import hhstream; print("testing hhstream", hhstream.__version__, "from", hhstream.__file__)' set +e pytest suite \ --color=no -rf -q \ --junit-xml=report.xml \ -p no:cacheprovider \ --strict-markers \ --strict-config pytest_rc=$? set -e echo set +e python3 ${./lib/check_report.py} report.xml report_rc=$? set -e if [ "$report_rc" -eq 1 ]; then echo "unit check: the suite is empty or its report is unusable -- failing." >&2 exit 1 fi if [ "$report_rc" -ne 0 ] || [ "$pytest_rc" -ne 0 ]; then echo "unit check: the suite ran but did not pass (pytest exit $pytest_rc)." >&2 exit 1 fi mkdir -p $out cp report.xml $out/junit.xml ''