Skip to content

8373798: Refactor java/math tests to use JUnit#28848

Closed
rgiulietti wants to merge 1 commit intoopenjdk:masterfrom
rgiulietti:8373798
Closed

8373798: Refactor java/math tests to use JUnit#28848
rgiulietti wants to merge 1 commit intoopenjdk:masterfrom
rgiulietti:8373798

Conversation

@rgiulietti
Copy link
Contributor

@rgiulietti rgiulietti commented Dec 16, 2025

Replace testng framework with junit


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8373798: Refactor java/math tests to use JUnit (Sub-task - P4)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28848/head:pull/28848
$ git checkout pull/28848

Update a local copy of the PR:
$ git checkout pull/28848
$ git pull https://git.openjdk.org/jdk.git pull/28848/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28848

View PR using the GUI difftool:
$ git pr show -t 28848

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28848.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Dec 16, 2025

👋 Welcome back rgiulietti! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Dec 16, 2025

@rgiulietti This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8373798: Refactor java/math tests to use JUnit

Reviewed-by: darcy

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 17 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@openjdk openjdk bot added the core-libs core-libs-dev@openjdk.org label Dec 16, 2025
@openjdk
Copy link

openjdk bot commented Dec 16, 2025

@rgiulietti The following label will be automatically applied to this pull request:

  • core-libs

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added the rfr Pull request is ready for review label Dec 16, 2025
@mlbridge
Copy link

mlbridge bot commented Dec 16, 2025

Webrevs

("NumberFormatException should not have a cause");
} else {
throw nfe;
}
Copy link
Contributor

Choose a reason for hiding this comment

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

If you want, you could use NumberFormatException nfe = assertThrows(..) here, then assert the cause. That would avoid mixing JUnit asserts with explicit throw of RuntimeException.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's just the result of a mechanical conversion of the original testng-based code.

Copy link
Contributor

Choose a reason for hiding this comment

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

Okay, but you could go the extra mile and replace the throw of RuntimeException as it looks very strange to have the test be a JUnit test and still have this.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It is my plan to review all numerics related tests, rewriting some of those that do not use any framework to use junit in the end.
For now, the priority is to remove the dependencies on testng.

Copy link
Member

@jddarcy jddarcy left a comment

Choose a reason for hiding this comment

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

Looks fine.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Dec 16, 2025
@rgiulietti
Copy link
Contributor Author

/integrate

@openjdk
Copy link

openjdk bot commented Dec 17, 2025

Going to push as commit fc76403.
Since your change was applied there have been 35 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Dec 17, 2025
@openjdk openjdk bot closed this Dec 17, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Dec 17, 2025
@openjdk
Copy link

openjdk bot commented Dec 17, 2025

@rgiulietti Pushed as commit fc76403.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

@rgiulietti rgiulietti deleted the 8373798 branch December 17, 2025 09:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core-libs core-libs-dev@openjdk.org integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

3 participants