-
Notifications
You must be signed in to change notification settings - Fork 30
Update compiler tests to use JUnit instead of TestNG #566
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
Conversation
👋 Welcome back mabbay! A progress list of the required criteria for merging this PR into |
@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:
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
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 |
Webrevs
|
There was a problem hiding this 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.
test/langtools/tools/javac/reflect/quoted/TestCaptureQuoted.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this 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 |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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")
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or that :-)
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? |
import org.junit.jupiter.params.provider.MethodSource; | ||
|
||
import static org.testng.Assert.*; | ||
import java.util.stream.IntStream; |
There was a problem hiding this comment.
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); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
/integrate |
Going to push as commit 37ab07b.
Your commit was automatically rebased without conflicts. |
Update compiler tests to use JUnit instead of TestNG.
Progress
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