[JBoss JIRA] Created: (ARQ-360) Honor system property for exporting test archives
by Dan Allen (JIRA)
Honor system property for exporting test archives
-------------------------------------------------
Key: ARQ-360
URL: https://issues.jboss.org/browse/ARQ-360
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Often times a developer will want to dump the test archives to inspect them when debugging a test failure. Currently, this requires editing the arquillian.xml descriptor (assuming there is one) and refreshing the project. As an alternative, it would be convenient to have a system property that would activate this feature for a single test run:
mvn test -Darquillian.exportPath=target/
Since the goal of this run is to export the archives, not necessarily run the tests (since presumably the test is currently failing), it would be nice to have an "export only" mode that just generates the archives.
mvn test -Darquillian.exportPath=target/ -Darquillian.exportOnly=true
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (ARQ-345) Arquillian needs to deliver a raw archive to the test container
by David Bosschaert (JIRA)
Arquillian needs to deliver a raw archive to the test container
---------------------------------------------------------------
Key: ARQ-345
URL: https://issues.jboss.org/browse/ARQ-345
Project: Arquillian
Issue Type: Feature Request
Components: Base Implementation
Reporter: David Bosschaert
In order to support performance tests and deployment testing Arquillian needs to be able to deliver raw archives to the tests being run inside a container.
* For performance tests it's important to measure exactly the amount of time a deployment might take and this measurement should not be polluted with the time it takes a client to construct a bundle and the time spent in sending the archive over a socket to the test running in the container.
* For deployment tests, the test itself needs to directly exercise the deployment APIs using test archives, it cannot let the Arquillian framework do this.
This is currently possible in the OSGiContainerImpl class in the getTestArchive() method
https://github.com/jbosgi/arquillian/blob/jbosgi/protocols/osgi/src/main/...
however this functionality is currently limited to OSGi deployments only.
To be able to implement this properly, Shrinkwrap needs to be capable of running in a module system such as OSGi, so this issue depends on https://issues.jboss.org/browse/SHRINKWRAP-242 .
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (ARQ-198) Install bundle from maven dependencies
by Thomas Diesler (JIRA)
Install bundle from maven dependencies
--------------------------------------
Key: ARQ-198
URL: https://jira.jboss.org/browse/ARQ-198
Project: Arquillian
Issue Type: Feature Request
Components: OSGi Containers
Reporter: Thomas Diesler
* Another interesting feature would be the installation of bundles that are declared as dependencies in the maven pom.xml. Let's say in the pom.xml you have the following dependency:
<dependency>
<groupId>org.apache.felix</groupId>
<artifactId>org.apache.felix.configadmin</artifactId>
<version>${configadmin.version}</version>
</dependency>
then it would be great if you could install that bundle simply through some installBundle("org.apache.felix", "org.apache.felix.configadmin") API which would infer the version from the maven context. Both Pax Exam and Apache ServiceMix testing have this feature and it makes integration with the maven buildsystem really easy.
--
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, 7 months
[JBoss JIRA] Created: (ARQ-216) Extensions should be able to communicate between Client and Container
by Aslak Knutsen (JIRA)
Extensions should be able to communicate between Client and Container
---------------------------------------------------------------------
Key: ARQ-216
URL: https://jira.jboss.org/browse/ARQ-216
Project: Arquillian
Issue Type: Feature Request
Components: Frameworks, Test Protocol SPIs and Implementation
Reporter: Aslak Knutsen
Arquillian should provide a Communication channel between the Container and Client so extension can push custom data between.
This is needed in cases like code coverage where data is collected in container, but reported on on the client side.
I think it should be ok to open up the TestRunner Protocols for 'custom' data as well as the TestResults. This means we can piggy back on all the Protocol impls with out much extra work.
--
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, 7 months