Write "Getting started Guide"
-----------------------------
Key: ARQ-40
URL: https://jira.jboss.org/jira/browse/ARQ-40
Project: Arquillian
Issue Type: Task
Reporter: Aslak
Fix For: 1.0.0-alpha-1
how to set it up (maven dep / eclipse deps)
how to write a test (junit @RunWith / @Deployment)
what it supports (injection / packaging)
what it does / how it works
--
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
Recreate demo modules
---------------------
Key: ARQ-44
URL: https://jira.jboss.org/jira/browse/ARQ-44
Project: Arquillian
Issue Type: Task
Reporter: Aslak Knutsen
current layout:
demo = JUnit version
demo-testng = TestNG version
both project contain the same 'business' classes.
Change layout:
demo=business classes
demo-junit=JUnit version
demo-testng=TestNG version
Rename demo to TestSuite ? Make it a full test suite to test all containers/enrichers/runners with all technologies and runner features?
--
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
Demo projects should use package name cdi, not weld.
----------------------------------------------------
Key: ARQ-47
URL: https://jira.jboss.org/jira/browse/ARQ-47
Project: Arquillian
Issue Type: Feature Request
Reporter: Aslak Knutsen
This is a very minor request, but an important one to avoid confusion in terminology. The InjectionTestCase should be in the com.acme.cdi package instead of com.acme.weld. We shouldn't use the term "Weld" unless we are doing some specific to the Weld SPI or implementation. Otherwise, it should just be the standard: CDI. Can you rename that package in the demo and demo-testng projects?
Dan
--
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