Yeah, fine by me ... I'd say if it is just a single formatter class
lets copy it to our test src tree.
--
Manik Surtani
Lead, JBoss Cache
JBoss, a division of Red Hat
Email: manik(a)jboss.org
Telephone: +44 7786 702 706
MSN: manik(a)surtani.org
Yahoo/AIM/Skype: maniksurtani
On 11 Jan 2007, at 17:06, Vladimir Blagojevic wrote:
Hey,
Brian thanks for the pointer. This works! There is a small caveat. We
have to use a special formatter [1] in order to have a nice report
that
indicates which stack was used in a specific test. Since this
formatter
class resides in jboss test project and is not dependent to anything
else should we copy it to our source tree or use a jboss test project
jar?
So how will test report look like, you ask? Each test name will have
appended jgroups stack configuration used. Something like this report
[2] except it is not going to be reddish so much, same colours as
before.
What do you guys say?
[1]
http://fisheye.jboss.org/viewrep/JBoss/jbosstest/src/main/org/jboss/
ant/
taskdefs/XMLJUnitMultipleResultFormatter.java?r=1.3.4.2
[2]
http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.2-
testsuite-1.4/2006
1231190048/results/org/jboss/test/cluster/test/package-summary.html
> Have a look at tests-clustering-all-stacks in the AS
> testsuite build.xml. It basically re-runs all the tests with
> a different config, and info about the config is appended to
> the name of the test report so the 2nd run doesn't overwrite
> the 1st. I'm sure what you'd do would be different, but you
> can probably gets some ideas from there.
>
> - Brian
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev