Skip to content

Generate xunit files valid for the junit10.xsd#225

Merged
j-rivero merged 1 commit intomasterfrom
junit10_xsd
Mar 11, 2020
Merged

Generate xunit files valid for the junit10.xsd#225
j-rivero merged 1 commit intomasterfrom
junit10_xsd

Conversation

@j-rivero
Copy link
Copy Markdown

Following ament/ament_lint#220 . Same rationale, in this case just change skip by skipped

@j-rivero j-rivero requested a review from dirk-thomas March 11, 2020 17:58
Signed-off-by: Jose Luis Rivero <jrivero@osrfoundation.org>
@dirk-thomas
Copy link
Copy Markdown
Contributor

Actually shouldn't it be failures="" errors="%d" then since the test failed to generated the expected test result?

@j-rivero
Copy link
Copy Markdown
Author

Actually shouldn't it be failures="" errors="%d" then since the test failed to generated the expected test result?

I agree with this in the case of _generate_results() is being called in the presence of problems affecting the own testing code (I think that this is being done in https://github.com/ament/ament_cmake/blob/master/ament_cmake_test/ament_cmake_test/__init__.py#L104). I see more points in the code where _generate_results() is being called and probably they are not related to test code problems.

In that case the current form is valid, in the first scenario you are right, errors="%d" failures="0" should be more close to the specification.

@j-rivero
Copy link
Copy Markdown
Author

I agree with this in the case of _generate_results() is being called in the presence of problems affecting the own testing code (I think that this is being done in https://github.com/ament/ament_cmake/blob/master/ament_cmake_test/ament_cmake_test/__init__.py#L104). I see more points in the code where _generate_results() is being called and probably they are not related to test code problems.

In that case the current form is valid, in the first scenario you are right, errors="%d" failures="0" should be more close to the specification.

I'll follow this in a new PR with some code changes.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants