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

test: migrate client module api tests to junit 5 #4377

Merged
merged 3 commits into from
Aug 26, 2024

Conversation

sherlock-lin
Copy link
Contributor

Descriptions of the changes in this PR:

Fix #4322

Main Issue: #4322

@sherlock-lin sherlock-lin force-pushed the sherlock-migrate-to-junit5-0516 branch 2 times, most recently from bcc59bb to da302e5 Compare May 21, 2024 08:24
@sherlock-lin sherlock-lin reopened this May 21, 2024
@sherlock-lin sherlock-lin force-pushed the sherlock-migrate-to-junit5-0516 branch from da302e5 to e85971e Compare May 21, 2024 09:38
@sherlock-lin
Copy link
Contributor Author

@shoothzj

@sherlock-lin sherlock-lin force-pushed the sherlock-migrate-to-junit5-0516 branch 6 times, most recently from 407fc29 to f0aa9af Compare May 22, 2024 01:55
@sherlock-lin sherlock-lin force-pushed the sherlock-migrate-to-junit5-0516 branch from f0aa9af to 859af11 Compare May 22, 2024 07:29
Copy link
Member

@lhotari lhotari left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use JUnit5's TestInfo instead of adding custom extension.

@shoothzj
Copy link
Member

@lhotari Thanks for you remind, I remember this class too, and it has been used in

void setTestNameJunit5(TestInfo testInfo) {
testName = testInfo.getDisplayName();
}

@sherlock-lin sherlock-lin force-pushed the sherlock-migrate-to-junit5-0516 branch 2 times, most recently from 8cb695d to 2615c36 Compare May 31, 2024 01:36
Copy link
Member

@shoothzj shoothzj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor nits: I think volatile in private volatile String testName; might be useless

@sherlock-lin sherlock-lin force-pushed the sherlock-migrate-to-junit5-0516 branch from 2615c36 to 84335b9 Compare June 6, 2024 02:09
@sherlock-lin
Copy link
Contributor Author

minor nits: I think volatile in private volatile String testName; might be useless

done :)

@sherlock-lin
Copy link
Contributor Author

@lhotari help review,please

Copy link
Member

@lhotari lhotari left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@lhotari
Copy link
Member

lhotari commented Aug 23, 2024

Good work @sherlock-lin

@lhotari
Copy link
Member

lhotari commented Aug 23, 2024

I'll close and reopen to see if it passes with latest changes in master.

@lhotari lhotari closed this Aug 23, 2024
@lhotari lhotari reopened this Aug 23, 2024
@shoothzj shoothzj merged commit 4936d39 into apache:master Aug 26, 2024
45 checks passed
@shoothzj
Copy link
Member

Thanks for your contribution :)

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.

Migrate tests from junit4 to junit5
4 participants