Pytest currently outputs a junit xml file, saved as an artefact by GHActions, which lacks detail.
Current pytest command:
|
pytest --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml |
Current output:
<?xml version="1.0" encoding="utf-8"?><testsuites name="pytest tests"><testsuite name="pytest" errors="0" failures="0" skipped="0" tests="3" time="0.394" timestamp="2025-10-06T10:13:04.464747+00:00" hostname="runnervmwhb2z"><testcase classname="tests.test_db" name="test_card_insert_and_get" time="0.005" /><testcase classname="tests.test_random" name="test_random_card_request" time="0.178" /><testcase classname="tests.test_transform" name="test_transform_card_pulls_correct_values" time="0.000" /></testsuite></testsuites>
I'd like a more verbose report, possibly as a committed file, rather than a zipped (and slightly buried artefact) that clearly displays what passed and what failed, as with running pytest locally on terminal, (or found buried in the execution logs).
Finally, perhaps the action should 'fail' if any tests fail to give a clearer alert of failing tests... though this might get confusing if the testing process fails, rather than the rest result. Explore best practice here.
Pytest currently outputs a junit xml file, saved as an artefact by GHActions, which lacks detail.
Current pytest command:
scry/.github/workflows/run-tests.yml
Line 35 in 812390c
Current output:
I'd like a more verbose report, possibly as a committed file, rather than a zipped (and slightly buried artefact) that clearly displays what passed and what failed, as with running
pytestlocally on terminal, (or found buried in the execution logs).Finally, perhaps the action should 'fail' if any tests fail to give a clearer alert of failing tests... though this might get confusing if the testing process fails, rather than the rest result. Explore best practice here.