JDK-8317107 : Investigate automating JFrame/DefaultCloseOperation.java
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 22
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2023-09-27
  • Updated: 2023-10-02
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Relates :  
Description
The test/jdk/javax/swing/JFrame/DefaultCloseOperation.java test could be improved:

In fact, I thought about iterating the values automatically ... and ask the tester to click the Close button on the window. The do nothing could be the last option tested, and the frame/dialog would be closed from the handler.

Another way could be sending the event programmatically. This would automate the test completely. However, we may still leave the manual test... just in case the tester sees anything unusual.

See https://github.com/openjdk/jdk/pull/15827#discussion_r1336149065 from JDK-8316211 for more details.