Introduction

This tool provides a custom ant task which can be used to invoke and run your dpUInt tests from an ANT build file. This set of ant tasks has some features (such as the fileset) which are ignored by the test runner currently but will be available shortly in the next beta version of dpUInt.

Add your content here.

Details

Requirements:

• To use the dpUInt ant task you need to have the Adobe Air dpUInt Test Runner installed. This can be downloaded from the dpUInt project site http://code.google.com/p/dpuint/
• An installed copy of ANT of 1.6.x or greater

How to use the dpUInt ANT tag <dpuint>:

• You need to put dpUintAnt.jar in your system class path so ant can find it, or you can import it into the ANT script at runtime with ANT <PATH> tag

	<path id="libraries">
		<fileset dir="${targetdir}">
	        	<include name="**/*.jar"/>
	        </fileset>
	</path>

• You then need to import and define the dpUInt Ant tag in your build script with the classname "net.digitalprimates.ant.tasks.dpUint.DpUint".

	<taskdef name="dpunit"
		classname="net.digitalprimates.ant.tasks.dpUint.DpUint"
		classpathref="libraries" />

• Now that the DpUInt Ant tag has been defined in your build file you can call it with the <dpuint> tag, like so.

	<target name="runTests">
		<dpunit
			debug="true"
			headless="false"
			testRunner="C:/Program Files/dpUintAir/dpUintAir.exe"
			outputDir="${basedir}">
			<fileset dir="${basedir}">
	            		<include name="**/*.swf"/>
			</fileset>
		</dpunit>
	</target>

The attributes of the <dpuint> tag are:

• debug - return debug information to the console
• headless="true|false" - to run the Air application in a headless (no ui) mode or to launch and run the air application as a full application. (Please note, this does not mean this can be launched from a truly headless server, dpUInt will still instantiate visual objects, just not waste the time showing you a tree and progress bar)
• testRunner="" - The path to your installed copy of the dpUInt air application
• outputDir="" - the location where the test runner should write out to disk all of the test results.
• <fileset> - a fileset of all the flex test suites modules (compiled as mx:Modules). (Pleaase note, the use of the fileSet tag will be explained in detail along with the upcoming updates to dpUInt)