Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] change in structure of junit report #2007

Open
1 task done
camaeel opened this issue Sep 24, 2024 · 0 comments
Open
1 task done

[Feature] change in structure of junit report #2007

camaeel opened this issue Sep 24, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@camaeel
Copy link

camaeel commented Sep 24, 2024

Problem Statement

Old reports (version 0.2.9 and earlier) were nicely imported to Jenkins using junit plugin.
After 0.2.10 any XML based format looks bad.

Solution Description

Could you change testcase's classname to testcase's name? I did some trial and error and it seems that classname is very important here.

JUNIT-OPERATIONS could look like:

<testsuites name="chainsaw-report" time="60.532180" tests="10">
  <testsuite name="ingress-test" tests="10" failures="0" errors="0" id="0" package="ingress-test" time="60.530826" timestamp="2024-09-23T16:14:53+02:00">
    <properties>
      <property name="namespace" value="chainsaw-equal-falcon"></property>
    </properties>
    <testcase name="step 1 / operation 1" classname="nice-test-name" time="0.198683"></testcase>
    <testcase name="step 1 / operation 2" classname="nice-test-name" time="0.218880"></testcase>
    <testcase name="step 1 / operation 3" classname="nice-test-name" time="0.205299"></testcase>
  </testsuite>
</testsuites>

and similiar for other report types:

  • JUNIT-TEST:
<testsuites name="chainsaw-report" time="27.806035" tests="1">
  <testsuite name="ingress-test" tests="1" failures="0" errors="0" id="0" time="">
    <testcase name="nice-test-name" classname="nice-test-name" time="27.805601"></testcase>
  </testsuite>
</testsuites>

Alternatives

Parsing xml or json result and creating own report format

Additional Context

No response

Slack discussion

No response

Research

  • I have searched other issues in this repository and mine is not recorded.
@camaeel camaeel added the enhancement New feature or request label Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant