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: Hudson build is back to normal : River-trunk-QA #51
Date Sat, 06 Nov 2010 16:40:19 GMT
2010/11/6 Peter Firmstone <jini@zeus.net.au>

> Infra provided a solaris zone:
> Sun Microsystems Inc.   SunOS 5.10      Generic January 2005
> -bash-3.00$ uname -a
> SunOS river 5.10 Generic_137112-04 i86pc i386 i86pc
> -bash-3.00$ prtconf -D
> System Configuration:  Sun Microsystems  i86pc
> Memory size: 8192 Megabytes
> System Peripherals (Software Nodes):
> prtconf: devinfo facility not available
> The KDC and squid just need to be set up.  We could establish a registrar
> there also I suppose.
> OK great. There is a JIRA issue open already for this I believe.

> Well I don't think Junit would be suitable, since multiple jvm's are
> employed.  I've also had to modify some jtreg tests that made some
> assumptions about ClassLoader visibility (jre/lib/ext related) and failed
> later when we made some changes.  The qa suite might be suitable, but I
> don't think the effort's worthwhile, we can't guarantee that we're
> simulating the failure conditions properly, even if only a few of us run
> these tests, it's better than everyone running them if they're not genuinely
> simulating failure conditions.

Not all of them use/need a multi VM setup. Those are candidates for JUnit.
The others would be QA candidates.
I'm not saying it is easy to migrate any of these though, doing so requires
knowledge of how the jtreg framework operates, as well as the proposed
target framework (JUnit, QA).

> JUnit's good when we're only testing a single object implementation, we can
> document and expect people to utilse the qa suite for more complex tests.


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