January 2012 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-540) Support @ArquillianResource URL for in-container test cases

by Ian Brandt (JIRA)

Support @ArquillianResource URL for in-container test cases ----------------------------------------------------------- Key: ARQ-540 URL: https://issues.jboss.org/browse/ARQ-540 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 1.0.0.CR2 Reporter: Ian Brandt >From [IRC|http://echelog.matzon.dk/logs/browse/jbosstesting/1312408800]: {quote} [2:13pm] ianbrandt: aslak, Should @ArquillianResource injection work for in-container test cases? It works fine when I try it for an as-client test, but when I do the same in-container the org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider.protocolMetadata.get() is null, so no context URL. I verified the container is returning a non-null ProtocolMetaData from deploy(...). [2:15pm] aslak: ianbrandt, no it currently doesn't work [2:16pm] aslak: ianbrandt, it probably should, but i'm not sure we have the info incontianer without doing a callback to the client.. [2:16pm] aslak: ianbrandt, but then we don't know which deployment we are when incontianer, so we have a little problem there.. [2:17pm] ianbrandt: aslak, Ah, okay. [2:17pm] aslak: no wait we do [2:18pm] aslak: the Protocol is executed within a DeploymentScope/ContainerScope, so when it gets the callback, it has the correct context.. [2:18pm] aslak: we tho need OperatesOnDeployment support for that tho, cuz you possible want to inject URLs not to your self, but to another deployment on possible another contianer that you should invoke from incontainer [2:19pm] aslak: so from incontianer on dep 1, we can do @ArqRes @OperatesOnDep("dep2") URL url; [2:23pm] ianbrandt: aslak, Makes sense. It's a little more than I could take on at the moment. I was just augmenting the Tomcat tests to show @ArqRes usage. I'll skip it for shouldBeAbleToInvokeServletInDeployedWebApp, and JIRA+Wiki the limitation. {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] (ARQ-647) Implement a convenient way to pass system properties to managed container's JVM.

by Ondrej Zizka (Created) (JIRA)

Implement a convenient way to pass system properties to managed container's JVM. -------------------------------------------------------------------------------- Key: ARQ-647 URL: https://issues.jboss.org/browse/ARQ-647 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 1.0.0.CR5 Reporter: Ondrej Zizka Assignee: Aslak Knutsen Priority: Critical Currently, the only way to pass system props to a container (say, JBoss AS 7), is to use {code} <property name="javaVmArguments">-Dfoo=bar</property> {code} It would be great if system properties could be specified in a special way, like: * by loading a .properties file and setting them in JVM * from a deployment * from a path * from an URL * by a special config elements * by taking them all from the launching JVM; possibly only those with a given prefix Here's how I'd imagine it. Params in [] are optional, with default values. {code} <arquillian xmlns="http://jboss.org/schema/arquillian" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.org/schema/arquillian http://jboss.org/schema/arquillian/arquillian_1_0.xsd"> <container qualifier="jboss" default="true"> <configuration> <property name="jbossHome">target/smoke</property> <property name="javaVmArguments">${server.jvm.args}</property> <property name="serverConfig">${server.config:standalone.xml}</property> <property name="allowConnectingToRunningServer">true</property> <systemProperties> <copyCurrent [prefix="arq."]/> <loadFromDeployment [path="META-INF/arq.system.properties"] [optional="false"]> <loadFromFile [path="../testsuite/my.properties"] [optional="false"]> <loadFromUrl [url="http://foo.redhat.com/foo.properties"] [optional="true"]> <property name="jbossas.ts.integ.dir">${fooBar}</property> </systemProperties> </configuration> </container> </arquillian> {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

6
7
0 / 0

[JBoss JIRA] (ARQ-634) Servlet 2.5 support on Servlet 3.0 containers

by Aslak Knutsen (Created) (JIRA)

Servlet 2.5 support on Servlet 3.0 containers --------------------------------------------- Key: ARQ-634 URL: https://issues.jboss.org/browse/ARQ-634 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Test Protocol SPIs and Implementation Affects Versions: 1.0.0.CR5 Reporter: Aslak Knutsen In a Servlet Container that is defined to use the Servlet 3.0 protocol, but the user defined deployment use a web.xml set to 2.5, the Arquillian Servlet which is added as a web-fragment.xml in the Servlet 3.0 impl will be ignored and Arquillian can not find itself. The Servlet Protocol could possible check the web.xml defined in @Deployment to determine which Servlet Protocol version to use. Meaning the Servlet 3.0 impl can downgrade to Servlet 2.5 in the packaging process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
3
0 / 0

[JBoss JIRA] (ARQ-689) Implement @BeforeDeploy (possibly as an extension)

by Ondrej Zizka (Created) (JIRA)

Implement @BeforeDeploy (possibly as an extension) -------------------------------------------------- Key: ARQ-689 URL: https://issues.jboss.org/browse/ARQ-689 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.0.0.CR5 Reporter: Ondrej Zizka Assignee: Aslak Knutsen -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
4
0 / 0

[JBoss JIRA] (ARQ-729) Do not replace TestNG provided method parameters with values from TestEnrichers

by Dan Spasojevic (JIRA)

