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

com.hazelcast.client.config.ClientTpcConfigTest mixes JUnit 4 & 5 assertions #26193

Open
JackPGreen opened this issue Dec 20, 2023 · 1 comment · May be fixed by #26265
Open

com.hazelcast.client.config.ClientTpcConfigTest mixes JUnit 4 & 5 assertions #26193

JackPGreen opened this issue Dec 20, 2023 · 1 comment · May be fixed by #26265
Labels
good first issue Good for newcomers Source: Internal PR or issue was opened by an employee Team: Core

Comments

@JackPGreen
Copy link
Contributor

JackPGreen commented Dec 20, 2023

com.hazelcast.client.config.ClientTpcConfigTest uses both org.junit.Assert.assertFalse (JUnit4) & org.junit.jupiter.api.Assertions.assertTrue (JUnit5) .

  • This should only use one version (probably JUnit4 based on the frequency of imports)
  • This should have been caught by com.hazelcast.NoMixedJUnitAnnotationsInOurTestSourcesTest.noJUnitMixing() and failed the tests

A similar scenario occurs in com.hazelcast.osgi.HazelcastOSGiIT - org.junit.experimental.categories.Category (JUnit4) & org.junit.jupiter.api.AfterEach (JUnit5)

@dr-divago
Copy link

Hi @JackPGreen is this issue still open?

@dr-divago dr-divago linked a pull request Feb 25, 2024 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers Source: Internal PR or issue was opened by an employee Team: Core
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants