On Wed, 4 May 2022 17:58:17 GMT, Alexander Zuev <kiz...@openjdk.org> wrote:
>> This test case tests the functionality of `setAlwaysOnTop`. >> Documentation on `setAlwaysOnTop`: >> [Link](https://docs.oracle.com/en/java/javase/17/docs/api/java.desktop/java/awt/Window.html#setAlwaysOnTop(boolean)) >> >> The following test case was seen to fail on windows and linux platforms. >> With the proposed fix, the test case works on all platforms. >> >> The test case tests `alwaysOnTop` for the following three cases: >> >> 1. JDialog with no parent/owner >> 2. JDialog with JFrame as owner >> 3. JDialog with another JDialog as owner >> >> Each of the three cases mentioned above is tested under 3 scenarios: >>  > > 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. ------------- PR: https://git.openjdk.java.net/jdk/pull/8509
