Re: [11] RFR [TEST][JDK-8197948] Create test for SwingSet2 main window

2018-02-14 Thread Muneer Kolarkunnu
Hi Semyon, Only the file test/jdk/sanity/client/SwingSet/src/SwingSet2DemoTest.java is newly created. I have done some minor changes in files SwingSet2.java, swingset.properties files, mainly removed/commented unwanted codes for this test. Also I haven't included lots of other sub

Re: [11] RFR [TEST][JDK-8197948] Create test for SwingSet2 main window

2018-02-14 Thread Semyon Sadetsky
Hi, can you clarify which files were newly created and which are copied from SwingSet2 without changes. Thanks. --Semyon On 02/14/2018 09:28 AM, Muneer Kolarkunnu wrote: Hi All, Please review the following, a new client sanity test case: Task:

[11] RFR [TEST][JDK-8197948] Create test for SwingSet2 main window

2018-02-14 Thread Muneer Kolarkunnu
Hi All, Please review the following, a new client sanity test case: Task: https://bugs.openjdk.java.net/browse/JDK-8197948 Webrev Link: http://cr.openjdk.java.net/~akolarkunnu/8197948/webrev.00/ Summary: This is a new test for automated testing of SwingSet2 main window using Jemmy.

Re: [11] RFR JDK-8197825: [Test] Intermiitent timeout with javax/swing JColorChooser Test

2018-02-14 Thread Sergey Bylokhov
On 14/02/2018 02:58, Prasanta Sadhukhan wrote: Maybe the robot mouse events are not getting enough time to be processed which is why the toolkit shutdown is not able to happen as those are still in the event queue. Adding waitForIdle() in the test allows those robot events to be processed and

Re: [11] RFR JDK-8197825: [Test] Intermiitent timeout with javax/swing JColorChooser Test

2018-02-14 Thread Prasanta Sadhukhan
Hi Sergey, Maybe the robot mouse events are not getting enough time to be processed which is why the toolkit shutdown is not able to happen as those are still in the event queue. Adding waitForIdle() in the test allows those robot events to be processed and then toolkit thread gets chance to