Skip to content

[FLINK-39527][test] Migrate flink-end-to-end-tests to JUnit 5#28040

Open
mateczagany wants to merge 1 commit intoapache:masterfrom
mateczagany:FLINK-39527
Open

[FLINK-39527][test] Migrate flink-end-to-end-tests to JUnit 5#28040
mateczagany wants to merge 1 commit intoapache:masterfrom
mateczagany:FLINK-39527

Conversation

@mateczagany
Copy link
Copy Markdown
Contributor

What is the purpose of the change

Update flink-end-to-end-tests module to use only JUnit 5 instead of JUnit 4

Brief change log

  • Migrated assertions to use AssertJ
  • Limited visibility of classes/methods/fields where I could
  • Upgraded Prometheus E2E test to use newer release, to make it work on ARM-based MacOS
  • Replaced JUnit 4 runners with JUnit 5 extensions, such as FlinkResourceExtension and DownloadCacheExtension

Verifying this change

  • The PR should pass all CI checks

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

Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

@flinkbot
Copy link
Copy Markdown
Collaborator

flinkbot commented Apr 27, 2026

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants