Alwaysgaurav1 opened a new pull request, #29111:
URL: https://github.com/apache/flink/pull/29111

   ## What is the purpose of the change
   
   This pull request migrates legacy JUnit 4 and Hamcrest test assertions in 
`flink-statebackend-rocksdb` to JUnit 5 (Jupiter) and AssertJ in accordance 
with Apache Flink test standards.
   
   ## Brief change log
   
   - Migrated `RocksDBMemoryControllerUtilsTest` to JUnit 5 (`@TempDir`, 
`@BeforeAll`) and AssertJ assertions.
   - Migrated `RocksDBResourceContainerTest` to JUnit 5 and AssertJ assertions.
   - Migrated `RocksDBWriteBatchWrapperTest` to JUnit 5 and 
`assertThatThrownBy(...)` / AssertJ assertions.
   - Migrated `RocksDBNativeMetricOptionsTest` to JUnit 5 and AssertJ 
assertions.
   
   ## Verifying this change
   
   This change is a code refactoring of test suites without any changes to 
existing production runtime logic.
   
   - Run maven tests:
     `mvn test -pl flink-state-backends/flink-statebackend-rocksdb -am -Dfast 
-Dtest=RocksDBMemoryControllerUtilsTest,RocksDBResourceContainerTest,RocksDBWriteBatchWrapperTest,RocksDBNativeMetricOptionsTest
 -Dsurefire.failIfNoSpecifiedTests=false`
   - All 30 tests pass cleanly with 0 failures and 0 errors.
   
   ## Does this pull request potentially affect one of the following parts:
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? not applicable


-- 
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