From: "Sanne Grinovero" <sanne(a)infinispan.org&gt; To: "infinispan -Dev List" <infinispan-dev(a)lists.jboss.org&gt; Sent: Wednesday, April 22, 2015 12:46:38 AM Subject: [infinispan-dev] Merging of integration testing modules Hi all, as I was exploring the source tree for potentially interesting tests to run on WildFly 9, I'm getting a bit confused by the amount of testing modules. For example, I have no idea why there is a module "infinispan-embedded-query-it" which apparently contains some more tests for "infinispan-query" - but above all I'm not seeing why such tests should be living in a separate module. Also, it looks like there might possibly be quite some redundancy on top of existing tests.

In a similar way, I'm aware "infinispan-as-lucene-integration" was just created as we migrated those from Hibernate Search. But we could merge that in our existing integration tests right? Ideally I was hoping that an activity like a WildFly upgrade would touch just a couple of modules; I think the only reason we should have to separate these in different modules is if it's really important to not have some module installed. If we could achieve that, it should be easier to then start the container only once (twice) to run all tests quicker? Thanks, Sanne _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

Ok, thanks for all explanations! Sorry I felt a bit lost but it makes sense, let's just hope to keep working on minimizing these in the future. Sanne On 22 April 2015 at 13:57, Jiri Holusa <jholusa(a)redhat.com&gt; wrote: > > > ----- Original Message ----- >> From: "Sanne Grinovero" <sanne(a)infinispan.org&gt; >> To: "infinispan -Dev List" <infinispan-dev(a)lists.jboss.org&gt; >> Sent: Wednesday, April 22, 2015 12:46:38 AM >> Subject: [infinispan-dev] Merging of integration testing modules >> >> Hi all, >> as I was exploring the source tree for potentially interesting tests >> to run on WildFly 9, I'm getting a bit confused by the amount of >> testing modules. >> >> For example, I have no idea why there is a module >> "infinispan-embedded-query-it" which apparently contains some more >> tests for "infinispan-query" - but above all I'm not seeing why such >> tests should be living in a separate module. >> Also, it looks like there might possibly be quite some redundancy on >> top of existing tests. > > This module was created for testing of uberjars. According to chat with Tristan, we had to make sure that no dependencies will be pulled other than uberjars. But don't worry, we are planning to change this somehow that we would run the whole testsuite just with uberjars, so there would be no test duplication, but first we need to figure out how. > >> >> In a similar way, I'm aware "infinispan-as-lucene-integration" was >> just created as we migrated those from Hibernate Search. But we could >> merge that in our existing integration tests right? >> >> Ideally I was hoping that an activity like a WildFly upgrade would >> touch just a couple of modules; I think the only reason we should have >> to separate these in different modules is if it's really important to >> not have some module installed. >> If we could achieve that, it should be easier to then start the >> container only once (twice) to run all tests quicker? >> >> Thanks, >> Sanne >> _______________________________________________ >> infinispan-dev mailing list >> infinispan-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/infinispan-dev >> > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev