[JBoss JIRA] Created: (ARQ-50) research an alternative approach to inheriting from Arquillian base class in TestNG
by Dan Allen (JIRA)
research an alternative approach to inheriting from Arquillian base class in TestNG
-----------------------------------------------------------------------------------
Key: ARQ-50
URL: https://jira.jboss.org/jira/browse/ARQ-50
Project: Arquillian
Issue Type: Feature Request
Affects Versions: 1.0.0-alpha-1
Reporter: Dan Allen
Priority: Minor
This issue is a research and development task to determine if there is an alternative approach that can be used, rather than inheriting from the Arquillian base class, to hook a TestNG test into the Arquillian functionality. JUnit offers a @RunWith annotation which is what the JUnit module uses. The closest hook TestNG seems to offer is the ITestListener interface. However, the question becomes, how does that map to the requirements:
@BeforeSuite -> start container (~ ITestListener.onStart)
@BeforeClass -> deploy (??)
TestMethod/IHookable -> remote call (??)
@AfterClass -> undeploy -> (??)
@AfterSuite -> stop container -> (~ ITestListener.onFinish)
There was discussion on this thread about supporting @RunWith in TestNG: http://markmail.org/message/fxm6bddk6wzqa4yp
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (ARQ-66) provide a mechanism for adding library JARs (test dependencies) to the deployment
by Dan Allen (JIRA)
provide a mechanism for adding library JARs (test dependencies) to the deployment
---------------------------------------------------------------------------------
Key: ARQ-66
URL: https://jira.jboss.org/jira/browse/ARQ-66
Project: Arquillian
Issue Type: Feature Request
Components: Core
Reporter: Dan Allen
Assignee: Pete Muir
Fix For: 1.0.0-alpha-1
The requirement to add extra JARs into the deployment is going to surface fairly early on in the adoption of Arquillian. In our examples, we are sticking to APIs in Java EE, but most projects have third-party JARs on which the application depends. Common examples are a logging framework, Apache Commons libraries, Google Collections, Hibernate Search...anything not available in the container.
We might need to update the @Deployment signature to support:
@Deployment
static Set<Archive<?>> x();
Or maybe a seperate @DeploymentDependencies (this could be defined in e.g. a super class)
@DeploymentDependencies
static Set<Archive<?>> x()
We are also going to need to consider providing APIs for resolving Maven dependencies (groupId, artifactId, version) or resolving test dependencies from the Maven pom. We need to be flexible.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months