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

Update unit tests to support both old and new GTest versions #3677

Merged

Conversation

shrijitsingh99
Copy link
Contributor

@shrijitsingh99 shrijitsingh99 commented Feb 25, 2020

An updated PR which builds upon #3419 and fixes the remaining issues
Fixes #3373 , closes #3419
Credits to @jammm, all of the work was already done by him, I just had to fix some minor issues

Copy link
Member

@kunaltyagi kunaltyagi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct me if I'm wrong, but I think this is the only unaddressed item from the prev PR

test/include/pcl/test/test_macros.h Outdated Show resolved Hide resolved
@kunaltyagi kunaltyagi added changelog: enhancement Meta-information for changelog generation module: test needs: more work Specify why not closed/merged yet labels Feb 25, 2020
Copy link
Member

@kunaltyagi kunaltyagi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, pending CI. Don't wait on my approval for merge since Sergio was taking point on this before 😄

@kunaltyagi kunaltyagi added needs: code review Specify why not closed/merged yet and removed needs: more work Specify why not closed/merged yet labels Feb 25, 2020
@kunaltyagi kunaltyagi dismissed their stale review February 25, 2020 23:11

not point person

@taketwo
Copy link
Member

taketwo commented Feb 26, 2020

Sorry, me again with header naming suggestions 🤷‍♂️

As was agreed in the other discussion (#3654), umbrella-named headers like "xxx_macros" are not desirable. In the case at hand, I believe a more suitable name would be "pcl/test/gtest.h". Indeed, the file is nothing else but include of GTest plus a compatibility layer to support older versions. The fact that this compatibility layer is implemented through macros is not important.

@SergioRAgostinho
Copy link
Member

@shrijitsingh99 Incorporate @taketwo's comment regarding file renaming and I'll review it after.

@SergioRAgostinho SergioRAgostinho self-assigned this Feb 26, 2020
@shrijitsingh99
Copy link
Contributor Author

@shrijitsingh99 Incorporate @taketwo's comment regarding file renaming and I'll review it after.

Renamed the file as @taketwo suggested

Copy link
Member

@SergioRAgostinho SergioRAgostinho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@PointCloudLibrary/maintainers would you mind if I squash everything up despite the multiple authors? I don't believe this fix is worth more than a single commit.

Edit: by the way. What's the current established label for me waiting for other maintainers to chime? It used to be needs: decision, but that one is no longer part of the label pool.

@SergioRAgostinho SergioRAgostinho removed the needs: code review Specify why not closed/merged yet label Feb 26, 2020
@taketwo
Copy link
Member

taketwo commented Feb 26, 2020

From maintainer perspective yes, please squash. Maybe add contributors' names to the commit message.

What's the current established label for me waiting for other maintainers to chime?

We abolished it. Is there a need? What's the difference to "needs: review"? We can introduce "needs: maintainers feedback".

@SergioRAgostinho
Copy link
Member

In my mind needing a review means full code review, feedback is to just chime in on a specific topic. While navigating through the issue list it helps me distil both. Did the meaning for needs: review also change?

@SergioRAgostinho SergioRAgostinho merged commit 4316e11 into PointCloudLibrary:master Feb 26, 2020
@taketwo
Copy link
Member

taketwo commented Feb 26, 2020

Did the meaning for needs: review also change?

No, it's still the same.

feedback is to just chime in on a specific topic.

OK, understood.

I just wanted to compress the label set, which implies a bit of meaning overloading... In this case the difference is too large though. Let's have "needs: maintainers feedback/opinions"?

@SunBlack
Copy link
Contributor

Just a hint: #include <gtest/gtest.h> is not required anymore as it is always includes via #include <pcl/test/gtest.h> now

@kunaltyagi
Copy link
Member

Let's have "needs: maintainers feedback/opinions"?

Added the label.

#include <gtest/gtest.h> is not required anymore

Ah yeah, I guess I'll create an issue of that

@kunaltyagi kunaltyagi mentioned this pull request Mar 12, 2020
22 tasks
@shrijitsingh99 shrijitsingh99 deleted the gtest-deprecated branch March 12, 2020 20:52
FSund pushed a commit to FSund/pcl that referenced this pull request Mar 16, 2020
…est versions (PointCloudLibrary#3677)

Co-authored-by:
Aaryaman Vasishta @jammm <jem456.vasishta@gmail.com>
Shrijit Singh @shrijitsingh99 <shrijitsingh99@gmail.com>
@taketwo taketwo changed the title Update TYPED_TEST_CASE to TYPED_TEST_SUITE with fallback for older GTest versions Update unit tests to support both old and new GTest versions Mar 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog: enhancement Meta-information for changelog generation module: test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

GTest deprecated TYPED_TEST_CASE
6 participants