Dan Spasojevic created ARQ-729: ---------------------------------- Summary: Do not replace TestNG provided method parameters with values from TestEnrichers Key: ARQ-729 URL: https://issues.jboss.org/browse/ARQ-729 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Test Harness Integration Affects Versions: 1.0.0.CR7 Environment: shrinkwrap 1.0.0-cr-1 arquillian 1.0.0.CR7 jboss AS 7 remote arquillian container 7.1.0CR1b testng 6.3.1 Reporter: Dan Spasojevic At the moment, Arquillian with always replace values provided by TestNG @DataProviders and [TestNG basic injection|http://testng.org/doc/documentation-main.html#dependency-injection] with values produced by TestEnricher+resolve(Method):Object[]. This means that test methods will not receive values produced by the @DataProvider if they are also produced by a TestEnricher. It would be desirable if enrichment was only done if too few values are provided by TestNG. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] (ARQ-705) @ShouldThrowException() - if expected deployment exception is not raised it will stop to invoke other deployments and any tests aren't processed at all

by Pavel Janousek (Created) (JIRA)

@ShouldThrowException() - if expected deployment exception is not raised it will stop to invoke other deployments and any tests aren't processed at all ------------------------------------------------------------------------------------------------------------------------------------------------------- Key: ARQ-705 URL: https://issues.jboss.org/browse/ARQ-705 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Pavel Janousek Let imagine class like:{code} @RunWith(Arquillian.class) public class ImagineTestCase { @Deployment(name="dep1") @ShouldThrowException(Exception.class) public static Archive<?> dep1() { ... } @Deployment(name="dep2") public static Archive<?> dep2() { ... } @Test @OperateOnDeployment("dep1") public void Test1() throws Exception { ... } @Test @OperateOnDeployment("dep2") public void Test2() throws Exception { ... } } {code} Present behavior - if exception isn't raised during deployment dep1 (and this is also the first deployment ARQ want to run), everything other is stopped, although deployment dep2 could work ok and Test2() depends only on dep2. It doesn't make sense for me, I prefer to continue run some tests if anyone is available and isn't blocked by failed deployment -> try to run dep2(), deploy produced artifact and invoke Test2, even dep1() failed (not raised Exception in this case). Do you agree with me? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
4
0 / 0

[JBoss JIRA] (ARQ-733) ClientDeployer.deploy should return a boolean

by George Vagenas (JIRA)

George Vagenas created ARQ-733: ---------------------------------- Summary: ClientDeployer.deploy should return a boolean Key: ARQ-733 URL: https://issues.jboss.org/browse/ARQ-733 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployable Containers SPI Reporter: George Vagenas Priority: Optional In a unmanaged deployement where the ClientDeployer.deploy method is used to deploy the archive, the method should return a boolean to indicate success or failure of the deployment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (ARQ-141) Add option to export the generated Archive to inspect the final deployment

by Aslak Knutsen (JIRA)

Add option to export the generated Archive to inspect the final deployment -------------------------------------------------------------------------- Key: ARQ-141 URL: https://jira.jboss.org/browse/ARQ-141 Project: Arquillian Issue Type: Task Components: Configuration, Documentation Reporter: Aslak Knutsen It is useful for debugging to have Arquillian export the Archive it is about to deploy, specially in IN_CONTAINER mode. Create a ArchiveExporter EventHandler on class level and make the export folder configurable. If option is not set: don't export -- 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

12 years, 8 months

4
10
0 / 0

[JBoss JIRA] Created: (ARQ-350) Map client events 1 to 1 with container events

by Aslak Knutsen (JIRA)

Map client events 1 to 1 with container events ---------------------------------------------- Key: ARQ-350 URL: https://issues.jboss.org/browse/ARQ-350 Project: Arquillian Issue Type: Feature Request Components: Base Implementation, Test Protocol SPIs and Implementation Reporter: Aslak Knutsen We should redo how the test execution lifecycles happen. In the current impl the flow is: Client(BeforSuite, BeforeClass, Before) -> Container(BeforSuite, BeforeClass, Before, Test, After, AfterClass, AfterSuite) -> Client(After, AfterClass, AfterSuite) We should map these 1 to 1 with the incontainer execution and keep the test instance alive between the calls. Client(BeforeClass) -> Container(BeforeClass) Client(Before) -> Container(Before) .. This way the execution is closer to how it normally would be, and extensions can interact with the Container/Environment or Client in the appropriate lifecycles more naturally. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (ARQ-506) Support more complex property types in container configuration

by Gerhard Poul (JIRA)

Support more complex property types in container configuration -------------------------------------------------------------- Key: ARQ-506 URL: https://issues.jboss.org/browse/ARQ-506 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Configuration Reporter: Gerhard Poul Priority: Optional It might sometimes be helpful to support arbitrary property lists within an arquillian configuration, such as when we want to make it possible to pass properties to the underlying container implementations, but that have no effect on the behavior of the arquillian-container-implementation itself. This is not to replace, but to augment the current configuration capability, such that we can provide something like the following in an arquillian.xml: <container qualifier="someQualifier" default="true"> <configuration> <propertyList name="somePropertyName"> <propertyEntry name="somePropertyEntryName" type="java.lang.String" value="someValue" /> <propertyEntry name="somePropertyEntryName2" type="java.lang.Integer" value="1234" /> ... </propertyList> <property name="someOtherProperty">someValue</property> </configuration> </container> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues January 2012