-
Notifications
You must be signed in to change notification settings - Fork 96
Increase coverage with a graveyard behavior test and unmanaged instance test #159
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
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,79 @@ | ||
/* | ||
* Copyright (c) 2012, Willow Garage, Inc. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. review the copyright There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Added a second copyright line and line about what was modified at the bottom of the license. |
||
* All rights reserved. | ||
* Copyright (c) 2020, Open Source Robotics Foundation, Inc. | ||
* | ||
* Redistribution and use in source and binary forms, with or without | ||
* modification, are permitted provided that the following conditions are met: | ||
* | ||
* * Redistributions of source code must retain the above copyright | ||
* notice, this list of conditions and the following disclaimer. | ||
* * Redistributions in binary form must reproduce the above copyright | ||
* notice, this list of conditions and the following disclaimer in the | ||
* documentation and/or other materials provided with the distribution. | ||
* * Neither the name of the Willow Garage, Inc. nor the names of its | ||
* contributors may be used to endorse or promote products derived from | ||
* this software without specific prior written permission. | ||
* | ||
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" | ||
* AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE | ||
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE | ||
* ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE | ||
* LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR | ||
* CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF | ||
* SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS | ||
* INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN | ||
* CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) | ||
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE | ||
* POSSIBILITY OF SUCH DAMAGE. | ||
* | ||
* 2020, Copied from plugins1.cpp and plugins2.cpp and changing class names | ||
*/ | ||
|
||
#include <iostream> | ||
|
||
#include "class_loader/class_loader.hpp" | ||
|
||
#include "./base.hpp" | ||
|
||
class Kangaroo : public Base | ||
{ | ||
public: | ||
void saySomething() | ||
{ | ||
printf("[Angry growl]\n"); | ||
} | ||
}; | ||
|
||
class Panda : public Base | ||
{ | ||
public: | ||
void saySomething() | ||
{ | ||
printf("[Excited squeaks!!!]\n"); | ||
} | ||
}; | ||
|
||
class Hyena : public Base | ||
{ | ||
public: | ||
void saySomething() | ||
{ | ||
printf("[Cackling laugh]\n"); | ||
} | ||
}; | ||
|
||
class Alpaca : public Base | ||
{ | ||
public: | ||
void saySomething() | ||
{ | ||
printf("hhhaaaaaaaaaa\n"); | ||
} | ||
}; | ||
|
||
|
||
CLASS_LOADER_REGISTER_CLASS(Kangaroo, Base) | ||
CLASS_LOADER_REGISTER_CLASS(Panda, Base) | ||
CLASS_LOADER_REGISTER_CLASS(Hyena, Base) | ||
CLASS_LOADER_REGISTER_CLASS(Alpaca, Base) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
The link would be this, right?
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.
I've started just linking to the full cobertura report because the statistics for a package has to be composed from multiple lines. In this case, there is coverage in the include and src directories.
I'm open to better approaches for this sort of thing though.
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.
Mmm, isn't the full coverage reported under its package folder? The fact that the coverage is tested with more packages is stated in the developer guide, IMO it should be enough.
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.
Since there are functions in the include directory, coverage for class_loader should be composed from:
https://ci.ros2.org/job/nightly_linux_coverage/lastSuccessfulBuild/cobertura/src_ros_class_loader_include_class_loader/
and
https://ci.ros2.org/job/nightly_linux_coverage/lastSuccessfulBuild/cobertura/src_ros_class_loader_src/
As described in the developer guide, the coverage statistics should include
src.*.<repository_name>.<package_name>.*
andbuild/.<repository_name>.*
(if it exists). Depending on the package that may be a lot of links to include in a single paragraph. Seeing as the number of links might grow or shrink as the package grows or shrinks, I figured it would be a lot easier to just link to the main page.