[
https://issues.jboss.org/browse/SEAMFORGE-349?page=com.atlassian.jira.plu...
]
Lincoln Baxter III commented on SEAMFORGE-349:
----------------------------------------------
Actually, I think this is even easier than scanning the class. If the project packaging is
WAR, then make a WebArchive, if it is JAR, then make a JavaArchive :) PS. Who are you?
When Creating an Arquillian test and the class file select requires
any web-only features the Test.java class should create a WebArchive rather than a
JavaArchive.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: SEAMFORGE-349
URL:
https://issues.jboss.org/browse/SEAMFORGE-349
Project: Forge
Issue Type: Enhancement
Components: JBoss Tools Integration, Plugin Repository
Affects Versions: 1.0.0.Beta3
Environment: Any environment
Reporter: Craig Schwarzwald
End result of the created arquillian test class should have Deployment method as
follows:
@Deployment public static WebArchive createDeployment() {
return ShrinkWrap.create(WebArchive.class, "test.war")
.addPackage(<ClassBeingTested>.class.getPackage()) //To ensure all
necessary classes are added
.addAsResource("META-INF/persistence.xml") //If this file exists
.addAsWebResource(new StringAsset("<beans/>"),
ArchivePaths.create("WEB-INF/beans.xml"));
}
Currently when running:
arquillian create-test --class MyClass.java
An Arquillian test is created, but as a JavaArchive which is not correct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira