On Mon, 7 Mar 2022 23:31:54 GMT, lawrence.andrews wrote:
> Following methods are covered in this testcase
> getAccessibleAction()
> getAccessibleActionCount()
> doAccessibleAction(int direction)
>
> @shurymury
This pull request has now been integrated.
Changeset: 8db5247e
Author:lawrence.
On Mon, 23 May 2022 18:00:39 GMT, Alexandre Iline
wrote:
>> Before the fix the test was failing around 1 time in fifty runs. After the
>> fix the test did not fail in ~ 1k runs.
>> Additional instrumentation is added to save useful information on the UI
>> state, should the failure happen agai
On Wed, 27 Apr 2022 00:06:41 GMT, lawrence.andrews
wrote:
> 1) Fixed Parser error by removing yesno from @run main/manual=yesno
> 2) Used PassFaileJFrame to show the test instruction to the user instead of
> printing the test instruction on the console or jtreg log file.
> 3) If printer is n
> 1) Fixed Parser error by removing yesno from @run main/manual=yesno
> 2) Used PassFaileJFrame to show the test instruction to the user instead of
> printing the test instruction on the console or jtreg log file.
> 3) If printer is not configured then mark the test as passed.
>
> @shurymury
On Mon, 25 Apr 2022 22:36:59 GMT, lawrence.andrews
wrote:
> 1) Removed yesno to eliminate parserException
> 2) Added code to fit into manual framework so that timeout, pass & fail is
> handled.
> 3) Added code to mark the test as pass if printer service is not available
> 4) Added code to handl
On Fri, 29 Apr 2022 22:39:28 GMT, lawrence.andrews
wrote:
> 1) Removed Applet dependent code and used Frame as top level.
> 2) Automated the manual test.
>
> @shurymury
This pull request has now been integrated.
Changeset: 44a60ce1
Author:lawrence.andrews
Committer: Phil Race
URL:
On Mon, 4 Apr 2022 23:39:33 GMT, lawrence.andrews wrote:
> 1) Modified ManualTestFrame.java to support non SwingSet2 and this include
> modification of SwingSetTest.java
> 2) Added new TestJProgressBarAccessibility.java testcase that uses
> ManualTestFrame
> 3) Added timeout support in case us
> 1) Removed Applet dependent code and used Frame as top level.
> 2) Automated the manual test.
>
> @shurymury
lawrence.andrews has updated the pull request incrementally with one additional
commit since the last revision:
Fixed disposing of frame with in EDT
-
Changes:
- all:
1) Removed Applet dependent code and used Frame as top level.
2) Automated the manual test.
@shurymury
-
Commit messages:
- 8285867 : Convert applet manual tests SelectionVisible.java to Frame and
automate
Changes: https://git.openjdk.java.net/jdk/pull/8477/files
Webrev: https://
> 1) Fixed Parser error by removing yesno from @run main/manual=yesno
> 2) Used PassFaileJFrame to show the test instruction to the user instead of
> printing the test instruction on the console or jtreg log file.
> 3) If printer is not configured then mark the test as passed.
>
> @shurymury
> 1) Fixed Parser error by removing yesno from @run main/manual=yesno
> 2) Used PassFaileJFrame to show the test instruction to the user instead of
> printing the test instruction on the console or jtreg log file.
> 3) If printer is not configured then mark the test as passed.
>
> @shurymury
On Fri, 29 Apr 2022 00:41:50 GMT, Sergey Bylokhov wrote:
>> lawrence.andrews has updated the pull request with a new target base due to
>> a merge or a rebase. The incremental webrev excludes the unrelated changes
>> brought in by the merge/rebase. The pull request contains three additional
>>
> 1) Removed yesno to eliminate parserException
> 2) Added code to fit into manual framework so that timeout, pass & fail is
> handled.
> 3) Added code to mark the test as pass if printer service is not available
> 4) Added code to handle pressing or clicking of 'Cancel' button.
>
> @shurymury
>
> 1) Fixed Parser error by removing yesno from @run main/manual=yesno
> 2) Used PassFaileJFrame to show the test instruction to the user instead of
> printing the test instruction on the console or jtreg log file.
> 3) If printer is not configured then mark the test as passed.
>
> @shurymury
> 1) Fixed Parser error by removing yesno from @run main/manual=yesno
> 2) Used PassFaileJFrame to show the test instruction to the user instead of
> printing the test instruction on the console or jtreg log file.
> 3) If printer is not configured then mark the test as passed.
>
> @shurymury
On Tue, 26 Apr 2022 01:44:45 GMT, lawrence.andrews
wrote:
> 1) Removed yesno since test was failing with parser error due to @run
> main/manual=yesno
> 2) User can't decide whether it as pass or fail after looking into the
> printout so add the PassFailJFrame support
>
> @shurymury
> @aivan
1) Fixed Parser error by removing yesno from @run main/manual=yesno
2) Used PassFaileJFrame to show the test instruction to the user instead of
printing the test instruction on the console or jtreg log file.
3) If printer is not configured then mark the test as passed.
@shurymury
@aivanov-jdk
> 1) Removed yesno to eliminate parserException
> 2) Added code to fit into manual framework so that timeout, pass & fail is
> handled.
> 3) Added code to mark the test as pass if printer service is not available
> 4) Added code to handle pressing or clicking of 'Cancel' button.
>
> @shurymury
>
1) Removed yesno since test was failing with parser error due to @run
main/manual=yesno
2) User can't decide whether it as pass or fail after looking into the printout
so add the PassFailJFrame support
@shurymury
@aivanov-jdk
-
Commit messages:
- 8285617 : Fix java/awt/print/Pri
1) Removed yesno to eliminate parserException
2) Added code to fit into manual framework so that timeout, pass & fail is
handled.
3) Added code to mark the test as pass if printer service is not available
4) Added code to handle pressing or clicking of 'Cancel' button.
@shurymury
@aivanov-jdk
-
On Mon, 28 Mar 2022 20:23:20 GMT, lawrence.andrews
wrote:
> Fixed the following issue.
> 1) Removed yes/no since test was failing due to "Parser error due to yesno in
> @run main/manual=yesno"
> 2) After removing yes/no test run( just shows the UI and gets dispose
> immediately). User cannot i
> Fixed the following issue.
> 1) Removed yes/no since test was failing due to "Parser error due to yesno in
> @run main/manual=yesno"
> 2) After removing yes/no test run( just shows the UI and gets dispose
> immediately). User cannot interact with the test UI and mark the test pass or
> failed.
> Fixed the following issue.
> 1) Removed yes/no since test was failing due to "Parser error due to yesno in
> @run main/manual=yesno"
> 2) After removing yes/no test run( just shows the UI and gets dispose
> immediately). User cannot interact with the test UI and mark the test pass or
> failed.
On Tue, 19 Apr 2022 18:47:22 GMT, Alexey Ivanov wrote:
>> lawrence.andrews has updated the pull request incrementally with two
>> additional commits since the last revision:
>>
>> - Merge branch 'JDK-8283803' of https://github.com/lawrence-andrew/jdk into
>> JDK-8283803
>> - Removed checking
> Fixed the following issue.
> 1) Removed yes/no since test was failing due to "Parser error due to yesno in
> @run main/manual=yesno"
> 2) After removing yes/no test run( just shows the UI and gets dispose
> immediately). User cannot interact with the test UI and mark the test pass or
> failed.
On Sat, 16 Apr 2022 22:51:43 GMT, Phil Race wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Update PrintGlyphVectorTest.java
>
> test/jdk/java/awt/regtesthelpers/PassFailJFrame.java line 311:
>
>> 309: /**
> Fixed the following issue.
> 1) Removed yes/no since test was failing due to "Parser error due to yesno in
> @run main/manual=yesno"
> 2) After removing yes/no test run( just shows the UI and gets dispose
> immediately). User cannot interact with the test UI and mark the test pass or
> failed.
> Fixed the following issue.
> 1) Removed yes/no since test was failing due to "Parser error due to yesno in
> @run main/manual=yesno"
> 2) After removing yes/no test run( just shows the UI and gets dispose
> immediately). User cannot interact with the test UI and mark the test pass or
> failed.
> Fixed the following issue.
> 1) Removed yes/no since test was failing due to "Parser error due to yesno in
> @run main/manual=yesno"
> 2) After removing yes/no test run( just shows the UI and gets dispose
> immediately). User cannot interact with the test UI and mark the test pass or
> failed.
> Following issues were fixed in this test
> 1) Fixed - Parser error due to yesno in @run main/manual=yesno
> 2) Fixed Wrong test name specified in @run jtreg
> @run main/manual=yesno PrintTextTest . It should be @run main/manual=yesno
> SwingUIText
> 3) Instruction frame does not have 'Pass' or
> Fixed the following issue.
> 1) Removed yes/no since test was failing due to "Parser error due to yesno in
> @run main/manual=yesno"
> 2) After removing yes/no test run( just shows the UI and gets dispose
> immediately). User cannot interact with the test UI and mark the test pass or
> failed.
> Fixed the following issue.
> 1) Removed yes/no since test was failing due to "Parser error due to yesno in
> @run main/manual=yesno"
> 2) After removing yes/no test run( just shows the UI and gets dispose
> immediately). User cannot interact with the test UI and mark the test pass or
> failed.
> Fixed the following issue.
> 1) Removed yes/no since test was failing due to "Parser error due to yesno in
> @run main/manual=yesno"
> 2) After removing yes/no test run( just shows the UI and gets dispose
> immediately). User cannot interact with the test UI and mark the test pass or
> failed.
> Fixed the following issue.
> 1) Removed yes/no since test was failing due to "Parser error due to yesno in
> @run main/manual=yesno"
> 2) After removing yes/no test run( just shows the UI and gets dispose
> immediately). User cannot interact with the test UI and mark the test pass or
> failed.
On Fri, 25 Mar 2022 21:06:12 GMT, lawrence.andrews
wrote:
> We need a common manual test framework code that can be shared across all the
> client manual test. This framework class should have the following
> 1) Frame which contains test instruction .
> 2) Pass & Fail button so that user can ma
> We need a common manual test framework code that can be shared across all the
> client manual test. This framework class should have the following
> 1) Frame which contains test instruction .
> 2) Pass & Fail button so that user can mark the test pass or fail
> 3) Upon failing the test user shou
> We need a common manual test framework code that can be shared across all the
> client manual test. This framework class should have the following
> 1) Frame which contains test instruction .
> 2) Pass & Fail button so that user can mark the test pass or fail
> 3) Upon failing the test user shou
On Tue, 5 Apr 2022 20:38:58 GMT, Alexey Ivanov wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Dispose the Frame based in EDT
>
> test/jdk/java/awt/regtesthelpers/PassFailJFrame.java line 135:
>
>> 133:
> 1) Modified ManualTestFrame.java to support non SwingSet2 and this include
> modification of SwingSetTest.java
> 2) Added new TestJProgressBarAccessibility.java testcase that uses
> ManualTestFrame
> 3) Added timeout support in case user does not interact with the
> ManualTestFrame
>
> @shu
On Wed, 6 Apr 2022 10:39:44 GMT, Alexey Ivanov wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Fixed review comments
>
> test/jdk/java/awt/print/PrinterJob/PrintLatinCJKTest.java line 85:
>
>> 83:
On Tue, 5 Apr 2022 18:58:27 GMT, Alexey Ivanov wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Dispose the Frame based in EDT
>
> test/jdk/java/awt/print/PrinterJob/PrintLatinCJKTest.java line 91:
>
>> 89:
On Tue, 5 Apr 2022 20:16:28 GMT, lawrence.andrews wrote:
>> We need a common manual test framework code that can be shared across all
>> the client manual test. This framework class should have the following
>> 1) Frame which contains test instruction .
>> 2) Pass & Fail button so that user can
> We need a common manual test framework code that can be shared across all the
> client manual test. This framework class should have the following
> 1) Frame which contains test instruction .
> 2) Pass & Fail button so that user can mark the test pass or fail
> 3) Upon failing the test user shou
On Mon, 4 Apr 2022 18:59:39 GMT, Phil Race wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Dispose the Frame based in EDT
>
> test/jdk/java/awt/print/PrinterJob/PrintLatinCJKTest.java line 74:
>
>> 72:
> We need a common manual test framework code that can be shared across all the
> client manual test. This framework class should have the following
> 1) Frame which contains test instruction .
> 2) Pass & Fail button so that user can mark the test pass or fail
> 3) Upon failing the test user shou
On Fri, 4 Feb 2022 18:39:52 GMT, lawrence.andrews wrote:
> This testcase covers both old and new api ( api added in jdk17
> getAccessibleAction(), getAccessibleActionCount() ,
> getAccessibleActionDescription )
>
> @shurymury
> @savoptik
This pull request has now been integrated.
Changeset
Fixed the following issue.
1) Removed yes/no since test was failing due to "Parser error due to yesno in
@run main/manual=yesno"
2) After removing yes/no test run( just shows the UI and gets dispose
immediately). User cannot interact with the test UI and mark the test pass or
failed.
So added P
On Sat, 26 Mar 2022 02:38:41 GMT, Phil Race wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Fixed the white space issue
>
> test/jdk/java/awt/regtesthelpers/PassFailJFrame.java line 127:
>
>> 125:
> We need a common manual test framework code that can be shared across all the
> client manual test. This framework class should have the following
> 1) Frame which contains test instruction .
> 2) Pass & Fail button so that user can mark the test pass or fail
> 3) Upon failing the test user shou
On Sat, 26 Mar 2022 02:37:09 GMT, Phil Race wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Fixed the white space issue
>
> test/jdk/java/awt/regtesthelpers/PassFailJFrame.java line 103:
>
>> 101: * If us
On Sat, 26 Mar 2022 02:13:24 GMT, lawrence.andrews
wrote:
>> We need a common manual test framework code that can be shared across all
>> the client manual test. This framework class should have the following
>> 1) Frame which contains test instruction .
>> 2) Pass & Fail button so that user ca
> We need a common manual test framework code that can be shared across all the
> client manual test. This framework class should have the following
> 1) Frame which contains test instruction .
> 2) Pass & Fail button so that user can mark the test pass or fail
> 3) Upon failing the test user shou
> We need a common manual test framework code that can be shared across all the
> client manual test. This framework class should have the following
> 1) Frame which contains test instruction .
> 2) Pass & Fail button so that user can mark the test pass or fail
> 3) Upon failing the test user shou
On Fri, 25 Mar 2022 21:35:49 GMT, Phil Race wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Fixed the review comments and fixed the test using PassFailJFrame.java
>
> test/jdk/java/awt/regtesthelpers/PassFailJF
On Fri, 25 Mar 2022 21:33:46 GMT, Phil Race wrote:
>> We need a common manual test framework code that can be shared across all
>> the client manual test. This framework class should have the following
>> 1) Frame which contains test instruction .
>> 2) Pass & Fail button so that user can mark t
We need a common manual test framework code that can be shared across all the
client manual test. This framework class should have the following
1) Frame which contains test instruction .
2) Pass & Fail button so that user can mark the test pass or fail
3) Upon failing the test user should be able
Following issues were fixed in this test
1) Fixed - Parser error due to yesno in @run main/manual=yesno
2) Fixed Wrong test name specified in @run jtreg
@run main/manual=yesno PrintTextTest . It should be @run main/manual=yesno
SwingUIText
3) Instruction frame does not have 'Pass' or 'Fail' butto
On Wed, 15 Dec 2021 02:21:35 GMT, lawrence.andrews
wrote:
> 1) Test scenario was just showing test instruction with JTextArea. So added
> the JTextArea as the instruction and method says.
> 2) JTextArea is filled with contents so that and an Emoji character making
> sure that screen reader ca
On Thu, 17 Mar 2022 21:47:12 GMT, lawrence.andrews
wrote:
> 1) Removed =yesno since it was throwing Error: Not a test or directory
> containing tests
> 2) Test was just printing the "Test passes" on the printer and user did not
> had any option to mark the test as pass or fail and test was alw
On Wed, 23 Mar 2022 22:51:17 GMT, Phil Race wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Fixed minor spelling
>
> test/jdk/java/awt/print/PrinterJob/InitToBlack.java line 172:
>
>> 170: if (!CountDo
> 1) Removed =yesno since it was throwing Error: Not a test or directory
> containing tests
> 2) Test was just printing the "Test passes" on the printer and user did not
> had any option to mark the test as pass or fail and test was always passing.
> so created test UI with test instruction and
On Mon, 21 Mar 2022 16:52:26 GMT, Alexandre Iline
wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Fixed review comments
>
> test/jdk/javax/accessibility/JSlider/AccessibleAction/JSliderAccessibleAction.java
>
> Following methods are covered in this testcase
> getAccessibleAction()
> getAccessibleActionCount()
> doAccessibleAction(int direction)
>
> @shurymury
lawrence.andrews has updated the pull request incrementally with one additional
commit since the last revision:
Fixed review comments
> This testcase covers both old and new api ( api added in jdk17
> getAccessibleAction(), getAccessibleActionCount() ,
> getAccessibleActionDescription )
>
> @shurymury
> @savoptik
lawrence.andrews has updated the pull request incrementally with one additional
commit since the last revision:
1) Removed =yesno since it was throwing Error: Not a test or directory
containing tests
2) Test was just printing the "Test passes" on the printer and user did not had
any option to mark the test as pass or fail and test was always passing. so
created test UI with test instruction and test contr
On Thu, 16 Dec 2021 19:23:10 GMT, Artem Semenov wrote:
>> Hi @savoptik,
>> a) The test createTextArea() does not have JTextArea . I have attached the
>> screen shot of the test https://bugs.openjdk.java.net/browse/JDK-8278828
>> b) The test does not say its a non-editable JTextArea. Even the ex
On Thu, 27 Jan 2022 21:47:04 GMT, lawrence.andrews
wrote:
>> 1) Test scenario was just showing test instruction with JTextArea. So added
>> the JTextArea as the instruction and method says.
>> 2) JTextArea is filled with contents so that and an Emoji character making
>> sure that screen reade
On Wed, 9 Mar 2022 21:36:06 GMT, Alexandre Iline wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Added command after the date
>
> test/jdk/javax/swing/JSlider/8262981/JSliderAccessibleAction.java line 179:
>
>
> Following methods are covered in this testcase
> getAccessibleAction()
> getAccessibleActionCount()
> doAccessibleAction(int direction)
>
> @shurymury
lawrence.andrews has updated the pull request incrementally with one additional
commit since the last revision:
Fixed review comments
On Tue, 8 Mar 2022 04:34:35 GMT, Sergey Bylokhov wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> run the on windows and mac
>
> test/jdk/java/awt/a11y/AccessibleJSliderTest.java line 2:
>
>> 1: /*
>> 2: * Cop
> This testcase covers both old and new api ( api added in jdk17
> getAccessibleAction(), getAccessibleActionCount() ,
> getAccessibleActionDescription )
>
> @shurymury
> @savoptik
lawrence.andrews has updated the pull request incrementally with one additional
commit since the last revision:
> Following methods are covered in this testcase
> getAccessibleAction()
> getAccessibleActionCount()
> getAccessibleActionDescription()
> doAccessibleAction(int direction)
>
> @shurymury
lawrence.andrews has updated the pull request incrementally with one additional
commit since the last revis
Following methods are covered in this testcase
getAccessibleAction()
getAccessibleActionCount()
getAccessibleActionDescription()
doAccessibleAction(int direction)
@shurymury
-
Commit messages:
- Fixed white issue
- 8282771 : Create test case for JDK-8262981
Changes: https://git.o
On Fri, 4 Mar 2022 09:10:02 GMT, Artem Semenov wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> run the on windows and mac
>
> Looks good to me. I agree
@savoptik , can you approve this PR so that this PR is el
> This testcase covers both old and new api ( api added in jdk17
> getAccessibleAction(), getAccessibleActionCount() ,
> getAccessibleActionDescription )
>
> @shurymury
> @savoptik
lawrence.andrews has updated the pull request incrementally with one additional
commit since the last revision:
> This testcase covers both old and new api ( api added in jdk17
> getAccessibleAction(), getAccessibleActionCount() ,
> getAccessibleActionDescription )
>
> @shurymury
> @savoptik
lawrence.andrews has updated the pull request incrementally with one additional
commit since the last revision:
On Wed, 23 Feb 2022 02:03:24 GMT, lawrence.andrews
wrote:
>> test/jdk/javax/accessibility/JSlider/JSliderAccessibilityTest.java line 68:
>>
>>> 66: frame.setLocationRelativeTo(null);
>>> 67: frame.setDefaultCloseOperation(JFrame.DISPOSE_ON_CLOSE);
>>> 68: frame.setVisibl
On Sun, 6 Feb 2022 08:22:04 GMT, Sergey Bylokhov wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Added @key headful
>
> test/jdk/javax/accessibility/JSlider/JSliderAccessibilityTest.java line 2:
>
>> 1: /*
>>
> This testcase covers both old and new api ( api added in jdk17
> getAccessibleAction(), getAccessibleActionCount() ,
> getAccessibleActionDescription )
>
> @shurymury
> @savoptik
lawrence.andrews has updated the pull request incrementally with one additional
commit since the last revision:
On Mon, 7 Feb 2022 10:48:03 GMT, Artem Semenov wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Added @key headful
>
> test/jdk/javax/accessibility/JSlider/JSliderAccessibilityTest.java line 68:
>
>> 66:
On Fri, 28 Jan 2022 21:03:48 GMT, lawrence.andrews
wrote:
> 1) Removed =yesno that was causing the test to fail with following exception
> test result: Error. Parse Exception: Arguments to `manual' option not
> supported: yesno
> After removing =yesno, test was just passing without user interac
On Thu, 10 Feb 2022 08:47:51 GMT, Alexey Ivanov wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Removed RenderingHints.VALUE_TEXT_ANTIALIAS_GASP and fixed the review
>> comments
>
> test/jdk/java/awt/Graphics/
> 1) Removed =yesno that was causing the test to fail with following exception
> test result: Error. Parse Exception: Arguments to `manual' option not
> supported: yesno
> After removing =yesno, test was just passing without user interaction so
> fixed the following
>
> Add the following so that
On Tue, 8 Feb 2022 19:59:57 GMT, Alexey Ivanov wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Dispose the frame via EDT
>
> test/jdk/java/awt/Graphics/TextAAHintsTest.java line 2:
>
>> 1: package awt;
>> 2:
> 1) Removed =yesno that was causing the test to fail with following exception
> test result: Error. Parse Exception: Arguments to `manual' option not
> supported: yesno
> After removing =yesno, test was just passing without user interaction so
> fixed the following
>
> Add the following so that
> 1) Removed =yesno that was causing the test to fail with following exception
> test result: Error. Parse Exception: Arguments to `manual' option not
> supported: yesno
> After removing =yesno, test was just passing without user interaction so
> fixed the following
>
> Add the following so that
On Sun, 6 Feb 2022 08:36:46 GMT, Sergey Bylokhov wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Execute test all platform other than mac
>
> test/jdk/java/awt/Graphics/TextAAHintsTest.java line 231:
>
>> 229:
On Fri, 4 Feb 2022 22:20:32 GMT, Phil Race wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Added @key headful
>
> test/jdk/javax/accessibility/JSlider/JSliderAccessibilityTest.java line 28:
>
>> 26: * @bug 82
> This testcase covers both old and new api ( api added in jdk17
> getAccessibleAction(), getAccessibleActionCount() ,
> getAccessibleActionDescription )
>
> @shurymury
> @savoptik
lawrence.andrews has updated the pull request incrementally with one additional
commit since the last revision:
This testcase covers both old and new api ( api added in jdk17
getAccessibleAction(), getAccessibleActionCount() ,
getAccessibleActionDescription )
@shurymury
@savoptik
-
Commit messages:
- 8281284 : Write JSlider accessibility test
Changes: https://git.openjdk.java.net/jdk/pul
> 1) Removed =yesno that was causing the test to fail with following exception
> test result: Error. Parse Exception: Arguments to `manual' option not
> supported: yesno
> After removing =yesno, test was just passing without user interaction so
> fixed the following
>
> Add the following so that
On Fri, 28 Jan 2022 21:03:48 GMT, lawrence.andrews
wrote:
> 1) Removed =yesno that was causing the test to fail with following exception
> test result: Error. Parse Exception: Arguments to `manual' option not
> supported: yesno
> After removing =yesno, test was just passing without user interac
On Tue, 1 Feb 2022 03:16:28 GMT, Sergey Bylokhov wrote:
>> 1) Removed =yesno that was causing the test to fail with following exception
>> test result: Error. Parse Exception: Arguments to `manual' option not
>> supported: yesno
>> After removing =yesno, test was just passing without user intera
1) Removed =yesno that was causing the test to fail with following exception
test result: Error. Parse Exception: Arguments to `manual' option not
supported: yesno
After removing =yesno, test was just passing without user interaction so fixed
the following
Add the following so that user can user
On Thu, 27 Jan 2022 19:56:20 GMT, lawrence.andrews
wrote:
>> 1) Test scenario was just showing test instruction with JTextArea. So added
>> the JTextArea as the instruction and method says.
>> 2) JTextArea is filled with contents so that and an Emoji character making
>> sure that screen reade
> 1) Test scenario was just showing test instruction with JTextArea. So added
> the JTextArea as the instruction and method says.
> 2) JTextArea is filled with contents so that and an Emoji character making
> sure that screen reader can read Emoji also.
> 3) Now user can user arrow keys to navig
> 1) Test scenario was just showing test instruction with JTextArea. So added
> the JTextArea as the instruction and method says.
> 2) JTextArea is filled with contents so that and an Emoji character making
> sure that screen reader can read Emoji also.
> 3) Now user can user arrow keys to navig
On Thu, 16 Dec 2021 08:32:40 GMT, Artem Semenov wrote:
>> 1) Test scenario was just showing test instruction with JTextArea. So added
>> the JTextArea as the instruction and method says.
>> 2) JTextArea is filled with contents so that and an Emoji character making
>> sure that screen reader ca
1) Test scenario was just showing test instruction with JTextArea. So added the
JTextArea as the instruction and method says.
2) JTextArea is filled with contents so that and an Emoji character making sure
that screen reader can read Emoji also.
3) Now user can user arrow keys to navigate the JT
On Wed, 13 Oct 2021 17:02:03 GMT, lawrence.andrews
wrote:
> InterpolationQualityTest.java test fails consistently on windows 10 hence
> adding it in the problemList.
>
> @shurymury
Its a latest window on a new VM.
Checking the VM's graphic system configuration.
I checked the VM graphics con
1 - 100 of 136 matches
Mail list logo
