Python support

[axc450]

I would like Python tests to be supported by the test reporter./

Using the Java JUNIT format with unittest-xml-reporting seems to work decently, but I don't seem to get a traceback with failed tests:

Could this be fixed (or have a proper supported Python type)? The traceback does exist in the XML, so maybe we could have an option to turn the parsing of it off?

Thanks!

[jnguyen75]

I've had success with pytest (which is compatible with unittest) by providing --junit-xml option and --tb to configure the traceback, which this test report uses to display more useful error messages.

[tfikler]

I've had success with pytest (which is compatible with unittest) by providing --junit-xml option and --tb to configure the traceback, which this test report uses to display more useful error messages.

Can you please provide more information about how you managed to do it on using python pytest?

[jnguyen75]

I've had success with pytest (which is compatible with unittest) by providing --junit-xml option and --tb to configure the traceback, which this test report uses to display more useful error messages.

Can you please provide more information about how you managed to do it on using python pytest?

You just need to provide the --junit-xml argument as documented here: https://docs.pytest.org/en/7.2.x/how-to/output.html

Then provide that same path to the path input for this plugin.

[rivethead]

I am using the action with pytest with junit xml.

Step to run tests:

      - name: Run tests
        run: pytest -rfsp --junit-xml=test-results.xml --tb=auto

Step to surface test results:

      - name: Publish Test Results
        uses: dorny/test-reporter@v1
        if: always()
        with:
          name: Tests
          path: <your-path>/*.xml
          reporter: java-junit

[micmarc]

I am using this in a Django project with unittest-xml-reporting. I can see my tracebacks, but I have to scroll all the way to the bottom under "Annotations" and click the "Raw Output" button. (This is on V1; I have not gone to V2 yet.) It's not ideal, but it works fine for my purposes.

    - name: (Django) Run Tests
      run: pipenv run python manage.py test

    - name: Generate Test Report
      uses: dorny/test-reporter@v1
      if: ${{ !cancelled() }}
      with:
        name: Test Results
        path: junit-report.xml
        reporter: java-junit
        fail-on-error: false

[micmarc]

With V2 I am now seeing the full failure message (value of failure.message from JUnit report XML) inline with the failed test entry. This is very useful. However, I no longer have the traceback available in the annotations, even though I can see it as CDATA in the XML.