Re: [jbosstools-dev] Integration tests on coretests update site?

>>>>> But afaik you still use a mix of reddeer and soa dependencies so not sure it makes sense to add them to coretests at this point ? >>>> Yes this is true but we are going to use reddeer in future and SOA tests >>>> are going to have soa dependencies also AFAIK. >>> As is pointed out in the JIRA, for now we could at least add the bot ext plugin to the site so we don't have to build it before running every test. Bot ext doesn't require red deer so it should be safe. >> This beckon to question why bot ext was ever moved in the first place ? > We wanted to have ability to change our tests after code freeze because > we have to fix tests once new version of JBT/JBDS is available for QE. the base library for doing tests aren't part of that - that should just affect the main test code, right?

>> And why bot tests that requires SOA tests was put together into the same repository. It has its upsides but not sure it is the best way since these plugins life cycle are very different. >> > I think to have SOA tests separated in different repo would be good. I > don't know why it was put to the same repo as "core" integration tests. We cant run a git migraiton on the integration-tests repo to split it up. Your call.

>>> Yes, right now the reason is mostly running the tests on Machydra. But not exclusively - even if we (or anyone else) wants to run a test localy we have to build bot ext first. Having it on the coretests site would solve this. >>> Also, I have some jobs for the EAP QA team set up on the main jboss jenkins instance and it works the same way - unless bot ext is on the coretests site it needs to be build first. I'm not saying that it is such a big problem but I think it would make sense to have this in the coretests site if possible. >> If it needs to be in coretets why is the code moved to integration tests ? >> >> Isn't this just about integreation-tests needing to have its own updatesite ? (which we can get easier once reddeer dependency variance is solved ?) > To have separate update site for integration-tests would be good. I was > just thinking that it would be easier to add integration-tests to > existing coretests update site that it will need less work than creating > new update site and changing our builds to use it. which builds - you guys have your own root parent pom now you can add additional site to afaik. You already did it for reddeer, doing that is not bad in itself, bad was that it was/is? pointing to an updatesite not mirrored/maintained/etc.

/max