RE: [jbosscache-dev] Testing JDBCCacheLoader - Embedding AS inside a UT?

IMHO,. I think the usual test suite for JBCCacheLoader that runs through CC should only include only the test for functionality. The interop with AS and Hibernate which would validate the various use cases of JDBCCacheLoader should be done in its own domain. For Example, when releasing a beta of JBC and populating the AS repository with it then we can run a set of interop test cases that would validate JDBCCacheLoader and might be other areas that we can expand on in this domain. That would give us the time to fix issues within JBC before GA release and not clutter the JBC test suite. The same thing could be done with Hibernate. Hany Hany M. Mesha Sr. Software Engineer, Consultant Novell Identity Management Engineering Toronto, Canada hmesha(a)novell.com Mobile: 416-456-6945 skype: hanymesha Novell, Inc. SUSE® Linux Enterprise 10 Your Linux is ready http://www.novell.com/linux +100... Something we can start looking at once 2.0 is out? 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/ ----- Original Message----- From: Manik Surtani [mailto:manik@jboss.org] Sent: 16 January 2007 11:05 To: Galder Zamarreno Cc: jbosscache- dev(a)lists.jboss.org; QA Subject: Re: [jbosscache- dev] Testing JDBCCacheLoader - Embedding AS inside a UT? 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: _______________________________________________ jbosscache- dev mailing list jbosscache- dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosscache- dev