To create and use custom formatter, developer must define formatter class that satisfies following requirements:
Formatter class must extend
org.momeunit.ant.formatter.UnitResultFormatter
class.
Formatter class must contain no-arg constructor.
UnitResultFormatter
class
is the abstract base class for <momeunit>
formatters. It defines callback methods that every formatter
should implement for processing test events and contains
base and utility methods that formatter can use in
generating reports. See api documentation of
org.momeunit.ant.formatter.UnitResultFormatter
for details.
Users should specify formatter class name via
classname
attribute of
<formatter>
nested tag of <momeunit>
and set classpath to include this class via
classpath
attribute or <classpath>
nested tag of <momeunit>
.
Appeal:
If You developed formatter(s), please, share it with community via Extending Ant Integration forum or MoMEUnit-Ant-Extending mailing list.
If You want formatter of some type to be included in ant integration package, please, use "Extending Ant Integration" category of Feature Requests tracker system or Extending Ant Integration forum. I will try to implement it and make available via mailing list or ant integration main or optional package.
To create and use custom preverifier (class that runs preverify
tool),
developer should define preverifier class that satisfies following requirements:
Preverifier class must extend
org.momeunit.ant.preverifier.Preverifier
class.
Preverifier class must contain no-arg constructor.
Preverifier
class is the
abstract base class for all preverifiers. See api documentation of
org.momeunit.ant.preverifier.Preverifier
for details.
Users should specify preverifier class name via
classname
attribute of
<preverify>
nested tag of <momeunit>
and set classpath to include this class via
classpath
attribute or
<classpath>
nested tag
of <momeunit>
.
Appeal:
If You implemented preverifier (class that runs preverify
tool),
please, share it with community via
Extending Ant Integration
forum or
MoMEUnit-Ant-Extending
mailing list.
If You want some preverify tool to be supported by ant integration package, please, use "Extending Ant Integration" category of Feature Requests tracker system or Extending Ant Integration forum. I will try to implement it and make available via mailing list or ant integration main or optional package.
To create and use custom emulator (class that runs emulator
tool),
developer must define emulator class that satisfies following requirements:
Emulator class must extend
org.momeunit.ant.emulator.Emulator
class.
Emulator class must contain no-arg constructor.
Emulator
class is the abstract base class
for all emulators. See api documentation of
org.momeunit.ant.emulator.Emulator
for details.
Users should specify emulator class name via
classname
attribute
of <emulator> nested tag of
<momeunit>
and set classpath
of to include this class via
classpath
attribute
or <classpath>
nested tag of
<momeunit>
.
Appeal:
If You implemented emulator (class that runs emulator
tool),
please, share it with community via
Extending Ant Integration
forum or
MoMEUnit-Ant-Extending
mailing list.
If You want some emulator tool to be supported by ant integration package, please, use "Extending Ant Integration" category of Feature Requests tracker system or Extending Ant Integration forum. I will try to implement it and make available via mailing list or ant integration main or optional package.
Sergio Morozov. 2007