Add JUnit tests

[GoogleCodeExporter]

I find it fairly difficult to ensure that minor changes don't cause
regressions without a unit test suite that is easy to run/inspect.  It may
be that the existing bsh tests do fill this need, but my cursory inspection
seems to indicate that they are integration / functionality tests, rather
than focusing on units.  

I've added junit to the build system as part of ticket #28, and if there
are no objections, I'll commit these changes tomorrow.

This added the following ant targets:

   * junit-tests: Runs the tests (everything under ${junit-test-src-dir}
that matches the pattern **/*Test.java).  This target should "just work" --
building whatever is necessary and then running the tests.
   * build-junit-tests: Builds the test source (at the moment, it just
shoves the classes into the ${build-dir})

Results are recorded to a file in `BeanShell/tests/junit-reports`, and that
directory is cleared on `ant clean`.  A summary report is also printed at
the end of the ant output.

Original issue reported on code.google.com by cresw...@gmail.com on 2 Mar 2009 at 8:14

[GoogleCodeExporter]

Committed in revision 35:

http://code.google.com/p/beanshell2/source/detail?r=35

Original comment by cresw...@gmail.com on 4 Mar 2009 at 3:34

• Changed state: Fixed

[GoogleCodeExporter]

milestone=2.1b0

Original comment by pejob...@gmail.com on 25 Feb 2011 at 5:56

• Added labels: milestone-2.1b0

[GoogleCodeExporter]

Original comment by pejob...@gmail.com on 20 Oct 2011 at 7:12

• Added labels: v2.1