Bug 7900203 - JTreg needs to log instructions for rerunning test outside jtreg

David Chase david.r.chase at oracle.com
Tue Jul 16 16:03:47 PDT 2013

The JTReg maintainers suggested I ask this question here.  I would like an answer, not a pointer to a page for me to read that is alleged to contain an answer (but when I read the page, it does not contain an answer, which is why I want an answer -- fool me once, shame on you, fool me twice, shame on you).

I am trying to run a test from the command line, in java, not under jtreg, because I want to start gdb and set breakpoints.  The test is


It is a testng test.
I do not know what the name of the class to run the test is; that is not documented (not in jtreg).
I do not know what parameters that class takes; that is not documented  (not in jtreg).
I do not know what other entries that class takes on the classpath; that is not documented  (not in jtreg).

I want to run it on the command line, not from ant.
That is not documented on the default page for testng, and certainly not in jtreg.

It is clear that jtreg has to know all these things, else it cannot run the test properly itself, so I think jtreg is perfectly positioned to emit this information for my edification, but failing that, it can be documented.

Ideally all this information would appear in a cuttable-pastable form for command-line execution, but apparently that would be too boring and mechanical for computers to do, and instead is to be done by the developers who actually wish to debug a failing test.

As you can tell, I'm loving this a whole lot.


More information about the lambda-dev mailing list