[JBoss JIRA] Created: (ARQ-313) ARQ should support Multi-module (Multiple WAR deployments) testing
by Lincoln Baxter III (JIRA)
ARQ should support Multi-module (Multiple WAR deployments) testing
------------------------------------------------------------------
Key: ARQ-313
URL: https://jira.jboss.org/browse/ARQ-313
Project: Arquillian
Issue Type: Feature Request
Components: Packaging Enricher SPI
Reporter: Lincoln Baxter III
It would be useful if you could return multiple deployments, potentially as a list of archives, and then run tests either AS_CLIENT that would interact against all deployments (however the container handles them,) or run with one deployment as the primary and run tests in IN_CONTAINER from the perspective of that WAR.
This would effectively allow testing of multi-module WAR deployments or large-scale applications that are broken up under different ServletContexts.
--
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, 10 months
[JBoss JIRA] Created: (ARQ-362) @Run(AS_CLIENT) support on @Test
by Aslak Knutsen (JIRA)
@Run(AS_CLIENT) support on @Test
--------------------------------
Key: ARQ-362
URL: https://issues.jboss.org/browse/ARQ-362
Project: Arquillian
Issue Type: Feature Request
Components: Base Implementation, Test Harness Integration
Reporter: Aslak Knutsen
With support for multiple testable deployments and control off lifecycle method execution, we should open for:
@Run() on @Test methods, to override a single test method targeted against a testable deployment to 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, 10 months
[JBoss JIRA] Created: (ARQ-152) Support multiple container configurations for same container type
by Aslak Knutsen (JIRA)
Support multiple container configurations for same container type
-----------------------------------------------------------------
Key: ARQ-152
URL: https://jira.jboss.org/browse/ARQ-152
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Reporter: Aslak Knutsen
Configuration need to support multiple container configurations for the same container type with a runtime 'flag' for switching configuration.
UseCase:
Different configuration for test/stage servers. e.g.
{code:XML}
<arquillian xmlns="http://jboss.com/arquillian"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:jboss="urn:arq:org.jboss.arquillian.jbossas.remote60">
<jboss:container id="jbossTest">
<localDeploymentBindAddress>my.domain</localDeploymentBindAddress>
<remoteServerAddress>remote.test.server</remoteServerAddress>
<remoteServerHttpPort>8080</remoteServerHttpPort>
</jboss:container>
<jboss:container id="jbossStage">
<localDeploymentBindAddress>my.domain</localDeploymentBindAddress>
<remoteServerAddress>remote.stage.server</remoteServerAddress>
<remoteServerHttpPort>8181</remoteServerHttpPort>
</jboss:container>
</arquillian>
{code}
--
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, 10 months
[JBoss JIRA] Created: (ARQ-192) Install OSGi bundles in memory
by Thomas Diesler (JIRA)
Install OSGi bundles in memory
------------------------------
Key: ARQ-192
URL: https://jira.jboss.org/browse/ARQ-192
Project: Arquillian
Issue Type: Task
Reporter: Thomas Diesler
Currently the OSGiDeploymentPackager transforms a JavaArchive into a VF
private VirtualFile toVirtualFile(Archive<?> archive) throws IOException, MalformedURLException
{
// [TODO] Can this be done in memory?
ZipExporter exporter = archive.as(ZipExporter.class);
String archiveName = archive.getName();
int dotIndex = archiveName.lastIndexOf(".");
if (dotIndex > 0)
archiveName = archiveName.substring(0, dotIndex);
File target = File.createTempFile(archiveName + "-", ".jar");
exporter.exportZip(target, true);
target.deleteOnExit();
return AbstractVFS.getRoot(target.toURI().toURL());
}
We should be able to install the Archive directly and in-memory
--
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, 10 months
[JBoss JIRA] Created: (ARQ-164) NPE in DeployableTestBuilder
by Jesper Pedersen (JIRA)
NPE in DeployableTestBuilder
----------------------------
Key: ARQ-164
URL: https://jira.jboss.org/browse/ARQ-164
Project: Arquillian
Issue Type: Bug
Components: Deployable Containers SPI
Affects Versions: 1.0.0.Alpha2
Reporter: Jesper Pedersen
I get:
java.lang.NullPointerException
at org.jboss.arquillian.impl.DeployableTestBuilder.build(DeployableTestBuilder.java:82)
at org.jboss.arquillian.impl.DeployableTestBuilder.build(DeployableTestBuilder.java:71)
at org.jboss.arquillian.junit.Arquillian.<init>(Arquillian.java:68)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
Any component that uses a SPI implementation should guard against null values - if there is a non-null requirement of course - and throw an IllegalArgumentException with a descriptive error message.
--
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, 10 months