-
Notifications
You must be signed in to change notification settings - Fork 451
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
[P4Tools] Clean up the P4Tools GTest infrastructure. #4841
Conversation
a518cd4
to
54528ee
Compare
54528ee
to
368e18f
Compare
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.
Few small things...
backends/p4tools/modules/testgen/targets/bmv2/test/gtest_utils.h
Outdated
Show resolved
Hide resolved
using namespace P4::literals; | ||
|
||
class P4AssertsParserTest : public P4ToolsTest {}; | ||
class P4AssertsParserTest : public ::testing::Test {}; |
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.
Is there a conflict on the testing
namespace? Or why use the global marker ::
?
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 believe this is an artifact of other tests using ::testing::Test
and things getting copied as needed.
Eg., https://github.com/p4lang/p4c/blob/main/test/gtest/bitrange.cpp#L37
I can clean these up to testing::Test
, if desired.
backends/p4tools/modules/testgen/targets/bmv2/test/gtest_utils.h
Outdated
Show resolved
Hide resolved
Signed-off-by: fruffy <fruffy@nyu.edu>
Signed-off-by: fruffy <fruffy@nyu.edu>
51dcdb2
to
4957d6f
Compare
Clean up some of the P4Testgen Gtest infrastructure
P4Tools::Test
namespace to reduce some namespace clutter.Prerequisite for #4787.