From issues at jboss.org Thu Jun 13 08:23:06 2019 From: issues at jboss.org (Ehsan Zaery Moghaddam (Jira)) Date: Thu, 13 Jun 2019 08:23:06 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-567) Supporting Test Suites (@ArquillianSuite) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746363#comment-13746363 ] Ehsan Zaery Moghaddam commented on ARQ-567: ------------------------------------------- Any update since last year? :) > 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 > Priority: Major > 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.12.1#712002) From issues at jboss.org Thu Jun 13 08:35:05 2019 From: issues at jboss.org (Reza Rahman (Jira)) Date: Thu, 13 Jun 2019 08:35:05 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-567) Supporting Test Suites (@ArquillianSuite) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746370#comment-13746370 ] Reza Rahman commented on ARQ-567: --------------------------------- Indeed... > 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 > Priority: Major > 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.12.1#712002)