Wow. I'd hate to add the weight of downloading (on the fly?) an AS
version, starting and stopping it from within a unit test.
As an immediate solution we could add this to the list of manual
release procedures so it gets done with every release, but as you
pointed out manual steps suck too.
IMO, this falls into a category of integration tests (such as testing
with Hibernate releases) which needs to sit outside of the usual
cruise control runs and the functional test suite.
I propose a more formal integration test suite (maybe with it's own
cruise control target?) which:
1) Pulls down different versions of JBC and performs compat/interop
tests (we already have these)
2) Pulls down different Hibernate versions and performs tests on these
3) Pulls down different AS versions and performs tests, including
the JDBCCacheLoader with managed collections as well as other JBC
'use cases' such as SFSBs and HTTP Sessions
3.1) Different combinations of the versions in 2) and 3), to test
EJB3 entity beans
3.2) Combinations including different JGroups versions
So as you can see, we have a shit load of test combinations that can
come out of this. I do see the value here though, it will even make
QA's work in certifying JBC releases against AS versions and JGroups
versions (and even Hibernate versions) easier.
--
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 16 Jan 2007, at 00:42, Galder Zamarreno wrote:
I've been messing around with JDBCCacheLoader and I have realised
that we don't currently have a unit test that can test the
JDBCCacheLoader inside an AS. Ok, we have JDBCCacheLoaderTest that
can work based on the cache-jdbc.properties and you could start AS
manually and test it.
This however is a manual process and when it comes to CC, only
standalone JDBCCacheLoader is being tested.
I think it'd be ideal to basically extend JDBCCacheLoaderTest to
set it up to work with an AS (starting it/stopping it). This would
give us even more confidence and coverage for the
ManagedConnectionFactory area. I might not have time to do that
before I commit my current work for BETA1 but definitely something
worth bearing in mind.
Another question would be of course, what AS version would be
integrate against?
There're various projects out there that have done something
similar, first obviously AS itself and second messaging. What's
your experience with this? What have we learnt about it? Shall we
reuse some code for this? We would need a very limited AS version
actually with JNDI, JDBC Connection Pooling, HS and HS driver.
As you can see, this opens ups whole bunch of questions. Thoughts?
Opinions? Critics?
Cheers,
Galder ZamarreƱo
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat
IT executives: Red Hat still #1 for value
http://www.redhat.com/
promo/vendor/
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev