[FLINK-27936][tests] Migrate flink-connector-cassandra to JUnit5
What is the purpose of the change
Migrate WriteAheadSinkTestBase and flink-connector-cassandra module to AssertJ and JUnit 5 following the JUnit 5 Migration Guide
Brief change log
Use JUnit5 and AssertJ in tests instead of JUnit4 and Hamcrest
Verifying this change
This change is a code cleanup without any test coverage.
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)
CI report:
- 8eb8f795e822aafad2604efddab37c51d1bd27c2 Azure: SUCCESS
Bot commands
The @flinkbot bot supports the following commands:@flinkbot run azurere-run the last Azure build
@flinkbot run azure
@flinkbot run azure
@flinkbot run azure
@flinkbot run azure
@flinkbot run azure
@flinkbot run azure
@flinkbot run azure
I also rebased to the latest master to avoid FLINK-29161
The CI test failure is most likely connected to FLINK-29093
@flinkbot run azure