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

Peter Probst (JIRA) jira-events at lists.jboss.org
Mon Jul 15 07:18:28 EDT 2013


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

Peter Probst commented on ARQ-567:
----------------------------------

Hello Bernard,
thank you for pinpointing the suite extension and your and aslaks work on that. I've tested extension and the suite alone is working properly, but we are using persistence extension (1.0.0.Alpha5) and then following exception occurs:
java.lang.RuntimeException: Could not create new instance of class org.jboss.arquillian.test.impl.EventTestRunnerAdaptor
	at org.jboss.arquillian.persistence.core.deployment.PersistenceExtensionArchiveAppender.requiredLibraries(PersistenceExtensionArchiveAppender.java:81)
Unfortunately the real exception is eaten and i can't debug within persistence extension.
Thanks, Peter
                
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the arquillian-issues mailing list