Skip to content

[WIP] removing rviz plugins from test coverage since its not a production run-time component#1953

Merged
SteveMacenski merged 2 commits intomainfrom
rviz_rm
Aug 18, 2020
Merged

[WIP] removing rviz plugins from test coverage since its not a production run-time component#1953
SteveMacenski merged 2 commits intomainfrom
rviz_rm

Conversation

@SteveMacenski
Copy link
Copy Markdown
Member

#1810

We exclude navigation system tests because they're not run-time tools use on someone's robot during an actual use. The rviz plugins are a similar analog, only used for entry level testing, not used when actually on someone's robot for use. We should consider if it makes sense to exclude this as well.

CC @naiveHobo - thoughts?

@SteveMacenski
Copy link
Copy Markdown
Member Author

@SteveMacenski SteveMacenski merged commit f07c1ee into main Aug 18, 2020
@SteveMacenski SteveMacenski deleted the rviz_rm branch August 18, 2020 01:14
@naiveHobo
Copy link
Copy Markdown
Contributor

Ah, little late to the party but I agree here. Haven't been able to find a good way to write tests for the rviz plugins that actually test the functionality and as you said, they won't be used on actual robots.

@SteveMacenski
Copy link
Copy Markdown
Member Author

Awesome, sounds like we're in full agreement then, Ruffin also agrees

ruffsl pushed a commit to ruffsl/navigation2 that referenced this pull request Jul 2, 2021
…tion run-time component (ros-navigation#1953)

* removing rviz plugins from test coverage since its not a production run-time component

* Update code_coverage_report.bash
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