I am kind of +0 about the move of the integration tests into a separate project.
Many projects like CXF and Karaf have the integration tests in a separate project. There the benefit is that the individual modules have their unit tests which run very fast and the integration tests only have to run after all modules are built. So this allows to have a little bit faster development cycle. In syncope the itests are in the core module which does not have real unit tests anyway. So I think the advantage of moving the itests out is not so big. This may change if we start creating unit tests for the the core classes. I am not so sure though how well unit tests would work there. Additionally the whole syncope build is very fast (about 3 mins) compared to more than one hour in e.g. camel. Christian On 10.12.2012 09:56, Francesco Chicchiriccò wrote: > Hi all, > let's try to make some order :-) > > The current situation is: > > 1. I am about to merge the DEV_ROLE_PROVISIONING branch into the trunk > 2. Jan (with help from Christian) will then merge the cxf branch into > the trunk and also apply some refactoring (see SYNCOPE-241 and > SYNCOPE-242) by splitting the core module > > After (2) will have completed, we can think to discuss about > additional refactoring, IMO. > > > Now, I am not completely sure about the proposed refactoring, > especially after what I expect from (2): could you please give more > details about the benefits? > For example, I am not sure that moving test classes and resources in > separate modules (hence making such classes part of the release) is > necessarily a good thing. > > Regards. > > On 10/12/2012 09:41, Andrei Shakirin wrote: >> Hi JB, >> >> I mean just maven module, sure :) >> What do you prefer as a name? >> a) itests >> b) systests >> >> Cheers, >> Andrei. >> >>> -----Original Message----- >>> From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] >>> Sent: Sonntag, 9. Dezember 2012 20:47 >>> To: dev@syncope.apache.org >>> Subject: Re: Extract syncope system/integration tests into separate >>> project >>> >>> Hi Andrei, >>> >>> by separate project, you mean a "real" project (with its own release >>> cycle, >>> artifacts, svn repo, etc), or just a Maven module ? >>> >>> I don't think it's a good idea to have it in a separate "real" >>> project as it's >>> coupled to the others artifacts/modules/codebase. >>> >>> But a itest Maven module it's a good think (it's what we have most of >>> projects, like Karaf, ServiceMix, etc). >>> >>> Regards >>> JB >>> >>> On 12/09/2012 07:37 PM, Andrei Shakirin wrote: >>>> Hi, >>>> >>>> I would suggest to extract integration and system tests into separate >>> project. From my perspective it makes management of tests and build >>> process more transparent and easy. Of course, JUnit tests will stay in >>> corresponded projects. >>>> Does it make sense? >>>> >>>> Cheers, >>>> Andrei. >
