-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
JDK-8279641: Create manual JTReg tests for Swing accessibility #6993
Conversation
👋 Welcome back shurailine! A progress list of the required criteria for merging this PR into |
@shurymury 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. |
@prrace Can you take a look? |
An initial question, which look and feel are we expected to test? Do we need to cover the default one, or it is up to someone to pass the correct L&F? |
Need in what context ? Who is "we" ? |
This current implementation does not do anything to support different LAFs. A test executor can still specify the LAF through -vmoption:"-Dswing.defaultlaf=..." JTReg option. |
Even if the tests do nothing it is expected that these tests will pass on the default L&Fs like Aqua/Metal. If it is expected to pass on all L&F why not iterate over all installed L&F and prove that? BTW I am not sure that the metal l&f will work properly on macOS, does anybody test a11y for it? |
Changes suggested by this review only cover default LAF by default, unless LAF is specified explicitly. There may be improvements later which would suggest rotating LAFs, that would be a subject of a follow-up reviews. |
@shurymury 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 155 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 5523dde.
Your commit was automatically rebased without conflicts. |
@shurymury Pushed as commit 5523dde. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Tests are based on SwingSet2 application.
Test instructions are loaded from HTML files.
See readme for more info.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/6993/head:pull/6993
$ git checkout pull/6993
Update a local copy of the PR:
$ git checkout pull/6993
$ git pull https://git.openjdk.java.net/jdk pull/6993/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 6993
View PR using the GUI difftool:
$ git pr show -t 6993
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/6993.diff