Create usage examples
---------------------
Key: ARQ-35
URL: https://jira.jboss.org/jira/browse/ARQ-35
Project: Arquillian
Issue Type: Task
Reporter: Aslak
We need multiple examples on how to test different aspects/technologies.
Transactions, ejb, jms, weld, servlet, jsf.. etc etc
--
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
Jboss AS Arquillian Deployer
----------------------------
Key: ARQ-31
URL: https://jira.jboss.org/jira/browse/ARQ-31
Project: Arquillian
Issue Type: Feature Request
Reporter: Aslak
It could be interesting to have a Arquillian Deployer in AS.
scanning for *-tests.jar(Maven style) files and deploying them wrapped as a runnable testsuite/testcase via ie jmx.
this would basically bypass the 'client' side of Arquillian and run directly on the server.
--
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
Create a archive repository service for containers not supporting ShrinkWrap directly
-------------------------------------------------------------------------------------
Key: ARQ-26
URL: https://jira.jboss.org/jira/browse/ARQ-26
Project: Arquillian
Issue Type: Task
Reporter: Aslak
Not all containers will support ShrinkWrap directly.
Create a 'Service' or Abstract Deployable Container class to handle Archive<?> to URL mappings.
ie, Remote Jboss instances need a http url to deploy.
--
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
@Deployment should have some intelligent defaults
-------------------------------------------------
Key: ARQ-30
URL: https://jira.jboss.org/jira/browse/ARQ-30
Project: Arquillian
Issue Type: Task
Reporter: Aslak
The API @Deployment should have some smart auto packaging options to help package the test
- Add The TestCase itself
- Add the TestCase package recursively
- Add Resources in TestCase package ?
--
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
General Configuration module
----------------------------
Key: ARQ-33
URL: https://jira.jboss.org/jira/browse/ARQ-33
Project: Arquillian
Issue Type: Task
Reporter: Aslak
Most things are loaded dynamically based on what's on classpath, but we still need some 'common' configuration for the containers.
The configuration should be able to get configuration from multiple locations and override in some order..
system properties, properties file, maven config etc..
Some of the configuration is global, like port/bindaddress, but container specific configuration is also needed, ie Embedded AS having what 'profile' to run.
--
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
Create a extendable way for handling packaging on all levels
------------------------------------------------------------
Key: ARQ-25
URL: https://jira.jboss.org/jira/browse/ARQ-25
Project: Arquillian
Issue Type: Task
Reporter: Aslak
All the 4 levels "User Test Case", "Test Framework", "Arquillian" and "The Container" should be / need to add classes in the deployment.
The "User Created" archive might not be the one that is deployed, and the deployed archive might not be a ear..
Need a way to 'dynamically' add dependencies to 'any' Archive<?> on all 4 levels
--
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
Create a common TestEnricher lib for all jboss containers
---------------------------------------------------------
Key: ARQ-34
URL: https://jira.jboss.org/jira/browse/ARQ-34
Project: Arquillian
Issue Type: Task
Reporter: Aslak
All jboss instances can share the same TestEnrichers set.
The following test enrichers should be provided:
- EJB 3
- @EJB remote/local injection
- @Resource injection
- @TransactionAttribute test method level
- CDI
- @Inject injection
The Enrichers should probably use reflection to not directly depend on the cdi/ebj libs etc..
--
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