Copilot commented on code in PR #8168:
URL: https://github.com/apache/hbase/pull/8168#discussion_r3162634962


##########
hbase-server/src/test/java/org/apache/hadoop/hbase/wal/TestCompressedWAL.java:
##########
@@ -18,18 +18,20 @@
 package org.apache.hadoop.hbase.wal;
 
 import java.util.stream.Stream;
-import org.apache.hadoop.hbase.HBaseParameterizedTestTemplate;
 import org.apache.hadoop.hbase.HConstants;
 import org.apache.hadoop.hbase.testclassification.MediumTests;
 import org.apache.hadoop.hbase.testclassification.RegionServerTests;
 import org.junit.jupiter.api.AfterEach;
 import org.junit.jupiter.api.BeforeEach;
 import org.junit.jupiter.api.Tag;
+import org.junit.jupiter.params.ParameterizedClass;
 import org.junit.jupiter.params.provider.Arguments;
+import org.junit.jupiter.params.provider.MethodSource;

Review Comment:
   Same issue as the other WAL test: `@ParameterizedClass` + class-level 
`@MethodSource` are not standard JUnit Jupiter APIs for parameterization. If 
this annotation is not provided by a project-specific dependency, the test will 
not compile; if it is ignored, the tests will no longer run per-provider as 
expected (especially after converting the base tests from `@TestTemplate` to 
`@Test`). Consider moving parameterization to the test methods 
(`@ParameterizedTest`) or restoring a `@TestTemplate` setup that is known to 
work with HBase’s parameter sets.



##########
hbase-server/src/test/java/org/apache/hadoop/hbase/wal/TestCompressedWAL.java:
##########
@@ -18,18 +18,20 @@
 package org.apache.hadoop.hbase.wal;
 
 import java.util.stream.Stream;
-import org.apache.hadoop.hbase.HBaseParameterizedTestTemplate;
 import org.apache.hadoop.hbase.HConstants;
 import org.apache.hadoop.hbase.testclassification.MediumTests;
 import org.apache.hadoop.hbase.testclassification.RegionServerTests;
 import org.junit.jupiter.api.AfterEach;
 import org.junit.jupiter.api.BeforeEach;
 import org.junit.jupiter.api.Tag;
+import org.junit.jupiter.params.ParameterizedClass;
 import org.junit.jupiter.params.provider.Arguments;
+import org.junit.jupiter.params.provider.MethodSource;
 
 @Tag(RegionServerTests.TAG)
 @Tag(MediumTests.TAG)
-@HBaseParameterizedTestTemplate(name = "{index}: provider={0}")
+@ParameterizedClass(name = "{index}: provider={0}")
+@MethodSource("parameters")

Review Comment:
   Same issue as the other WAL test: `@ParameterizedClass` + class-level 
`@MethodSource` are not standard JUnit Jupiter APIs for parameterization. If 
this annotation is not provided by a project-specific dependency, the test will 
not compile; if it is ignored, the tests will no longer run per-provider as 
expected (especially after converting the base tests from `@TestTemplate` to 
`@Test`). Consider moving parameterization to the test methods 
(`@ParameterizedTest`) or restoring a `@TestTemplate` setup that is known to 
work with HBase’s parameter sets.



##########
hbase-compression/hbase-compression-zstd/src/test/java/org/apache/hadoop/hbase/io/compress/zstd/TestHFileCompressionZstd.java:
##########
@@ -86,7 +81,6 @@ public void testReconfLevels() throws Exception {
     long len_2 = FS.getFileStatus(path_2).getLen();
     LOG.info("Level 1 len {}", len_1);
     LOG.info("Level 22 len {}", len_2);
-    assertTrue("Reconfiguraton with ZSTD_LEVEL_KEY did not seem to work", 
len_1 > len_2);
+    assertTrue(len_1 > len_2, "Reconfiguraton with ZSTD_LEVEL_KEY did not seem 
to work");

Review Comment:
   Fix typo in assertion message: 'Reconfiguraton' → 'Reconfiguration'.
   



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to