river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Costers <jonathan.cost...@googlemail.com>
Subject Re: Build failed in Hudson: River-trunk-QA #16
Date Wed, 08 Sep 2010 14:29:24 GMT
Exactly. Thanks Patricia.

You either use "run-tests" and make sure the run.tests property is set
Or you use "run-categories" and make sure the run.categories property is set
(Both properties have default values though).
This all happens from qa/build.xml

In <trunk>/build.xml the target qa.run is setup to call run.categories, with
a specific list of categories (which you can also override if needed).

So .. You have a bunch of options to choose from :-)


2010/9/8 Patricia Shanahan <pats@acm.org>

> Sim IJskes - QCG wrote:
>> On 07-09-10 12:33, Jonathan Costers wrote:
>>> You check out the trunk, set the property "run.tests" in your
>>> <trunk>/build.properties to the tests that fail:
>>> run.tests=com/sun/jini/test/spec/lookupdiscovery/MulticastMonitorAllChange.td
>>> and from<trunk>/qa/build.xml, run the "run-tests" target.
>>> This will only run the test you requested.
>> Jonathan,
>> can you tell me where the mapping from run.categories to run.tests takes
>> place?
> I don't think there is any such mapping. Rather, there are two
> orthogonal systems for selecting tests. One, using run.tests, is based
> on the .td file's file name. The other, using run.categories, is based
> on the categories declared in the .td file.
> Patricia

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message