March 2013 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1349) Drone: upgrade Selenium to 2.31.0 and PhantomJS to 1.0.3

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1349?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1349: ---------------------------- Summary: Drone: upgrade Selenium to 2.31.0 and PhantomJS to 1.0.3 (was: Drone: upgrade Selenium to 2.31.0 and PhantomJS to 1.0.3-dev) > Drone: upgrade Selenium to 2.31.0 and PhantomJS to 1.0.3 > -------------------------------------------------------- > > Key: ARQ-1349 > URL: https://issues.jboss.org/browse/ARQ-1349 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Lukáš Fryč > Assignee: Karel Piwko > Priority: Minor > Labels: graphene-sprint > Fix For: drone_1.2.0.Alpha2 > > > PhantomJS to 1.0.3-dev contains [~jpapouse]'s changes which allows to use his prototype of binary distribution. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1351) Drone: augment RemoteWebDriver instances automatically

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1351?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1351: ----------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Lukáš Fryč Fix Version/s: drone_1.2.0.Alpha2 Resolution: Done Pushed ustream in https://github.com/arquillian/arquillian-extension-drone/commit/e59445be6... > Drone: augment RemoteWebDriver instances automatically > ------------------------------------------------------ > > Key: ARQ-1351 > URL: https://issues.jboss.org/browse/ARQ-1351 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Labels: graphene-sprint > Fix For: drone_1.2.0.Alpha2 > > > RemoteWebDriver does not implement interfaces such as TakeScreenshot because not all browsers support it. > For proper support, man might use [Augmenter|http://selenium.googlecode.com/svn/trunk/docs/api/java/org/open...] in order to create CGLIB improved RemoteWebDriver class which reflects what capabilities given remote session supports. > The incorporation of automatic augmentation improves usability of Drone. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1350) Drone: allow reuse of session even though all capabilities are not serializable

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1350?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1350: ----------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Lukáš Fryč Fix Version/s: drone_1.2.0.Alpha2 Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/e59445be6... > Drone: allow reuse of session even though all capabilities are not serializable > ------------------------------------------------------------------------------- > > Key: ARQ-1350 > URL: https://issues.jboss.org/browse/ARQ-1350 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Labels: graphene-sprint > Fix For: drone_1.2.0.Alpha2 > > > Remote drivers might store non-serializable instances in Capabilities map. > Drone fails to reuse such browsers since it is not able to store and serialize their capabilities in ReusedSession object. > One example of such a driver is PhantomJSDriver which stores object under key 'proxy': com.google.common.collect.Maps$TransformedEntriesMap. > --- > In order to maximize ability of session reusal, Drone may avoid reusing driver's capabilities at own, but try serialization of each capabilities entry separately and store them in new instance of DesiredCapabilities. > This allows to reuse PhantomJS sessions. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1357) link between arquillian json to stacks runtimes

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1357?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen commented on ARQ-1357: ------------------------------------------ Yes, i'm actually not sure which direction it should go. could argue stacks could list which recommended arquillian container makes sense to use with the runtime... > link between arquillian json to stacks runtimes > ------------------------------------------------ > > Key: ARQ-1357 > URL: https://issues.jboss.org/browse/ARQ-1357 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > > It would be interesting to have a link between https://raw.github.com/forge/plugin-arquillian/master/src/main/resources/... and https://raw.github.com/jboss-jdf/jdf-stack/master/stacks.yaml which defines download locations for runtimes which are not necessarily all in maven. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-417) Support maven deployments

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-417?page=com.atlassian.jira.plugin.sy... ] Karel Piwko updated ARQ-417: ---------------------------- Assignee: (was: Karel Piwko) > Support maven deployments > ------------------------- > > Key: ARQ-417 > URL: https://issues.jboss.org/browse/ARQ-417 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Configuration > Reporter: Adrian Cole > > Microdeployments via ShrinkWrap are a nimble deployment mechanism that allows developers to test bytecode skipping the build. Another usecase is to have ARQ in a CI loop, testing artifacts post-deploy. For this sort of scenario, it would be useful to reuse test cases from the microdeployments, but have them leveraged against code pulled from maven artifacts published in a prior step. > For example, we could have an @Maven annotation which could define the coordinates of an ear file, and place that on a test scenario that performs the war, ejb, cdi, etc tests of from the dependent modules. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1360) Persistence extension doesn't handle certain special characters.

by John Ament (JIRA)

