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

Junit support #63

Open
lionelbelmon opened this issue Jul 3, 2020 · 2 comments
Open

Junit support #63

lionelbelmon opened this issue Jul 3, 2020 · 2 comments

Comments

@lionelbelmon
Copy link

Since CSVcompare is typically used in CI toolchains for verifying non-regression of results, it would make sense to also generate a Junit XML summary of the comparisons.

@beutlich
Copy link
Collaborator

beutlich commented Jul 3, 2020

Can you please specify how such an XML summary is defined and where it needs to be saved? See https://stackoverflow.com/q/4922867/8520615.

Currently we have simple log files per comparison for automatic detection of the comparison verdict, see. e.g. https://github.com/modelica/MAP-LIB_ReferenceResults/blob/v4.0.0/Modelica/Blocks/Examples/PID_Controller/compare_passed.log for an example.

@lionelbelmon
Copy link
Author

HI Thomas,

you get the right link.

the Junit is a summary report for all comparisons, so should be dumped at the root, near the log file.

you can test if the Junit XML works well with a Jenkins Junit plug-in.

the content could be 1 test suite where each CSV comparison is a test case.

the main benefit is that you get a standardized summary reports that can be parsed by other tools and used in dashboards.

Junit_format_xml.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants