-
Notifications
You must be signed in to change notification settings - Fork 47
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
Add init options API test coverage. #108
Conversation
Signed-off-by: Michel Hidalgo <[email protected]>
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.
How are you monitoring coverage with these testing jobs? Is it even possible?
I believe it is possible if I run Linux CI jobs with coverage enabled. Haven't been doing so consistently though. Too many issues with the API itself and implementations made me shift focus. |
Also relevant. I can only test as far as the API contract goes, regardless of the implementation. |
Signed-off-by: Michel Hidalgo <[email protected]>
I'll hold off merging this until I've re-released RMWs so that |
@ros-pull-request-builder retest this please |
Going in! |
Signed-off-by: Michel Hidalgo <[email protected]>
Signed-off-by: Michel Hidalgo <[email protected]>
Needs ros2/rmw_fastrtps#399, ros2/rmw_connext#431 and ros2/rmw_cyclonedds#200.