Mailing-List: contact lenya-dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lenya Developers List" <lenya-dev@cocoon.apache.org>
To: lenya-dev@cocoon.apache.org
From: Andreas Hartmann <andreas@apache.org>
Subject: Re: DefaultSiteTreeTestCase FAILS
Date: Sun, 01 Jun 2003 23:10:29 +0200
Lines: 29
Message-ID: <bbdpvp$7gm$1@main.gmane.org>
References: <32840.141.154.73.181.1054388078.squirrel@mail.wyona.com>
      <bbalog$g55$1@main.gmane.org>
 <32855.141.154.73.181.1054484278.squirrel@mail.wyona.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.4) Gecko/20030529
In-Reply-To: <32855.141.154.73.181.1054484278.squirrel@mail.wyona.com>
Sender: news <news@main.gmane.org>

Michael Wechner wrote:

[...]

 > right, but how do we encourage (or rather enforce) people to write
 > more test cases (during Sprints on a regular basis would be a
 > possibility...)?

I could imagine the following first steps:

- all existing tests must run
- in the beginning - ask the committers personally to write tests
- putting some links to a good JUnit tutorial etc. in the docs

 > No problem, but how we can we make this path relative?

The only solution I found is to pass the path as a JVM parameter
to the test. I'm calling the test class from the build script
(not via the TestRunner) so I can access the main(String[]) arguments.

The problem is that the test must be invoked from the build script.
I hardcoded the paths as a fallback in the class, so that I can run
my tests from the IDE which makes test debugging easier.

If you're interested in the implementation, have a glance at the
AntTask and workflow test cases.

Andreas


---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org