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

xunit.xml test results not found in --test-result-base #105

Open
Aposhian opened this issue Jun 28, 2021 · 4 comments
Open

xunit.xml test results not found in --test-result-base #105

Aposhian opened this issue Jun 28, 2021 · 4 comments

Comments

@Aposhian
Copy link

#79 copies CTest Test.xml files over to the directory specified by --test-result-base, but not the *.xunit.xml result files. Since I am looking for my xunit "test results", the following documentation is misleading to me:

The base path for all test results. The default value is the --build-base argument. Each package uses a subdirectory in that base path as its package specific test result directory.

https://colcon.readthedocs.io/en/released/reference/verb/test.html

It seems like *.xunit.xml files should be copied over as well, or the documentation could be clarified.

@hidmic
Copy link
Contributor

hidmic commented Sep 10, 2021

Perhaps documentation promises too much. colcon through colcon-cmake supports CTest. It doesn't (and cannot) account for whatever output those tests may generate. There isn't even a convention (e.g. a CMake variable) to be leveraged. So I agree documentation should warn that the set of test results may vary with each colcon extension supporting the test verb.

CC @dirk-thomas for feedback.

@dirk-thomas
Copy link
Member

colcon can only handle what it knows about. So rephrasing the documentation to make this explicit is probably the best approach.

@hidmic
Copy link
Contributor

hidmic commented Sep 17, 2021

@Aposhian would you contribute a patch to docs?

@Aposhian
Copy link
Author

Yes I can do that.

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

No branches or pull requests

3 participants