Issue 82: Ant Task (Redeaux)
Project Member Reported by virtix, Mar 9, 2008
To keep in alignment with the upcoming runner, add an ant element TEST that
will be all encompassing - is uber-omni legal?. It will accept path and
runner parameters. The path can be dotted notation to a testcase or
testsuite, _or_ the path can be a directory path. To further facilitate
customization and extensibility, param tags will be optionally available to
provide additional instructions to the runner. The observant may also see
that this would have the additional benefit of not only running tests via
ant, but also arbitrary CFCs.

Example:
 <taskdef name="mxunittask" classname="org.mxunit.ant.MXUnitAntTask"
classpath="${mxunit.jar}"   />
<mxunittask server="localhost" port="8500" verbose="true" outputdir="[save
response here]">
  <test name="mytest">
    <param name="runner" value="/mxunit/runner/HttpAntRunner.cfc" />
    <param name="path" value="${component.path}\mxunit\tests\framework" />
    <param name="packageName" value="mxunit.tests.framework" />
    <param name="recurse" value="false" />
    <param name="excludes" value="" />
  </test>

   <!-- Now just run an arbitrary cfc - a non test -->
  <test name="runSomeCfc">
    <param name="runner" value="/myapp/MyCFC.cfc" />
    <param name="q" value="123" />
    <param name="p" value="abc" />
    <param name="method" value="POST" />
    <param name="excludes" value="" />
  </test>
    
 </mxunittask>


 
Jul 14, 2008
Project Member #1 virtix
Just bumping (me) for this ... It seems like the existing Ant task is somewhat
restrictive and doing the above would be better. Also, would provide the opportunity
to  use TestNG. 
Status: Accepted
Cc: -axsaheli -v.rajkumar henkemike
Jan 22, 2009
Project Member #2 virtix
nextgen
Labels: Milestone-Release-2.0
Jun 30, 2010
Project Member #3 virtix
older/outdated issues. archive in google docs. These are either Fixed, deprecated, or invalid

moving to Jira
Status: Fixed