RFR: JDK-8222323: ChildAlwaysOnTopTest.java fails with "RuntimeException: Failed to unset alwaysOnTop"

Phil Race prr at openjdk.java.net
Wed May 4 18:13:16 UTC 2022


On Wed, 4 May 2022 18:02:48 GMT, Harshitha Onkar <duke at openjdk.java.net> wrote:

>> test/jdk/java/awt/Window/MultiWindowApp/ChildAlwaysOnTopTest.java line 165:
>> 
>>> 163:                 throw new RuntimeException("Scenario 1: alwaysOnTop window is "+
>>> 164:                         "sent back by another child window with setVisible(). "
>>> 165:                         + color);
>> 
>> I see that we are doing a number of test scenarios but test fails immediately when first error occurs. Can we continue testing, save all screenshots and remember all the failures and then fail at the end if there were errors listing all the errors in all the LaF's that were happened during the run?
>
> @azuev-java Thank you for the suggestion. I can definitely add this functionality to the test for better failure analysis.

I think that's a reasonable suggestion in general to bear in mind when writing tests.
I've seen tests which bail at the first failure and you wish you knew how the rest of it worked out ..
Like (say) a test that iterates over the 4 available L&Fs might be a case.

-------------

PR: https://git.openjdk.java.net/jdk/pull/8509



More information about the client-libs-dev mailing list