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

[Felipe C. (JIRA)]

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

Felipe C. commented on ARQ-567:
-------------------------------

Hello all!

I agree with [~rezarahman]!
I made a POC in a project at my work and some members didn't like the deploy and test time. Because of that they don't want to use Arquillian, it bothers me a lot. I did another POC on my last work using https://github.com/felipecalmeida/arquillian-suite-extension and I was sattisfied with the results and the kind of development.
I don't know your schedule for the next releases, but maybe you could integrate this issue.
Also some new integrations could be great also, like http://concordion.org/, it's useful to QA results.

Thank's!

> Supporting Test Suites (@ArquillianSuite)
> -----------------------------------------
>
>                 Key: ARQ-567
>                 URL: https://issues.jboss.org/browse/ARQ-567
>             Project: Arquillian
>          Issue Type: Feature Request
>            Reporter: Mousavi Jahan Abadi S. M.
>            Assignee: Aslak Knutsen
>             Fix For: 1.2.0.Alpha1
>
>
> 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 was sent by Atlassian JIRA
(v7.2.3#72005)