From: Joe Buck <jbbuck@gmail.com>
To: Noah Watkins <jayhawk@cs.ucsc.edu>
Cc: Joe Buck <buck@soe.ucsc.edu>, ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Setup for building Java unit tests
Date: Mon, 29 Oct 2012 23:29:26 -0700 [thread overview]
Message-ID: <508F73C6.2040700@gmail.com> (raw)
In-Reply-To: <CAPrxi5_jSv9Z-S-RNjF0mrFjgEnXuGt79=+JZx11G0PL=oaJcA@mail.gmail.com>
On 10/29/2012 05:22 PM, Noah Watkins wrote:
> This is my proposal for handling Java unit test compilation:
>
> 1. Go with Joe's suggestion to backport the unit tests to the oldest
> version of JUnit shipping with the latest Ubuntu and Fedora.
>
> 2. Use --with-debug to enable unit test building:
>
> --enable-cephfs-java: no change
> --with-debug --enable-cephfs-java: builds Java tests
>
> 3. configure.ac tests for JUnit dependency in the --with-debug case
> using (a) the common distribution paths (b) the CLASSPATH environment
> variable. Stash location in an autoconf variable for Makefile.am to
> use.
>
> Running the tests from teuthology:
>
> The two dependencies are JUnit (above approach) and a test runner.
> Currently that runner is an Ant build script. Installing that script
> for a --with-debug build in a place like /usr/share/.. is an option,
> but seems like overkill just to get the teuthology tests going.
>
> How about instead we either 1) write a simple runner (few lines of
> java code) and include it in the test jar, or 2) stash a minimal
> Ant-based runner in the teuthology setup script that creates the Ant
> script at run time. Something like:
>
> cat << EOF > build.xml
> <target name="test>
> blah blah
> </target>
> EOF
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
To backfill a conversation Noah and I had offline: it turns out that
JUnit has a command line taskrunner, so we do not need to ship the
build.xml around nor worry about rolling our own.
If we follow the steps Noah laid out (he's going to help me modify
configure to find the JUnit jar) then a workunit can execute the tests
in teuthology via command line invocations (I have this working in my
branch now, save the smarter configuration/build (item #2 above)).
We still need to backport the test code to use the older library but
that's just a bit of time.
-Joe Buck
prev parent reply other threads:[~2012-10-30 6:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 0:22 Setup for building Java unit tests Noah Watkins
2012-10-30 6:29 ` Joe Buck [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=508F73C6.2040700@gmail.com \
--to=jbbuck@gmail.com \
--cc=buck@soe.ucsc.edu \
--cc=ceph-devel@vger.kernel.org \
--cc=jayhawk@cs.ucsc.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.