December 2011 - arquillian-issues

[JBoss JIRA] Created: (ARQ-74) Base test deployment on project in which test is run

by Pete Muir (JIRA)

Base test deployment on project in which test is run ---------------------------------------------------- Key: ARQ-74 URL: https://jira.jboss.org/jira/browse/ARQ-74 Project: Arquillian Issue Type: Feature Request Reporter: Pete Muir A common testing scenario will be to deploy the artifact generated by the current project, and run tests against it. For example, say my project was building a war, I want to be able to deploy that war, inserting the test case and any beans into the deployment, and have my tests run. In this case the deep control of the classpath through shrinkwrap is getting in the way. -- 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, 11 months

3
8
0 / 0

[JBoss JIRA] Created: (ARQ-160) Improve Exception messages / handling

by Aslak Knutsen (JIRA)

Improve Exception messages / handling ------------------------------------- Key: ARQ-160 URL: https://jira.jboss.org/browse/ARQ-160 Project: Arquillian Issue Type: Feature Request Affects Versions: 1.0.0.Alpha2 Reporter: Aslak Knutsen We should create an Exception message id set linking to wiki articles/faq about the specific error case. This will help on the user experience and exposure of jboss.org -- 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, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (ARQ-224) Create Wiki entries for every Error Message id

by Aslak Knutsen (JIRA)

Create Wiki entries for every Error Message id ---------------------------------------------- Key: ARQ-224 URL: https://jira.jboss.org/browse/ARQ-224 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen Every Exception ID Arquillian defines should be mapped to a open wiki page where we can add description about the exception, why and how to fix it etc.. -- 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, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (ARQ-232) Redesign Servlet protocol to be more human friendly

by Aslak Knutsen (JIRA)

Redesign Servlet protocol to be more human friendly --------------------------------------------------- Key: ARQ-232 URL: https://jira.jboss.org/browse/ARQ-232 Project: Arquillian Issue Type: Feature Request Components: Test Protocol SPIs and Implementation Reporter: Aslak Knutsen Priority: Minor We should redesign the Servlet communication protocol to be more Rest api like. This will make it easier for humans to execute tests outside of the Arquillian Client and opens for other clients to communicate with the test. http://arquillian.pastebin.com/XHsfaycJ Add support for html output -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-442) Change Examples modules to a container sanity test suite

by Aslak Knutsen (JIRA)

Change Examples modules to a container sanity test suite -------------------------------------------------------- Key: ARQ-442 URL: https://issues.jboss.org/browse/ARQ-442 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta1 Reporter: Aslak Knutsen The current examples modules should be recreated as a sanity test suite for the containers. Currently all containers have their own simple tests for validating the functionality. These container tests should be merged with the examples and created as a test suite. The test suite needs to be split up by package / module based on EE v / technology to support all containers(easy maven filtering). The containers should depend on this test suite and not the other way around. todo: research how to include a external module as a test suite for a module. (copy-dependencies / extract ? / container config etc) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
2
0 / 0

[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

13 years, 11 months

2
2
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

13 years, 11 months

3
3
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

13 years, 11 months

6
7
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

13 years, 11 months

4
4
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

13 years, 11 months

4
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues December 2011