-
Notifications
You must be signed in to change notification settings - Fork 53
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
Run colcon-coveragepy-result to collect all Python coverage data #247
Run colcon-coveragepy-result to collect all Python coverage data #247
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM once ros-tooling/setup-ros#208 and released so we can pin the version and test against it.
0.0.25 is released with the required patch |
@thomas-moulard I've opened #253 for the bump to |
@christophebedard could you please resolve any conflicts now that #253 is in |
Signed-off-by: Christophe Bedard <bedard.christophe@gmail.com>
Signed-off-by: Christophe Bedard <bedard.christophe@gmail.com>
…mple Signed-off-by: Christophe Bedard <bedard.christophe@gmail.com>
@piraka9011 done. I rebased. |
colcon-coveragepy-result
collects the Python coverage data for pure Python packages and for CMake packages with Python code (i.e.ros.ament_cmake
, see ament/ament_cmake#226) and combines it all into one file (coveragepy/.coverage
relative to the workspace).I also added an example to the README which uses the
coverage-pytest
mixin. This is both abuild
and atest
mixin (forros.ament_cmake
packages and pure Python packages, respectively).Part of #238
Requires ros-tooling/setup-ros#208
Note: I'm not entirely sure why I have all these changes; I think I have the right packages/versions.