harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geir Magnusson Jr <g...@pobox.com>
Subject Re: Tainting testing environment
Date Mon, 20 Mar 2006 13:10:31 GMT

Stepan Mishura wrote:
> On 3/19/06, Geir Magnusson Jr wrote:
> <snip>
>>>  - move the test to a suite of tests that fork the VM on each test
>>> invocation so you get a fresh environment every time (and therefore
>>> don't have to tidy-up).  This will make the test a pure API test, but
>>> will have performance overhead.
>> I'd vote for the second option.  Much cleaner and easy to understand -
>> therefore to maintain.
> Well, I can add that first option doesn't allow running tests in parallel
> (for example, if we switch to TestNG) because they share the same
> environment (BTW, this also relates to system properties). So the second
> option is more preferable way to solve the problem but ... how many
> different test suites we are going to create?

Who knows.

> What if I want to run a test in environment with all security properties
> unset? Should I create a new test suite to fork the VM with -
> Djava.security.properties==<empty file>? And what if I want to unset only
> selected security properties? Another test suite with custom security
> properties file? ... It doesn't look for me as elegant and lightweight
> solution and this makes me feel a little depressed.

As elegant and lightweight as what?

Have the abillity to neatly define the configuration scenarious you 
suggest sounds ince.


View raw message