These URLs start from the "Hello World" and tell you how to write an
Ant Build.xml to include the JUnit test cases also.

Could be a good point to start your learning process.

Regards
Kaushal

--- In junit@yahoogroups.com, "greg_plummer" <Greg.plummer@...> wrote:
>
> --- In junit@yahoogroups.com, "kultstatus77" <onlineguy@> wrote:
> >
> > Hi,
> >
> > I'm looking for information on running JUnit tests during an
> automated
> > build process. I do
> >
> > know that it's possible to include JUnit tasks in Ant's build.xml,
> but
> > I'm looking for a way
> >
> > to make JUnit tests mandatory for every piece of code that's written
> > and commited to our
> >
> > CVS. Is there a way to control uploads to CVS regarding JUnit?
> >
> > Another info I'd like to have: is there a way to decide dynamically
> > which tests Ant has to
> >
> > run (like running tests only for changed parts of source code, for
> > example)? I do know that
> >
> > it is common to run all the tests all the time, I'd just like to get
> > to know all the
> >
> > possibilities Ant offers when it comes to JUnit.
> >
>
> You could use the CruiseControl tool for automating your build
> process. You can tell it to run the build every time that something
> is checked into CVS. I would recommend buying the book "Pragmatic
> Project Automation" by Mike Clark. It describes how to automate your
> build process, including how to use CruiseControl and how to run to
> build when things are checked in to CVS.
>

Your message has been successfully submitted and would be delivered to recipients shortly.