Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JUnit5 support #18733

Open
kennknowles opened this issue Jun 3, 2022 · 4 comments
Open

JUnit5 support #18733

kennknowles opened this issue Jun 3, 2022 · 4 comments

Comments

@kennknowles
Copy link
Member

Imported from Jira BEAM-3415. Original Jira may contain additional context.
Reported by: romain.manni-bucau.

@IraRe
Copy link

IraRe commented Mar 9, 2023

We're looking forward to this feature for some time already. Are there any updates on the topic?

@kennknowles
Copy link
Member Author

Can you share more about how you want to use it? I think the Beam testing utilities include some JUnit4 utilities (like TestPipeline, and then also some hamcrest matchers. Maybe it would make sense to build a separate JUnit5 version of these while keeping the JUnit4 versions for compatibility with existing uses?

@the-serious-programmer
Copy link

Just starting out with testing my apache beam pipeline. Must say I am pretty surprised this is still depending on Junit 4.
Junit 5 has been out for a while now and Junit 4 is outdated.

@younes-d
Copy link

younes-d commented Feb 6, 2025

Is anyone actively working on adding JUnit5 support to Beam?

In TestPipeline,

import org.junit.rules.TestRule;
import org.junit.runner.Description;
import org.junit.runners.model.Statement;

are deprecated in JUnit5

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

No branches or pull requests

5 participants