Junit Task in Ant

[Will Myers]

Hi,
I'm trying to run some Junit tests with Ant that require a properties file to run (to pick up database info, etc) however the forked JVM doesn't pick up the file, am I doing something stupid? The tests that do not require this file run fine and running the tests in Eclipse is also ok...

    	
<property name="config.file" value="config/config.properties" />

<target name="junit" depends="jar,compile-tests" description="run the 'testcase'-specified or all unit tests">
		<echo>=== Running JUnit Tests ===</echo>
		<copy todir="${test.classes.dir}">
			<fileset dir="${test.src.dir}" excludes="**/*.java" />
		</copy>
		<mkdir dir="${junit.out.dir.xml}" />
		<echo>-D${basedir}/${config.file}</echo>
		<junit fork="yes" failureproperty="junit.failure" errorproperty="junit.error" showoutput="true" printsummary="withOutAndErr" haltonfailure="false">

			<jvmarg value="-D${basedir}/${config.file}" />

			<classpath refid="test.classpath" />
			<sysproperty key="src.dir" value="${test.src.dir}" />
			<formatter type="xml" />

			<batchtest todir="${junit.out.dir.xml}" fork="true">
				<fileset dir="${test.classes.dir}">
					<exclude name="**/*$*.class" />
					<include name="**/Test*.class" />
				</fileset>
			</batchtest>
		</junit>

[Peter Johnson]

It looks like you are passing in the properties file as an system property name, which will make it hard to look up. I would have expected to see something like this instead (replace 'configfile' with the proprty name your app uses to look up the file):

<jvmarg value="-Dconfigfile=${basedir}/${config.file}" />

As an aside, it would be better to place your config file in the classpath and look it up from there - then you don't have to give the app the exact location.