Skip to content

Commit f4d1a16

Browse files
committed
[fix](be) Use ConfigValidatorTest fixture consistently
### What problem does this PR solve? Issue Number: None Related PR: #67228 Problem Summary: PR #67228 added a TEST case to the existing ConfigValidatorTest suite, whose other test uses TEST_F. GoogleTest requires every test in one suite to use the same fixture declaration and rejects the mixed TEST/TEST_F suite during registration. Use TEST_F for the added case as well. ### Release note None ### Check List (For Author) - Test: No need to test (one-line GoogleTest fixture declaration correction) - Behavior changed: No - Does this need documentation: No
1 parent 1ff8aba commit f4d1a16

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎be/test/common/config_validator_test.cpp‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ TEST_F(ConfigValidatorTest, Validator) {
8383
EXPECT_EQ(cfg_validator_2, 8);
8484
}
8585

86-
TEST(ConfigValidatorTest, LookupConnectionCacheBlockPoolSize) {
86+
TEST_F(ConfigValidatorTest, LookupConnectionCacheBlockPoolSize) {
8787
const auto old_value = config::get_lookup_connection_cache_block_pool_size();
8888

8989
EXPECT_TRUE(config::set_config("lookup_connection_cache_block_pool_size", "1").ok());

0 commit comments

Comments
 (0)