Yes. Several different options provided with jtreg
influence the output per test. Here are a few verbose settings in order of
decreasing average output per test.
-verbose:fail
(and related
-verbose:pass
, -verbose:error
, and
-verbose:all
)-verbose
-verbose:summary
The following samples of output correspond to each of the above settings.
Each sample is run with three tests: Pass.java
,
Fail.java
, and Error.java
. Note that in
some cases, the output varies substantially depending on whether the test
passed or failed.
-verbose:fail
- Full output for failed
tests only. Two lines for tests that passed or produced errors (related
options: -verbose:pass
, -verbose:fail
, and
-verbose:all
).
ribbit$ jtreg -verbose:fail Pass.java Fail.java Error.java -------------------------------------------------- TEST: Pass.java TEST RESULT: Passed. Execution successful -------------------------------------------------- TEST: Fail.java JDK under test: (/usr/local/java/jdk1.4/solsparc) java version "1.4.0-beta" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta-b56) Java HotSpot(TM) Client VM (build 1.4-beta-B56, mixed mode) ACTION: build -- Passed. Compilation successful REASON: Named class compiled on demand TIME: 3.649 seconds ACTION: compile -- Passed. Compilation successful REASON: .class file out of date or does not exist TIME: 3.637 seconds STDOUT: STDERR: ACTION: main -- Failed. Execution failed: `main' threw exception: java.lang.Exception: Fail REASON: Assumed action based on file name: run main Fail TIME: 1.219 seconds STDOUT: STDERR: java.lang.Exception: I failed at Fail.main(Fail.java:5) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:30) at sun.reflect.InflatableMethodAccessorImpl.invoke(InflatableMethodAccessorImpl.java:46) at java.lang.reflect.Method.invoke(Method.java:306) at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94) at java.lang.Thread.run(Thread.java:579) JavaTest Message: Test threw exception: java.lang.Exception: I failed JavaTest Message: shutting down test STATUS:Failed.`main' threw exception: java.lang.Exception: I failed TEST RESULT: Failed. Execution failed: `main' threw exception: java.lang.Exception: I failed -------------------------------------------------- TEST: Error.java TEST RESULT: Error. Parse Exception: Unexpected length for bugid: 31415926, -------------------------------------------------- test results: passed: 1; failed: 1; error: 1 Report written to /u/iag/jtw/JTreport/report.html Results written to /u/iag/jtw/JTwork Error: some tests failed or other problems occurred
-verbose
- This option produces three
lines of output per test: start, end, final status.
ribbit$ jtreg -verbose Pass.java Fail.java Error.java runner starting test: Pass.java runner finished test: Pass.java Passed. Execution successful runner starting test: Fail.java runner finished test: Fail.java Failed. Execution failed: `main' threw exception: java.lang.Exception: I failed runner starting test: Error.java runner finished test: Error.java Error. Parse Exception: Unexpected length for bugid: 31415926, test results: passed: 1; failed: 1; error: 1 Report written to /u/iag/jtw/JTreport/report.html Results written to /u/iag/jtw/JTwork Error: some tests failed or other problems occurred
-verbose:summary
- A single line of
output per test: final status and name of file.
ribbit$ jtreg -verbose:summary Pass.java Fail.java Error.java Passed: Pass.java FAILED: Fail.java Error: Error.java test results: passed: 1; failed: 1; error: 1 Report written to /u/iag/jtw/JTreport/report.html Results written to /u/iag/jtw/JTwork Error: some tests failed or other problems occurred
No verbose option provides only general summary information about all the tests run.
ribbit$ jtreg Pass.java Fail.java Error.java test results: passed: 1; failed: 1; error: 1 Report written to /u/iag/jtw/JTreport/report.html Results written to /u/iag/jtw/JTwork Error: some tests failed or other problems occurred
If there is information that you find lacking in all of these options, please contact the developer to determine if it is possible to make it available.