February 2011 - arquillian-issues

[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, 1 month

2
1
0 / 0

[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, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (ARQ-31) Jboss AS Arquillian Deployer

by Aslak (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

13 years, 1 month

3
3
0 / 0

[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, 1 month

2
10
0 / 0

[JBoss JIRA] Created: (ARQ-194) Support multiple bundle deployments

by Thomas Diesler (JIRA)

Support multiple bundle deployments ----------------------------------- Key: ARQ-194 URL: https://jira.jboss.org/browse/ARQ-194 Project: Arquillian Issue Type: Feature Request Components: OSGi Integration Reporter: Thomas Diesler Currently a single test bundle is installed from the client side test runner. We should be able to install an arbitrary number of bundles as part of the test method execution -- 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, 1 month

2
12
0 / 0

[JBoss JIRA] Created: (ARQ-361) Split up Arquillian repository

by Aslak Knutsen (JIRA)

Split up Arquillian repository ------------------------------ Key: ARQ-361 URL: https://issues.jboss.org/browse/ARQ-361 Project: Arquillian Issue Type: Feature Request Affects Versions: 1.0.0.Beta1 Reporter: Aslak Knutsen Fix For: 1.0.0.CR1 The containers need their own release cycle and The Arquillian build and repository is getting to big. We could as a start split out by container owner. containers-jboss - jboss as 4.2, 5, 5.1, 6, 7 - remote, embedded, managed - weld se ee - 1, 11 - embedded - reloaded - osgi - tomcat sip v. containers-glassfish - glassfish 3, 3.1 - remote, embedded containers-apache - tomcat, openejb, openwebbeans containers-other - jetty -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (ARQ-195) Expose a Deployer API to the TestCase

by Aslak Knutsen (JIRA)

Expose a Deployer API to the TestCase ------------------------------------- Key: ARQ-195 URL: https://jira.jboss.org/browse/ARQ-195 Project: Arquillian Issue Type: Feature Request Components: Runtime Enricher SPI Reporter: Aslak Knutsen The TestCase should be able to deploy other deployments as part of it's lifecycle. E.g. - Test the effects of a Deployer - Test lifecycles of Bundles The API needs to be extendable. some Containers might support start/stop as well as deploy/undeploy. -- 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, 1 month

1
5
0 / 0

[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, 1 month

1
5
0 / 0

[JBoss JIRA] Created: (ARQAJO-5) Create a JUnit runner for Ajocado

by Karel Piwko (JIRA)

Create a JUnit runner for Ajocado --------------------------------- Key: ARQAJO-5 URL: https://issues.jboss.org/browse/ARQAJO-5 Project: Arquillian Ajocado Issue Type: Feature Request Affects Versions: 1.5.3 Reporter: Karel Piwko Assignee: Aslak Knutsen Create an JUnit runner with Ajocado. This will become handy if developer wants to use Ajocado without Arquillian, e.g. speed prototyping of functional tests. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (ARQAJO-30) Rename URL object names in configuration names, modify URLUtils accordingly

by Karel Piwko (JIRA)

Rename URL object names in configuration names, modify URLUtils accordingly --------------------------------------------------------------------------- Key: ARQAJO-30 URL: https://issues.jboss.org/browse/ARQAJO-30 Project: Arquillian Ajocado Issue Type: Enhancement Reporter: Karel Piwko Assignee: Lukas Fryc I find current URL object names (contextRoot and contextPath) a bit misleading. 1/ contextRoot and contextPath have same meaning as web application path, that is a part after authority's slash (/) and before next slash e.g. for http://localhost:8080/foo/bar the contextPath and contextRoot is either /foo (contextPath), foo(context-root) in current version contextRoot = http://localhost:8080, contextPath = http://localhost:8080/foo With URLUtils it is not possible to create a path such as http://localhost:8080/foo/ , because new URL(context, spec) called as new URL(contextPath, "/") according to RFC3296 returns http://localhost:8080 However, if contextPath was a string, it could be called as URLUtils(contextRoot, contextPath, "/"), not sure about slash between contextRoot and contextPath though. My suggestions: baseURL (http://localhost:8080/) - URL contextPath/contextRoot(/foo) - String fullURL (http://localhost:8080/foo) - URL -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues February 2011