Problem :
1) Test case was failing with following exception
test result: Error. Parse Exception: Arguments to `manual' option not
supported: yes
2) After removing =yes/no Parser exception is not seen but test UI will show
and closes immediately where the user cannot see what is on the frame.
> Problem :
> 1) Test case was failing with following exception
> test result: Error. Parse Exception: Arguments to `manual' option not
> supported: yes
> 2) After removing =yes/no Parser exception is not seen but test UI will show
> and closes immediately where the user cannot see what is on
On Tue, 20 Jul 2021 23:54:20 GMT, lawrence.andrews
wrote:
> 1) When the test is executed via jtreg user can see only print dialog with no
> instruction to the user. User has to see the test case to see the instruction
> and perform the test .
> 2) With this fix User is instructed what he/she
On Tue, 14 Sep 2021 16:38:34 GMT, Pankaj Bansal wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Fixed minor issue
>
> test/jdk/java/awt/Graphics/LCDTextAndGraphicsState.java line 126:
>
>> 124: instruc
On Tue, 20 Jul 2021 23:54:20 GMT, lawrence.andrews
wrote:
> 1) When the test is executed via jtreg user can see only print dialog with no
> instruction to the user. User has to see the test case to see the instruction
> and perform the test .
> 2) With this fix User is instructed what he/she
> 1) When the test is executed via jtreg user can see only print dialog with no
> instruction to the user. User has to see the test case to see the instruction
> and perform the test .
> 2) With this fix User is instructed what he/she has to do with the print
> dialog.
> 3) I have added both su
On Thu, 16 Sep 2021 19:44:48 GMT, Alexey Ivanov wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Close instruction frame if OK/Cancel button is pressed
>
> test/jdk/java/awt/print/Dialog/DialogCopies.java line 5
> 1) When the test is executed via jtreg user can see only print dialog with no
> instruction to the user. User has to see the test case to see the instruction
> and perform the test .
> 2) With this fix User is instructed what he/she has to do with the print
> dialog.
> 3) I have added both su
On Wed, 15 Sep 2021 15:14:36 GMT, Alexey Ivanov wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Fixed minor issue
>
> test/jdk/java/awt/Graphics/LCDTextAndGraphicsState.java line 60:
>
>> 58: private stati
> Problem :
> 1) Test case was failing with following exception
> test result: Error. Parse Exception: Arguments to `manual' option not
> supported: yes
> 2) After removing =yes/no Parser exception is not seen but test UI will show
> and closes immediately where the user cannot see what is on
> Problem :
> 1) Test case was failing with following exception
> test result: Error. Parse Exception: Arguments to `manual' option not
> supported: yes
> 2) After removing =yes/no Parser exception is not seen but test UI will show
> and closes immediately where the user cannot see what is on
On Fri, 17 Sep 2021 14:05:45 GMT, Alexey Ivanov wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Simplified test UI
>
> test/jdk/java/awt/Graphics/LCDTextAndGraphicsState.java line 49:
>
>> 47: import java.awt.
On Wed, 15 Sep 2021 15:15:15 GMT, Alexey Ivanov wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Fixed minor issue
>
> test/jdk/java/awt/Graphics/LCDTextAndGraphicsState.java line 59:
>
>> 57:
>> 58: priva
On Fri, 17 Sep 2021 13:15:44 GMT, Alexey Ivanov wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Simplified test UI
>
> test/jdk/java/awt/Graphics/LCDTextAndGraphicsState.java line 120:
>
>> 118:
>> 119:
On Wed, 15 Sep 2021 15:21:12 GMT, Alexey Ivanov wrote:
>> lawrence.andrews has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Fixed minor issue
>
> test/jdk/java/awt/Graphics/LCDTextAndGraphicsState.java line 79:
>
>> 77: Graphics2
On Mon, 13 Sep 2021 21:22:36 GMT, lawrence.andrews
wrote:
> Problem :
> 1) Test case was failing with following exception
> test result: Error. Parse Exception: Arguments to `manual' option not
> supported: yes
> 2) After removing =yes/no Parser exception is not seen but test UI will show
>
> 1) When the test is executed via jtreg user can see only print dialog with no
> instruction to the user. User has to see the test case to see the instruction
> and perform the test .
> 2) With this fix User is instructed what he/she has to do with the print
> dialog.
> 3) I have added both su
On Fri, 17 Sep 2021 18:01:06 GMT, Alexey Ivanov wrote:
>> lawrence.andrews has updated the pull request incrementally with three
>> additional commits since the last revision:
>>
>> - removed unwanted textarea.setText
>> - minor change
>> - Close instruction frame after clicking OK/Cancel bu
On Tue, 20 Jul 2021 23:54:20 GMT, lawrence.andrews
wrote:
> 1) When the test is executed via jtreg user can see only print dialog with no
> instruction to the user. User has to see the test case to see the instruction
> and perform the test .
> 2) With this fix User is instructed what he/she
On Mon, 20 Sep 2021 19:29:10 GMT, Sergey Bylokhov wrote:
> This testcase creates two threads for each tag, one thread continuously
> change the profiles, the second thread use that profiles for color
> conversion. The first thread executed no more than 15 seconds, and the second
> thread shoul
Problem : Testcase was failing with parser exception
test result: Error. Parse Exception: Arguments to `manual' option not
supported: yesno
Fix : Removed =yesno and run the testcase and Test UI ( instruction and print
dialog ) is visible
@shurymury
-
Commit messages:
- 8274029 :
Problem :
1) Testcase was failing due to parse exception yesno
2) After removing yesno tag test frame and immediately get disposed
Fix :
1) Removed yesno tag
2) Show the test frame with pass, fail button. Now user can click on the
`print' button to show the print dialog and take the print out
On Tue, 21 Sep 2021 08:13:41 GMT, Pankaj Bansal wrote:
>> Problem :
>> 1) Testcase was failing due to parse exception yesno
>> 2) After removing yesno tag test frame and immediately get disposed
>>
>> Fix :
>> 1) Removed yesno tag
>> 2) Show the test frame with pass, fail button. Now user can
> Problem :
> 1) Testcase was failing due to parse exception yesno
> 2) After removing yesno tag test frame and immediately get disposed
>
> Fix :
> 1) Removed yesno tag
> 2) Show the test frame with pass, fail button. Now user can click on the
> `print' button to show the print dialog and tak
On Tue, 21 Sep 2021 11:56:07 GMT, lawrence.andrews
wrote:
>> test/jdk/java/awt/print/PrinterJob/ImagePrinting/ImageTypes.java line 83:
>>
>>> 81: import static java.awt.image.BufferedImage.TYPE_INT_RGB;
>>> 82: import static java.awt.image.BufferedImage.TYPE_USHORT_555_RGB;
>>> 83: import stati
1) Removed =yesno
2) After running the test case, test UI will close immediately. Where the user
cannot interact so rewrote the test case.
a) Toolkit Modal Dialog will be shown after clicking the show button.
b) Added timeout & tested
c) Step by step instruction what the user has to perform
@shu
> Problem :
> 1) Testcase was failing due to parse exception yesno
> 2) After removing yesno tag test frame and immediately get disposed
>
> Fix :
> 1) Removed yesno tag
> 2) Show the test frame with pass, fail button. Now user can click on the
> `print' button to show the print dialog and tak
> 1) Removed =yesno
> 2) After running the test case, test UI will close immediately. Where the
> user cannot interact so rewrote the test case.
> a) Toolkit Modal Dialog will be shown after clicking the show button.
> b) Added timeout & tested
> c) Step by step instruction what the user has to p
On Tue, 5 Oct 2021 07:08:18 GMT, Sergey Bylokhov wrote:
>> 1) Removed =yesno
>> 2) After running the test case, test UI will close immediately. Where the
>> user cannot interact so rewrote the test case.
>> a) Toolkit Modal Dialog will be shown after clicking the show button.
>> b) Added timeou
On Fri, 1 Oct 2021 18:27:21 GMT, lawrence.andrews
wrote:
> 1) Removed =yesno
> 2) After running the test case, test UI will close immediately. Where the
> user cannot interact so rewrote the test case.
> a) Toolkit Modal Dialog will be shown after clicking the show button.
> b) Added timeout &
On Mon, 20 Sep 2021 21:36:34 GMT, lawrence.andrews
wrote:
> Problem : Testcase was failing with parser exception
> test result: Error. Parse Exception: Arguments to `manual' option not
> supported: yesno
> Fix : Removed =yesno and run the testcase and Test UI ( instruction and print
> dialog
java/awt/GraphicsDevice/DisplayModes/CycleDMImage.java is entered twice in the
problemList.txt
jtreg always picks the second entry not the first one and user expects that
test should be executed on the first entry platform but it executes.
@shurymury
-
Commit messages:
- 8275234
On Wed, 13 Oct 2021 18:37:40 GMT, lawrence.andrews
wrote:
> java/awt/GraphicsDevice/DisplayModes/CycleDMImage.java is entered twice in
> the problemList.txt
> jtreg always picks the second entry not the first one and user expects that
> test should be executed on the first entry platform but
On Tue, 21 Sep 2021 03:24:24 GMT, lawrence.andrews
wrote:
> Problem :
> 1) Testcase was failing due to parse exception yesno
> 2) After removing yesno tag test frame and immediately get disposed
>
> Fix :
> 1) Removed yesno tag
> 2) Show the test frame with pass, fail button. Now user can cl
InterpolationQualityTest.java test fails consistently on windows 10 hence
adding it in the problemList.
@shurymury
-
Commit messages:
- Added the right test case failure bugid
- 8275165 : ProblemList InterpolationQualityTest.java
Changes: https://git.openjdk.java.net/jdk/pull/593
On Wed, 13 Oct 2021 18:10:43 GMT, Sergey Bylokhov wrote:
>> InterpolationQualityTest.java test fails consistently on windows 10 hence
>> adding it in the problemList.
>>
>> @shurymury
>
> I remember this test was(and is) quite stable, did you check what is the
> reason of the failure. Is it po
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) 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 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 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, 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) 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 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
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
> 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
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
> 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 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
> 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:
> 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
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/
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 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:
> 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 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: /*
>>
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
> 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 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
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
> 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
> 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 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
> 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 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:
>
>
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 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
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
> 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()
> doAccessibleAction(int direction)
>
> @shurymury
lawrence.andrews has updated the pull request incrementally with one additional
commit since the last revision:
Fixed review comments
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
>
> 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 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
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, 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
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
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
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
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
> 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 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
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
> 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: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:
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 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
> 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 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
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 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:
> 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 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:
> 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
1 - 100 of 136 matches
Mail list logo
