[arquillian-issues] [JBoss JIRA] (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=12685543#comment-12685543 ] 

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

@Bernard Let me revise my standpoint :)
TestSuites should be possible, but a TestSuite should not be required to enable ARQ-197's sharing of a deployment across multiple test classes (to avoid the deployment performance cost). It should be configurable via a superclass too.
Because this would mean that adding a new Test class requires to add line in the TestSuite (which people would forget).
And - more annoyingly - simple running the test (or all tests in the package org.x.y) in the IDE might not work, as they 'll have to be activated through the test suite.

In any case, I only care about sharing a deployment (ARQ-197) via a common superclass.




                
> 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.
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