testing infrastructure confusion

Ian Springer ian.springer at redhat.com
Wed Mar 21 14:06:37 UTC 2012


The three new modules I added, and the two Arquillian modules that Lukas
wrote, are all specific to testing the plugin container or plugins
running inside it - the modules are not dependent on or dependencies of
anything under enterprise.So I thought core was the logical place for
them. That being said, I can see that these modules clutter the core
directory and make it harder to get a quick view of the non-test core
modules. So I could lump them in a subdirectory:

core/itest
|-- arquillian-integration
   |-- container
   |-- archive
|-- plugin-test-api

|-- plugin-test-util

|-- plugin-container-itest


As for the other modules...

cli-tests - let's move these under enterprise (e.g.
enterprise/remoting/cli-itests)
integration-tests
|-- apache-plugin-test - let's try to move this into the apache plugin
module
|-- jndi-access - looks like itests for
AllowRhqServerInternalsAccessPermission; Lukas, can this be moved
somewhere under enterprise?
|-- mod_cluster-plugin-test- let's try to move this into the mod_cluster
plugin module
|-- rest-api - Heiko, can this be moved somewhere under enterprise
(perhaps enterprise/gui/rest-war-itests)?

test-utils - I think these are fine where they are, since they are
generic test utils that are used by both core and enterprise modules

enterprise/server/itests - I think these are fine where they are


Mazz, anyone else, what do you think?


On 03/20/2012 10:42 AM, John Mazzitelli wrote:
> Oh, looks like I missed another one :/
>
> enterprise/server/itests
>
>
> On Tue, 2012-03-20 at 10:40 -0400, John Mazzitelli wrote:
>> I just looked at what maven modules we have to support testing and I
>> found the following under modules/
>>
>> cli-tests
>> integration-tests
>> test-utils
>> core/arquillian-integration
>> core/plugin-container-itest
>> core/plugin-test-api
>> core/plugin-test-util
>>
>> Is there anyway we can make this simpler? This is starting to get
>> confusing that we have several test modules and they are spread out in
>> modules/ and under modules/core/.
>>
>> Does any one person know how all of these work who can document these in
>> the wiki? Can we combine them all under a single "modules/testing"
>> module??
>>
>>
>>
>> _______________________________________________
>> rhq-devel mailing list
>> rhq-devel at lists.fedorahosted.org
>> https://fedorahosted.org/mailman/listinfo/rhq-devel
>
>
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/rhq-devel


-- 
Ian Springer
Principal Software Developer
JBoss Operations Network
Red Hat
ian.springer at redhat.com



More information about the rhq-devel mailing list