On Mon, 23 May 2022 16:25:37 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
> 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 again.
Alexandre Iline has updated the pull request i
On Mon, 23 May 2022 16:45:09 GMT, Phil Race wrote:
> Can you explain both the problem and the solution ?
>From what I have observed, the test starts before the window is painted. The
>window is basically gray. My hypothesis is then that it takes time to load the
>background image and the test
On Mon, 23 May 2022 16:25:37 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
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 again.
-
Commit messages:
- A public method to capture the wh
On Thu, 7 Apr 2022 22:59: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 ca
On Tue, 22 Mar 2022 15:14:34 GMT, lawrence.andrews
wrote:
>> Following methods are covered in this testcase
>> getAccessibleAction()
>> getAccessibleActionCount()
>> doAccessibleAction(int direction)
>>
>> @shurymury
>
> lawrence.andrews has updated the pull request incrementally with one
> a
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
On Thu, 24 Mar 2022 20:24:35 GMT, lawrence.andrews
wrote:
> 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
On Wed, 16 Mar 2022 21:17:44 GMT, lawrence.andrews
wrote:
>> Following methods are covered in this testcase
>> getAccessibleAction()
>> getAccessibleActionCount()
>> doAccessibleAction(int direction)
>>
>> @shurymury
>
> lawrence.andrews has updated the pull request incrementally with one
> a
On Tue, 8 Mar 2022 05:10:51 GMT, lawrence.andrews wrote:
>> Following methods are covered in this testcase
>> getAccessibleAction()
>> getAccessibleActionCount()
>> getAccessibleActionDescription()
>> doAccessibleAction(int direction)
>>
>> @shurymury
>
> lawrence.andrews has updated the pull r
On Tue, 8 Mar 2022 05:10:51 GMT, lawrence.andrews wrote:
>> Following methods are covered in this testcase
>> getAccessibleAction()
>> getAccessibleActionCount()
>> getAccessibleActionDescription()
>> doAccessibleAction(int direction)
>>
>> @shurymury
>
> lawrence.andrews has updated the pull r
On Tue, 8 Mar 2022 05:13:44 GMT, lawrence.andrews wrote:
>> This testcase covers both old and new api ( api added in jdk17
>> getAccessibleAction(), getAccessibleActionCount() ,
>> getAccessibleActionDescription )
>>
>> @shurymury
>> @savoptik
>
> lawrence.andrews has updated the pull reques
On Tue, 8 Mar 2022 05:10:51 GMT, lawrence.andrews wrote:
>> Following methods are covered in this testcase
>> getAccessibleAction()
>> getAccessibleActionCount()
>> getAccessibleActionDescription()
>> doAccessibleAction(int direction)
>>
>> @shurymury
>
> lawrence.andrews has updated the pull r
On Sat, 8 Jan 2022 00:42:18 GMT, Alexandre Iline wrote:
> Tests are based on SwingSet2 application.
> Test instructions are loaded from HTML files.
>
> See readme for more info.
This pull request has now been integrated.
Changeset: 5523ddeb
Author: Alexandre Iline
URL:
On Wed, 12 Jan 2022 03:03:41 GMT, Sergey Bylokhov wrote:
> > This current implementation does not do anything to support different LAFs.
>
> 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
On Tue, 11 Jan 2022 07:04:51 GMT, Phil Race wrote:
> 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?
This current implementation does not do anything to support different LAFs.
A test execu
On Sat, 8 Jan 2022 00:42:18 GMT, Alexandre Iline wrote:
> Tests are based on SwingSet2 application.
> Test instructions are loaded from HTML files.
>
> See readme for more info.
@prrace Can you take a look?
-
PR: https://git.openjdk.java.net/jdk/pull/6993
JDK-8279641: Create manual JTReg tests for Swing accessibility
-
Commit messages:
- JDK-8279641: Create manual JTReg tests for Swing accessibility
Changes: https://git.openjdk.java.net/jdk/pull/6993/files
Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=6993&range=00
Issue:
19 matches
Mail list logo
