JDK-8320676 : Manual printer tests have no Pass/Fail buttons, instructions close set 1
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 11,17,21,22
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2023-11-23
  • Updated: 2025-04-08
  • Resolved: 2024-04-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.
JDK 11 JDK 17 JDK 21 JDK 23 JDK 8
11.0.27-oracleFixed 17.0.15-oracleFixed 21.0.7-oracleFixed 23 b17Fixed 8u451Fixed
Related Reports
Relates :  
JDK-8324807 - Manual printer tests have no Pass/Fail buttons, instructions close set 2
Relates :  
JDK-8329322 - Convert PageFormat/Orient.java to use PassFailJFrame
Relates :  
JDK-8324808 - Manual printer tests have no Pass/Fail buttons, instructions close set 3
Description
The following manual printer tests use Sysout framework/classes to display its UI; it was used with applets but the tests are now converted to standalone apps, and there are no Pass or Fail buttons displayed. The instructions quickly appear on the screen and close quickly; in some cases they close after you click Print/OK in a displayed dialog.

This is not the intended behaviour.

The list of tests:
test/jdk/java/awt/print/PageFormat/PageSetupDialog.java
test/jdk/java/awt/print/PrinterJob/Cancel/PrinterJobCancel.java
test/jdk/java/awt/print/PrinterJob/Collate2DPrintingTest.java
test/jdk/java/awt/print/PrinterJob/DrawImage.java
test/jdk/java/awt/print/PrinterJob/DrawStringMethods.java
test/jdk/java/awt/print/PrinterJob/InvalidPage.java
test/jdk/java/awt/print/PrinterJob/JobName/PrinterJobName.java
test/jdk/java/awt/print/PrinterJob/NumCopies.java
test/jdk/java/awt/print/PrinterJob/PageDlgPrnButton.java
test/jdk/java/awt/print/PrinterJob/PrintCompoundString.java
test/jdk/java/awt/print/PrinterJob/PrintImage.java
test/jdk/java/awt/print/PrinterJob/PrintNullString.java
test/jdk/java/awt/print/PrinterJob/PrintParenString.java
test/jdk/java/awt/print/PrinterJob/PrintTranslatedFont.java
test/jdk/java/awt/print/PrinterJob/raster/RasterTest.java
test/jdk/java/awt/print/PrinterJob/ValidatePage/ValidatePage.java

I also attached as sysout.testlist file to this bug.

You can run the entire set by using a command-line like this:
java -jar jtreg.jar -nr -v $(cat sysout.testlist)
Comments
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/17607 Date: 2024-01-29 06:24:29 +0000
08-04-2025
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk17u-dev/pull/3217 Date: 2025-01-16 14:29:18 +0000
16-01-2025
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk21u-dev/pull/1332 Date: 2025-01-16 14:29:11 +0000
16-01-2025
Fix request [21u,17u] I backport this for parity with 21.0.7-oracle,17.0.15-oracle. No risk, only a test change. Clean backport. Tests start up properly.
16-01-2025
Changeset: 7eb78e33 Author: Renjith Kannath Pariyangad <rkannathpari@openjdk.org> Committer: Alexey Ivanov <aivanov@openjdk.org> Date: 2024-04-02 13:22:17 +0000 URL: https://git.openjdk.org/jdk/commit/7eb78e332080df3890b66ca04338a4ba69af45eb
02-04-2024
For better review, made tests into 3 set JDK-8324807 and JDK-8324808
29-01-2024
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/17565 Date: 2024-01-25 04:52:15 +0000
25-01-2024
The test/jdk/java/awt/print/PrinterJob/PrintAllFonts.java test falls into this category as well: it uses Sysout framework. Currently, it doesn't have `@test` tag and therefore it isn't run.
30-11-2023
In some cases the instructions need to be clarified: java/awt/print/PrinterJob/Cancel/PrinterJobCancel.java refers to console, yet the tester doesn't see the console. The test needs to be updated either to display the messages to the tester or handle the scenario automatically. For this reason, it could be separated into its own issue. java/awt/print/PrinterJob/PageDlgPrnButton.java requires at least two printers. Can this be verified before displaying the UI to tester? The test instructions state the tester should press Pass; thus the test is to have `@requires` tag so that it runs only on windows.
23-11-2023