[jboss-jira] [JBoss JIRA] (AS7-2062) TS: Check clustering and compat tests

[Ondrej Zizka (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/AS7-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634695#comment-12634695 ] 

Ondrej Zizka commented on AS7-2062:
-----------------------------------

There's been a discussion, which's outcome is that **compat** and **clustering** tests may be in the integration module afterall: https://docspace.corp.redhat.com/docs/DOC-81323
Also **spec** may be melded into integration, as per ALR's explanation:

{quote}
The focus of testsuite/spec and testsuite/api was to enforce a limited 
set of dependencies for these modules.

Breaking into src/main and src/test further enforced that test artifacts 
like EJBs, CDI beans, Servlets, etc were written from a *user 
perspective* and did not contain any AS runtime libs.

This was an unpopular approach.  I still believe that to properly write 
testcases they should be done from a user perspective w/ strict 
dependencies, so I'm in the minority here.

What we've done instead is validated that the "spec" module of JBossAS7 
is exporting out all of the Java EE packages by introducing a 
compile-only test:

https://github.com/jbossas/jboss-as/blob/master/spec-api/test/src/test/java/org/jboss/as/spec/api/test/SpecApiDependencyCheck.java 


...this shows that by introducing a dependency upon the AS7 "spec" POM, 
the user will get all EE libraries on his/her compilation classpath.

To further integrate all the testsuite stuff, everything in 
testsuite/spec, testsuite/api can be flattened into src/test in 
testsuite/integration.  Again, not the approach I preferred for the 
reasons stated above, but the popular one and I've since dropped the issue.

S,
ALR
{quote}
                
> TS: Check clustering and compat tests
> -------------------------------------
>
>                 Key: AS7-2062
>                 URL: https://issues.jboss.org/browse/AS7-2062
>             Project: Application Server 7
>          Issue Type: Sub-task
>          Components: Test Suite
>            Reporter: Ondrej Zizka
>            Assignee: Ondrej Zizka
>
> Stuart Douglas: 
> 1) Clustering tests do not run, and as they require a different arquillian adaptor they must not be in the same maven module as other integration tests.
> 2) Compat tests do not run correctly. Even though they have a different hibernate version specified in the profile, when attempting to run alongside other tests the hibernate version will be overriden. Also as this modifies a build time dependency test classes need to be re-compiled each run, to make sure they are built against the correct hibernate version.
> I'll merge our changes into Stuart's branch since moving poms and scripts is easier than moving Clustering and Compat dirs back to their original location.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira