db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Myrna van Lunteren <m.v.lunte...@gmail.com>
Subject Re: system properties in Derby unit tests
Date Tue, 07 Feb 2006 22:19:45 GMT
I *think* the jvmflags is specifically intended to be passing on properties
without the -D flag. I remember being disappointed in the harness mangling
it if it has/needs a -D.

You may also have a look at testJavaFlags. The encryption suites use this,
I'm not entirely sure it works with RunTest, but worth a try. In that one,
the harness adds a -D, I think.


On 2/7/06, Kathey Marsden <kmarsdenderby@sbcglobal.net> wrote:
> Rick Hillegas wrote:
> > I would like to set a system property for a Derby unit test run  under
> > the RunTest framework. Would appreciate advice on how to do this. The
> > instructions in trunk/java/testing/README.htm say that I can crank up
> > RunTest with -DtestSpecialProps and that is useful for a hand-run
> > test. However, I don't know how to force a test to always have a
> > certain System property when run inside derbyall. The *_app.properties
> > files are nice too but they don't set system properties.
> I don't really understand the difference between testSpecialProps and
> jvmflags but setting jvmflags in the <test>_app.properties file like
> lang/largeCodeGen does works ok as long as the test is not run with
> useprocess false.
> Kathey

View raw message