-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8318613: ChoiceFormat patterns are not well tested #16324
8318613: ChoiceFormat patterns are not well tested #16324
Conversation
👋 Welcome back jlu! A progress list of the required criteria for merging this PR into |
@justin-curtis-lu The following label will be automatically applied to this pull request:
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. |
Webrevs
|
public void validPatternsTest(String pattern) { | ||
assertDoesNotThrow( ()-> new ChoiceFormat(pattern), | ||
"Valid pattern should not have thrown an exception"); | ||
} |
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 those valid cases, it may be helpful to actually format some edge cases, and check the results, especially for those odd ones. Or compare the parsed arrays.
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.
Good point, added some code to actually compare the formatted values to the expected results as suggested.
|
||
public class PatternsTest { | ||
|
||
private static final String err1 = |
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.
Nit: static constants should be uppercased.
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.
LGTM
@justin-curtis-lu 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 61 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 |
/integrate |
Going to push as commit 10427c0.
Your commit was automatically rebased without conflicts. |
@justin-curtis-lu Pushed as commit 10427c0. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review this PR which adds a test for ChoiceFormat intended to test a wide range of ChoiceFormat patterns.
The existing test Bug4387255 only tests a singular basic pattern and does not test for incorrect patterns either.
The new test checks
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/16324/head:pull/16324
$ git checkout pull/16324
Update a local copy of the PR:
$ git checkout pull/16324
$ git pull https://git.openjdk.org/jdk.git pull/16324/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 16324
View PR using the GUI difftool:
$ git pr show -t 16324
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/16324.diff
Webrev
Link to Webrev Comment