[JBoss JIRA] Created: (ARQ-422) Rename static field Arquillian.caughtTestException so it doesn't show in auto-complete
by Dan Allen (JIRA)
Rename static field Arquillian.caughtTestException so it doesn't show in auto-complete
--------------------------------------------------------------------------------------
Key: ARQ-422
URL: https://issues.jboss.org/browse/ARQ-422
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Base Implementation
Affects Versions: 1.0.0.Alpha5
Reporter: Dan Allen
Priority: Minor
When adding Arquillian support to a test class, the caughtTestException gets in the way of auto-complete. For instance, when you type:
@RunWith(Arquillian.c
Then press <Ctrl>+Space you get
.caughtTestException
.class
On more than one occasion, I've accidentally selected .caughtTestException. This field should either be renamed to CAUGHT_TEST_EXCEPTION, queuedTestException or moved to another class (the best solution).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[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
[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