[ https://issues.jboss.org/browse/ARQ-1360?page=com.atlassian.jira.plugin.s... ] John Ament updated ARQ-1360: ---------------------------- Issue Type: Bug (was: Feature Request) > Persistence extension doesn't handle certain special characters. > ---------------------------------------------------------------- > > Key: ARQ-1360 > URL: https://issues.jboss.org/browse/ARQ-1360 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: John Ament > > The persistence extension seems to choke when sql scripts (.sql files) contain certain characters. > 1. If I put "©" in my statement it treats the ; as a terminator. > 2. If I put a new line in my file, it treats that as a terminator. > 3. If I put a / (e.g. </some-tag> from xml) in my SQL, it gets very confused. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1360) Persistence extension doesn't handle certain special characters.

by John Ament (JIRA)

John Ament created ARQ-1360: ------------------------------- Summary: Persistence extension doesn't handle certain special characters. Key: ARQ-1360 URL: https://issues.jboss.org/browse/ARQ-1360 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: John Ament The persistence extension seems to choke when sql scripts (.sql files) contain certain characters. 1. If I put "©" in my statement it treats the ; as a terminator. 2. If I put a new line in my file, it treats that as a terminator. 3. If I put a / (e.g. </some-tag> from xml) in my SQL, it gets very confused. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-863) Poor error message when WebArchive deployed with ".jar" name

by Tommy Tynjä (JIRA)

[ https://issues.jboss.org/browse/ARQ-863?page=com.atlassian.jira.plugin.sy... ] Tommy Tynjä commented on ARQ-863: --------------------------------- I've also encountered this on JBoss AS 7.1.1 and it's an annoying issue. The error message for this is much clearer with e.g. Apache TomEE. I guess this could be fixed either in the JBoss AS 7.1.1 adapter, or make it fail/warn in Arquillian which could detect this kind of error. > Poor error message when WebArchive deployed with ".jar" name > ------------------------------------------------------------ > > Key: ARQ-863 > URL: https://issues.jboss.org/browse/ARQ-863 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.CR8 > Environment: Jboss AS 7.1.1.Final > java version "1.7.0_01" > Java(TM) SE Runtime Environment (build 1.7.0_01-b08) > Java HotSpot(TM) 64-Bit Server VM (build 21.1-b02, mixed mode) > Linux ayaki.localdomain 3.3.0-4.fc16.x86_64 #1 SMP Tue Mar 20 18:05:40 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux > Reporter: Craig Ringer > Priority: Minor > Attachments: ArquillianShrinkwrapWarBug.zip > > > If a WebArchive is deployed with the name ending in ".jar" instead of ".war" (due to, eg, a stupid editing mistake) the error message is not at all helpful. The container will fail to run the test class with a ClassNotFoundException for the test class. > It'd be really nice if the deployer or the packager would detect this issue and report it. > {code} > 13:58:42,082 ERROR [org.jboss.arquillian.protocol.jmx.JMXTestRunner] (pool-1-thread-29) Failed: com.example.shrinkwrapwarbug.DemoTest.testReturnOne: > java.lang.ClassNotFoundException: com.example.shrinkwrapwarbug.DemoTest from [Module "deployment.demo.jar:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.1.GA] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA] > at org.jboss.as.arquillian.service.ArquillianConfig.loadClass(ArquillianConfig.java:130) [arquillian-service:] > at org.jboss.as.arquillian.service.ArquillianService$ExtendedTestClassLoader.loadTestClass(ArquillianService.java:259) [arquillian-service:] > at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:124) [arquillian-service:] > at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:107) [arquillian-service:] > at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.runTestMethod(ArquillianService.java:226) [arquillian-service:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_01] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_01] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_01] > at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_01] > at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:111) [rt.jar:1.7.0_01] > at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:45) [rt.jar:1.7.0_01] > at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:235) [rt.jar:1.7.0_01] > at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) [rt.jar:1.7.0_01] > at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:250) [rt.jar:1.7.0_01] > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) [rt.jar:1.7.0_01] > at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:791) [rt.jar:1.7.0_01] > at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:498) > at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:246) > at org.jboss.remotingjmx.protocol.v1.ServerProxy$InvokeHandler.handle(ServerProxy.java:1034) > at org.jboss.remotingjmx.protocol.v1.ServerProxy$MessageReciever$1.run(ServerProxy.java:215) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_01] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_01] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_01] > {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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-917) Support the use of @Deployment on a static field

by Tommy Tynjä (JIRA)

[ https://issues.jboss.org/browse/ARQ-917?page=com.atlassian.jira.plugin.sy... ] Tommy Tynjä commented on ARQ-917: --------------------------------- I would find the @ReadDeploymentFrom annotation unnecessary. What I've usually encountered is a specific class defining a deployment, and then just extend that class from the test class. Example: {code:java}public class DefaultProjectDeployment { @Deployment public static Archive createDeployment() { ... } } public class MyIntegrationTest extends DefaultProjectDeployment { @Test public void shouldTestSomething() { ... } } {code} Sure it could be benefitial if you want to reference a deployment from a class which contains tests which you don't want to inherit, but I would argue that you should restructure your code in that case. > Support the use of @Deployment on a static field > ------------------------------------------------ > > Key: ARQ-917 > URL: https://issues.jboss.org/browse/ARQ-917 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.0.0.Final > Reporter: Dan Allen > Priority: Minor > > To cut down on verbosity and visual clutter for simple use cases, allow the use of a static field to define a @Deployment. If logic is required to build the deployment, a static block can be used. This also caters well when delegating to a static method. > See examples in this gist: https://gist.github.com/2640101 -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-235) Automatically infer ID locator from field name annotated just by @FindBy

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-235?page=com.atlassian.jira.plugin... ] Juraj Húska updated ARQGRA-235: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Automatically infer ID locator from field name annotated just by @FindBy > ------------------------------------------------------------------------ > > Key: ARQGRA-235 > URL: https://issues.jboss.org/browse/ARQGRA-235 > Project: Arquillian Graphene > Issue Type: Enhancement > Reporter: Lukáš Fryč > Assignee: Juraj Húska > Priority: Minor > Fix For: 2.0.0.Beta1 > > > Consider following: > {code:java} > @FindBy(id = "loginButton") > WebElement loginButton; > @FindBy > WebElement loginButton; > {code} > The lookup should be done using ID or name attribute strategy. -- 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, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues March 2013