[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Classpathx-discuss] Use of JUNIT on ClasspathX projects (auto build sys

From: Nic Ferrier
Subject: [Classpathx-discuss] Use of JUNIT on ClasspathX projects (auto build systems)
Date: 22 Feb 2002 04:32:06 +0000

The GNU autoconf archive has a JUNIT macro:

It checks the CLASSPATH for the Junit classes; we could use it for
crypto and other projects that want to use Junit.

I don't think that's what people want though.

I think what's really needed is something to find the junit jar file
(and then perhaps test that it works).

The way I tend to configure my machines is that I try and keep all
my jar files in one place (/usr/local/share/java as it happens) but I
notice that others don't seem to work that way.

Judging by the distribution setups of Jakarta projects a lot of
people just use the distro and do some sort of symlink from /usr/bin
(or some variant).

This means that IF people will have the junit stuff installed:

- it might be in the CLASSPATH, fine if it is.

- it might be a jar file in some well known location, we can probably
  find it by listing some well known locations (eg: Sun's "ext"
  directory, /usr/local/share/java [which is the debian std I think]).

- it might be in the junit distro directory (currently called

If it's the last one I'm not sure how we're expected to find that
directory. I guess it could be in /usr/local or /usr/local/share or
/usr or /usr/share (or the /java variations).

Maybe if it's this last one we just have to tell the user we can't
find it and let them worry about where it should be.

Anyways, once we find it we can then just subst the variable in the
makefile and let people setup whatever tests they like.

Which brings me to my second question:

Do people here want tests that are part of the user build process? In
other words if the tests after the compiles fail is the build invalid?

Or are tests just administrivia? to be used by CVS for check in tests
and developers whilst working on code.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]