@@ -578,12 +578,13 @@ <h3 id="pkcs11-tests">PKCS11 Tests</h3>
578578< p > For more notes about the PKCS11 tests, please refer to
579579test/jdk/sun/security/pkcs11/README.</ p >
580580< h3 id ="client-ui-tests "> Client UI Tests</ h3 >
581+ < h4 id ="system-key-shortcuts "> System key shortcuts</ h4 >
581582< p > Some Client UI tests use key sequences which may be reserved by the
582583operating system. Usually that causes the test failure. So it is highly
583584recommended to disable system key shortcuts prior testing. The steps to
584585access and disable system key shortcuts for various platforms are
585586provided below.</ p >
586- < h4 id ="macos "> MacOS </ h4 >
587+ < h5 id ="macos "> macOS </ h5 >
587588< p > Choose Apple menu; System Preferences, click Keyboard, then click
588589Shortcuts; select or deselect desired shortcut.</ p >
589590< p > For example,
@@ -594,17 +595,41 @@ <h4 id="macos">MacOS</h4>
594595shortcut should be disabled using the steps described above, and then
595596deselect "Turn keyboard access on or off" option which is responsible
596597for < code > CTRL + F1</ code > combination.</ p >
597- < h4 id ="linux "> Linux</ h4 >
598+ < h5 id ="linux "> Linux</ h5 >
598599< p > Open the Activities overview and start typing Settings; Choose
599600Settings, click Devices, then click Keyboard; set or override desired
600601shortcut.</ p >
601- < h4 id ="windows "> Windows</ h4 >
602+ < h5 id ="windows "> Windows</ h5 >
602603< p > Type < code > gpedit</ code > in the Search and then click Edit group
603604policy; navigate to User Configuration -> Administrative Templates
604605-> Windows Components -> File Explorer; in the right-side pane
605606look for "Turn off Windows key hotkeys" and double click on it; enable
606607or disable hotkeys.</ p >
607608< p > Note: restart is required to make the settings take effect.</ p >
609+ < h4 id ="robot-api "> Robot API</ h4 >
610+ < p > Most automated Client UI tests use < code > Robot</ code > API to control
611+ the UI. Usually, the default operating system settings need to be
612+ adjusted for Robot to work correctly. The detailed steps how to access
613+ and update these settings for different platforms are provided
614+ below.</ p >
615+ < h5 id ="macos-1 "> macOS</ h5 >
616+ < p > < code > Robot</ code > is not permitted to control your Mac by default
617+ since macOS 10.15. To allow it, choose Apple menu -> System Settings,
618+ click Privacy & Security; then click Accessibility and ensure the
619+ following apps are allowed to control your computer: < em > Java</ em > and
620+ < em > Terminal</ em > . If the tests are run from an IDE, the IDE should be
621+ granted this permission too.</ p >
622+ < h5 id ="windows-1 "> Windows</ h5 >
623+ < p > On Windows if Cygwin terminal is used to run the tests, there is a
624+ delay in focus transfer. Usually it causes automated UI test failure. To
625+ disable the delay, type < code > regedit</ code > in the Search and then
626+ select Registry Editor; navigate to the following key:
627+ < code > HKEY_CURRENT_USER\Control Panel\Desktop</ code > ; make sure the
628+ < code > ForegroundLockTimeout</ code > value is set to 0.</ p >
629+ < p > Additional information about Client UI tests configuration for
630+ various operating systems can be obtained at < a
631+ href ="https://wiki.openjdk.org/display/ClientLibs/Automated+client+GUI+testing+system+set+up+requirements "> Automated
632+ client GUI testing system set up requirements</ a > </ p >
608633< h2 id ="editing-this-document "> Editing this document</ h2 >
609634< p > If you want to contribute changes to this document, edit
610635< code > doc/testing.md</ code > and then run
0 commit comments