Skip to content
This repository has been archived by the owner on Jan 6, 2018. It is now read-only.

add support for a test.properties file to load test system properties #346

Closed
tucu00 opened this issue Jan 25, 2011 · 1 comment
Closed

Comments

@tucu00
Copy link
Contributor

tucu00 commented Jan 25, 2011

running testcases often requires specifying real unix users/groups, kerberos principals, JT/NN URI.

running the testcases in different configurations requires different sets of system properties.

Being able to use a test properties file to specify these system properties sets would be very convenient.

Being able to specify different test properties files would make also easier to test different setups without having to specify a long list of of system properties in maven command line.

By default, is a 'test.properties' file exists, its values would be loaded as system properties before running any of the testcases.

If Maven is invoked with the option '-Doozie.test.properties=FILE' an alternate properties file would be used to load the system properties for the testcases run. This would allow having different test properties sets, for example: minicluster, simple & kerberos.

Values specified as options to Maven in the command line override would override values in the test.properties file.

@tucu00
Copy link
Contributor Author

tucu00 commented Jan 28, 2011

Closed by 2d9bbac add support for a test.properties file to load test system properties

tucu00 added a commit to brookwc/oozie that referenced this issue Aug 1, 2011
rvs pushed a commit to rvs/oozie that referenced this issue Aug 19, 2011
abayer pushed a commit to cloudera/oozie.old that referenced this issue Jun 21, 2012
…oad test system properties

From: Alejandro Abdelnur <tucu00@gmail.com>

git-svn-id: https://svn.apache.org/repos/asf/incubator/oozie/trunk@1168676 13f79535-47bb-0310-9956-ffa450edef68
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant