September 2012 - arquillian-issues

[JBoss JIRA] (ARQ-938) Introduce debug property for managed containers

by Dan Allen (JIRA)

Dan Allen created ARQ-938: ----------------------------- Summary: Introduce debug property for managed containers Key: ARQ-938 URL: https://issues.jboss.org/browse/ARQ-938 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: GlassFish Containers, JBoss AS Containers, Tomcat Containers Reporter: Dan Allen It's currently too tedious and inconsistent across managed containers to enable debugging with the VM set to suspend on startup. This task requires hacking on the VM arguments, which is too low level for casual users. Managed containers should offer a configuration property named "debug" that will enable the proper JVM switch to enable debugging with the VM set to suspend on startup. The suspend flag, of course, gives the developer an opportunity to connect the debugger before the tests begin executing. We can either make the debug flag a boolean or we can make it a three state toggle: true, suspend, false. In the latter case, a value of true enables debugging but not suspend, a value of suspend enables debugging and suspend and a value of false disables debugging. This should be implemented for the following containers: JBoss AS 5 - 6 GlassFish 3.1 Tomcat 6 - 7 An issue needs to be filed in the JBoss AS 7 issue tracker after this issue is resolved (so that we settle on the "standard" before lobbying for the feature in AS 7). -- 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

11 years, 5 months

2
1
0 / 0

[JBoss JIRA] (ARQ-1089) Warp should avoid depending on 'provided' container libs on client side

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1089: ---------------------------------- Summary: Warp should avoid depending on 'provided' container libs on client side Key: ARQ-1089 URL: https://issues.jboss.org/browse/ARQ-1089 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Warp Affects Versions: warp_1.0.0.Alpha1 Reporter: Aslak Knutsen Priority: Minor Warp require Servlet api jars on client side to package it self. The AuxiliaryArchiveAppender should be able to package it self without requiring 'provided' libs. {code} java.lang.NoClassDefFoundError: javax/servlet/Filter at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:791) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) at java.net.URLClassLoader.access$100(URLClassLoader.java:71) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:423) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:356) at org.jboss.arquillian.warp.DeploymentEnricher.createAuxiliaryArchive(DeploymentEnricher.java:86) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
2
0 / 0

[JBoss JIRA] (ARQ-964) Verify that all tests in ServerAssertion has been called - prevents false positives

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQ-964: ------------------------------ Summary: Verify that all tests in ServerAssertion has been called - prevents false positives Key: ARQ-964 URL: https://issues.jboss.org/browse/ARQ-964 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Warp Reporter: Lukáš Fryč Fix For: warp_1.0.0.next -- 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

11 years, 5 months

1
7
0 / 0

[JBoss JIRA] (ARQ-967) Warp: client-side filters for waiting for "right" request

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQ-967: ------------------------------ Summary: Warp: client-side filters for waiting for "right" request Key: ARQ-967 URL: https://issues.jboss.org/browse/ARQ-967 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Warp Reporter: Lukáš Fryč Fix For: warp_1.0.0.next When client can fire several requests at time, Warp enriches the first one which comes. Ideally, user should be able to select the appropriate request based on constraints: API proposal: {code:java} Warp.execute(new ClientAction() { ... }).filter(RequestFilter.extension(Extension.XHTML)).verify(...) {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

11 years, 5 months

1
17
0 / 0

[JBoss JIRA] (ARQAJO-118) Support Sizzle locators with Selenium 2

by Lukáš Fryč (Created) (JIRA)

Support Sizzle locators with Selenium 2 --------------------------------------- Key: ARQAJO-118 URL: https://issues.jboss.org/browse/ARQAJO-118 Project: Arquillian Ajocado Issue Type: Feature Request Components: core Reporter: Lukáš Fryč Fix For: 2.0-Tracking -- 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

11 years, 5 months

4
28
0 / 0

[JBoss JIRA] (ARQGRA-165) JSInterfaceFactory test case enrichment

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-165: --------------------------------- Summary: JSInterfaceFactory test case enrichment Key: ARQGRA-165 URL: https://issues.jboss.org/browse/ARQGRA-165 Project: Arquillian Graphene Issue Type: Enhancement Affects Versions: 2.0.0.Alpha2 Reporter: Lukáš Fryč Priority: Minor For creating Java-to-JavaScript calling interface, you need to use call {{JSInterfaceFactory.create(JavaScriptInterfaceToCreate.class)}}. This is not really handy for direct usage: {code:java} @RunWith(Arquillian.class) public class MyTestCase { @Drone private WebDriver browser; @Test public void test() throws InterruptedException { RequestGuard guard = JSInterfaceFactory.create(RequestGuard.class); Assert.assertEquals(RequestType.HTTP, guard.getRequestDone()); } {code} Let's implement test case enrichment, similarly as we did with @FindBy. You can re-use annotation @JavaScript: {code:java} @RunWith(Arquillian.class) public class MyTestCase { @Drone private WebDriver browser; @JavaScript RequestGuard guard; @Test public void test() throws InterruptedException { Assert.assertEquals(RequestType.HTTP, guard.getRequestDone()); } {code} This injection should work also in component objects. -- 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

11 years, 5 months

2
16
0 / 0

[JBoss JIRA] (ARQGRA-166) Enrichment of component objects with context/javascripts/configiuration

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-166: --------------------------------- Summary: Enrichment of component objects with context/javascripts/configiuration Key: ARQGRA-166 URL: https://issues.jboss.org/browse/ARQGRA-166 Project: Arquillian Graphene Issue Type: Feature Request Affects Versions: 2.0.0.Alpha2 Reporter: Lukáš Fryč Following objects should be injectable to Component Objects: * {{GrapheneContext}} * {{GrapheneConfiguration}} * Java-to-JavaScript interfaces -- 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

11 years, 5 months

2
16
0 / 0

[JBoss JIRA] (ARQGRA-191) Support @Drone and @ArquillianResource in Page objects

by Anthony O. (JIRA)

Anthony O. created ARQGRA-191: --------------------------------- Summary: Support @Drone and @ArquillianResource in Page objects Key: ARQGRA-191 URL: https://issues.jboss.org/browse/ARQGRA-191 Project: Arquillian Graphene Issue Type: Feature Request Affects Versions: 2.Future Reporter: Anthony O. In the same way as ARQGRA-189, I think it could be a good thing to support @Drone in Page objects too. Here is my use case : {code} public class FeatureTest extends Arquillian { @Page private HomePage homePage; @Test public testClickMenuRedirect() { FeaturePage featurePage = homePage.open() .doFeature(); assertEquals(featurePage.getSomeAttributeValue(), "someAttributeValue"); } } public class HomePage { @Drone private WebDriver driver; @ArquillianResource URL contextPath; @FindBy(id="featureLinkMenu") private WebElement featureLinkMenu; public HomePage open() { driver.get(URLUtils.buildUrl(contextPath, "pages/feature.xhtml"); } public HomePage doFeature() { guardHttp(featureLinkMenu).click(); return this; } // code for getSomeAttributeValue() } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
17
0 / 0

[JBoss JIRA] (ARQ-837) Managed GlassFish container does not shutdown when a test errors out

by Vineet Reynolds (JIRA)

Vineet Reynolds created ARQ-837: ----------------------------------- Summary: Managed GlassFish container does not shutdown when a test errors out Key: ARQ-837 URL: https://issues.jboss.org/browse/ARQ-837 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: GlassFish Containers Affects Versions: glassfish_1.0.0.CR3 Reporter: Vineet Reynolds When a test errors out, Arquillian does not invoke the {{DeployableContainer.stop()}} implementation of the managed GlassFish container. The GlassFish container started by Arquillian continues to run, and the subsequent test execution produces the expected error message: {{quote}} The server is already running! Managed containers does not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration {{quote}} The GlassFish container implementation should incorporate a mechanism similar to the JBoss AS 7 managed container implementation, to execute the {{asadmin stop-domain}} command in a shutdown hook. -- 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

11 years, 5 months

1
8
0 / 0

[JBoss JIRA] (ARQ-796) Remove the GlassFishRestDeploymentAppender from the GlassFish container adapter

by Vineet Reynolds (JIRA)

Vineet Reynolds created ARQ-796: ----------------------------------- Summary: Remove the GlassFishRestDeploymentAppender from the GlassFish container adapter Key: ARQ-796 URL: https://issues.jboss.org/browse/ARQ-796 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: GlassFish Containers Reporter: Vineet Reynolds Priority: Minor The GlassFishRestDeploymentAppender does not appear to serve any purpose. Although it is implemented as an auxiliary archive appender, it does not appear to be used to enhance the deployment archive. It assumes the responsibility of enhancing the archive with TestEnrichers, but this is already done by the TestEnricher extensions themselves. -- 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

11 years, 5 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues September 2012