Skip to content

8368091: Use JUnit Jupiter API in sun/net/ext, sun/net/www and sun/net/spi tests#30645

Closed
mahendrachhipa wants to merge 3 commits intoopenjdk:masterfrom
mahendrachhipa:JDK-8368091
Closed

8368091: Use JUnit Jupiter API in sun/net/ext, sun/net/www and sun/net/spi tests#30645
mahendrachhipa wants to merge 3 commits intoopenjdk:masterfrom
mahendrachhipa:JDK-8368091

Conversation

@mahendrachhipa
Copy link
Copy Markdown
Member

@mahendrachhipa mahendrachhipa commented Apr 9, 2026

Following tests are refactored to use JUnit Jupiter API :
sun/net/ext/ExtendedSocketOptionsTest.java
sun/net/www/protocol/file/DirPermissionDenied.java
sun/net/www/protocol/jar/MultiReleaseJarURLConnection.java
sun/net/www/protocol/jrt/Basic.java
sun/net/www/protocol/http/TestTransparentNTLM.java
sun/net/www/protocol/http/HttpHeaderParserTest.java
sun/net/www/http/RequestMethodCheck/RequestMethodEquality.java
sun/net/www/http/KeepAliveStreamCleaner/java.base/sun/net/www/http/KeepAliveStreamCleanerTest.java
sun/net/www/http/KeepAliveStreamCleaner/KeepAliveStreamCleanerTestDriver.java
sun/net/www/MessageHeaderTest.java
sun/net/spi/DefaultProxySelectorTest.java


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-8368091: Use JUnit Jupiter API in sun/net/ext, sun/net/www and sun/net/spi tests (Sub-task - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 30645

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link
Copy Markdown

bridgekeeper bot commented Apr 9, 2026

👋 Welcome back mchhipa! 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
Copy Markdown

openjdk bot commented Apr 9, 2026

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

8368091: Use JUnit Jupiter API in sun/net/ext, sun/net/www and sun/net/spi tests

Reviewed-by: dfuchs

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 50 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 changed the title JDK-8368091: Use JUnit Jupiter API in sun/net/ext, sun/net/www and su… 8368091: Use JUnit Jupiter API in sun/net/ext, sun/net/www and sun/net/spi tests Apr 9, 2026
@openjdk openjdk bot added the net net-dev@openjdk.org label Apr 9, 2026
@openjdk
Copy link
Copy Markdown

openjdk bot commented Apr 9, 2026

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

  • net

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 Apr 9, 2026
@mlbridge
Copy link
Copy Markdown

mlbridge bot commented Apr 9, 2026

Webrevs

Comment thread test/jdk/sun/net/ext/ExtendedSocketOptionsTest.java Outdated
try {
selector.select(null);
Assert.fail("select() was expected to fail for null URI");
fail("select() was expected to fail for null URI");
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

we could simplify and use assertThrows here, and in other places/files as well

Comment thread test/jdk/sun/net/www/protocol/http/HttpHeaderParserTest.java Outdated
public class HttpHeaderParserTest {
@DataProvider(name = "responses")
public Object[][] responses() {
public static Object[][] responses() {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Consider simplifying the method to use List.of and simply return List<String>

Comment thread test/jdk/sun/net/ext/ExtendedSocketOptionsTest.java Outdated
try {
selector.select(uri);
Assert.fail("select() was expected to fail for URI " + uri);
fail("select() was expected to fail for URI " + uri);
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Same here. Use assertThrows, even consider removind this method.

Copy link
Copy Markdown

@Marcono1234 Marcono1234 left a comment

Choose a reason for hiding this comment

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

Hopefully these comments are useful, if not please let me know. They are only suggestions; feel free to ignore them, I am not an OpenJDK member.

Comment thread test/jdk/sun/net/www/protocol/file/DirPermissionDenied.java
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Use JUnit's fail(...) instead of assertTrue(false, ...)?

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Use assertNotNull?

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Use assertNotEquals?

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Not directly related to JUnit changes, but use canonical way to write array type here?

- String expected[]
+ String[] expected

@openjdk openjdk bot added rfr Pull request is ready for review and removed rfr Pull request is ready for review labels Apr 10, 2026
Copy link
Copy Markdown
Member

@dfuch dfuch left a comment

Choose a reason for hiding this comment

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

LGTM. Don't forget to log a new task for revisiting DirPermissionDenied.java.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Apr 13, 2026
@mahendrachhipa
Copy link
Copy Markdown
Member Author

/integrate

@openjdk
Copy link
Copy Markdown

openjdk bot commented Apr 13, 2026

Going to push as commit 9d6a94e.
Since your change was applied there have been 54 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 Apr 13, 2026
@openjdk openjdk bot closed this Apr 13, 2026
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Apr 13, 2026
@openjdk
Copy link
Copy Markdown

openjdk bot commented Apr 13, 2026

@mahendrachhipa Pushed as commit 9d6a94e.

💡 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 net net-dev@openjdk.org

Development

Successfully merging this pull request may close these issues.

3 participants