Skip to content

Conversation

mabbay
Copy link
Member

@mabbay mabbay commented Sep 12, 2025

Update compiler tests to use JUnit instead of TestNG.


Progress

  • Change must not contain extraneous whitespace

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 566

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/babylon/pull/566.diff

Using Webrev

Link to Webrev Comment

@mabbay mabbay self-assigned this Sep 12, 2025
@bridgekeeper
Copy link

bridgekeeper bot commented Sep 12, 2025

👋 Welcome back mabbay! A progress list of the required criteria for merging this PR into code-reflection 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 Sep 12, 2025

@mabbay 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:

Update compiler tests to use JUnit instead of TestNG

Reviewed-by: psandoz, mcimadamore

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 36 new commits pushed to the code-reflection 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 code-reflection branch, type /integrate in a new comment.

@openjdk openjdk bot added ready Pull request is ready to be integrated rfr Pull request is ready for review labels Sep 12, 2025
@mlbridge
Copy link

mlbridge bot commented Sep 12, 2025

Webrevs

Copy link
Member

@PaulSandoz PaulSandoz left a comment

Choose a reason for hiding this comment

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

One area we need to pay special attention to is the order of arguments of assert methods. junit and testng switch the order actual and expected parameters of such methods.

Copy link
Collaborator

@mcimadamore mcimadamore left a comment

Choose a reason for hiding this comment

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

Aside from @PaulSandoz comment, PR looks good

"TestCaptureQuotable.java", // plain testng test
"QuotedSameInstanceTest.java", // plain testng test
"CodeModelSameInstanceTest.java" // plain testng test
"TestLocalCapture.java", // plain junit test
Copy link
Collaborator

Choose a reason for hiding this comment

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

When looking again at this, it would perhaps be beneficial to put all the IR tests in a separate folder. It seems a bit sad that whenever we add a "plain" test we have to come back and list it here.

The exclusion for SuperTest/LocalClassTest of course make more sense, so it's ok for them to stay.

Copy link
Collaborator

Choose a reason for hiding this comment

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

(for the records, I'm not suggesting we tackle this in this PR -- more noting for "future work")

Copy link
Member Author

Choose a reason for hiding this comment

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

Actually, "plain" test should be in the runtime tests directory.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Or that :-)

@mabbay
Copy link
Member Author

mabbay commented Sep 15, 2025

One area we need to pay special attention to is the order of arguments of assert methods. junit and testng switch the order actual and expected parameters of such methods.

Yes. But It won't affect the test result, right ?

@mcimadamore
Copy link
Collaborator

One area we need to pay special attention to is the order of arguments of assert methods. junit and testng switch the order actual and expected parameters of such methods.

Yes. But It won't affect the test result, right ?

In the case of assertEquals, probably not -- but it might result in confusing error messages. You might try to provoke a failure and compare before/after?

@mabbay mabbay changed the title Use JUnit instead of TestNG Update compiler tests to use JUnit instead of TestNG Sep 15, 2025
import org.junit.jupiter.params.provider.MethodSource;

import static org.testng.Assert.*;
import java.util.stream.IntStream;
Copy link
Member

Choose a reason for hiding this comment

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

Suggestion: use IntelliJ to reorder your imports.

.mapToObj(i -> new Object[] { i })
.toArray(Object[][]::new);
public static IntStream ints() {
return IntStream.range(0, 50);
Copy link
Member

Choose a reason for hiding this comment

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

Nice!

@mabbay
Copy link
Member Author

mabbay commented Sep 22, 2025

/integrate

@openjdk
Copy link

openjdk bot commented Sep 22, 2025

Going to push as commit 37ab07b.
Since your change was applied there have been 36 commits pushed to the code-reflection branch:

Your commit was automatically rebased without conflicts.

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

openjdk bot commented Sep 22, 2025

@mabbay Pushed as commit 37ab07b.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

3 participants