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

[Rafael Pestano (JIRA)]

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

Rafael Pestano edited comment on ARQ-567 at 2/4/17 5:46 AM:
------------------------------------------------------------

I remember doing a small benchmark between arquillian-suite-extension  vs [arquillian core suite|http://discuss.arquillian.org/t/arquillian-core-suite-subsuite-support/162] in *2015 (Mar)* - even made a video: https://www.youtube.com/watch?v=r5e4HvVluyc - the times were pretty similar but what caught my attention was that *arquillian core suite was pretty usable at the time (almost two years ago)* so there must be a really blocker that made the work on this great feature halt.    


PS: At my company it was also a kind of "blocker" having a deploy/undeploy cycle per test class. Fortunately there was suite extension.



was (Author: kwintesencja):
I remember doing a small benchmark between arquillian-suite-extension  vs [arquillian core suite|http://discuss.arquillian.org/t/arquillian-core-suite-subsuite-support/162] in *2015 (Mar)* - even made a video: https://www.youtube.com/watch?v=r5e4HvVluyc - the times were pretty similar but what caught my attention was that *arquillian core suite was pretty usable at the time (almost two years ago)* so there must be a really blocker that made the work on this great feature halt.    


PS: Also at my company it was also a kind of "blocker" having a deploy/undeploy cycle per test class. Fortunately there was suite extension.


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