[JBoss JIRA] Created: (ARQ-351) @Run(AS_CLIENT) support on lifecycle methods and @Test
by Aslak Knutsen (JIRA)
@Run(AS_CLIENT) support on lifecycle methods and @Test
------------------------------------------------------
Key: ARQ-351
URL: https://issues.jboss.org/browse/ARQ-351
Project: Arquillian
Issue Type: Feature Request
Components: Base Implementation, Test Harness Integration
Reporter: Aslak Knutsen
With support for multiple testable deployments and control over lifecycle method execution, we should open for:
@Run() on @Test methods, to override a single test method targeted against a testable deployment ot be executed on the client side.
@Run() on @BeforeClass/@AfterClass/@Before/@After to support lifecycle methods both on client and incontainer.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (ARQ-229) Should split API and Impl in two different modules
by Aslak Knutsen (JIRA)
Should split API and Impl in two different modules
--------------------------------------------------
Key: ARQ-229
URL: https://jira.jboss.org/browse/ARQ-229
Project: Arquillian
Issue Type: Feature Request
Components: Extension - Performance
Reporter: Aslak Knutsen
Assignee: St?le Pedersen
Fix For: 1.0.0.Alpha4
ContextAppenders are auto included in the runtime if found on ClassPath.
We should consider splitting the performance extension into two modules, api and impl. Where API contains all the user facing annotations etc. With this you can compile against API and only include impl when you actually want to run the test case in performance 'mode', e.g. via a special profile.
mvn test -P jbossas-remote-6,performance-test
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (ARQ-315) add configuration property to JBoss AS containers to explode deployment
by Dan Allen (JIRA)
add configuration property to JBoss AS containers to explode deployment
-----------------------------------------------------------------------
Key: ARQ-315
URL: https://jira.jboss.org/browse/ARQ-315
Project: Arquillian
Issue Type: Feature Request
Components: JBoss Containers
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
In some cases, it's necessary to have JBoss AS explode the deployment on the server. For instance, if the framework (such as Weld Servlet) uses archive scanning, it wouldn't be able to handle the VFS files. While a more formal solution may be appropriate, a stopgap measure is often to have the archive exploded once it arrives at the server. The DeploymentManager offers this option, and thus we should have a configuration property for it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months