[arquillian-issues] [JBoss JIRA] Commented: (ARQ-567) Supporting Test Suites (@ArquillianSuite)

[Geoffrey De Smet (JIRA)]

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

Geoffrey De Smet commented on ARQ-567:
--------------------------------------

I don't believe TestSuites are the best solution for sharing @Deployment. I believe a (abstract?) superclass as shown in ARQ-197 is better:
- 1 testsuite can have 80 test classes which share 3 @Deployments (so which should be in 3 superclasses of 3 class hierarchies).
- Testsuites classes are overhead and suffer from bitrot. Just do "run all tests" suffices in most projects. Only a small percentage of the projects really need testsuites because the "run all tests" granularity doesn't suffice.
- spring-testing does it does it by superclass and it seems flexible enough

> Supporting Test Suites (@ArquillianSuite)
> -----------------------------------------
>
>                 Key: ARQ-567
>                 URL: https://issues.jboss.org/browse/ARQ-567
>             Project: Arquillian
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Mousavi Jahan Abadi S. M.
>
> Currently, it is supported that JUnit test cases being run by Arquillian. This feature request is request for supporting test suites too to be run by Arquillian too. Idea is like:
> @RunWith(ArquillianSuite.class)
> @Suite.SuiteClasses( { TestCase1.class, TestCase2.class, .... } )
> public class AllTests{
> 	@Deployment
> 	public static JavaArchive createTestArchive(){
> 		return ShrinkWrap.create(JavaArchive.class,"test.jar");
> 	}
> }
> The advantages of above approach for users of Arquillian framework are:
> - Test cases don't needed to be modified to have: "@RunWith(Arquillian.class)" annotation. In other words, test cases will be pure JUnit code, and no Arquillian code (results in less coding for end users).
> - It is not necessary to include the static "@Deployment" methods in all test cases any more, and only Test Suite need to define the archieving/deployment related setting/definitions.
> The advantage of above approach for framework itself is:
> - From performance point-of-view, it becomes possible for Arquillian to deploy all test cases in the Test Suite into J2EE container in one action (one deploy/undeploy for one test suite, instead of mulitple deploy/undeploy for each test case).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira