February 2011 - arquillian-issues

[JBoss JIRA] Moved: (ARQAJO-14) Harden FailureLoggingTestListener againts SeleniumException failures

by Lukas Fryc (JIRA)

[ https://issues.jboss.org/browse/ARQAJO-14?page=com.atlassian.jira.plugin.... ] Lukas Fryc moved JBQA-3834 to ARQAJO-14: ---------------------------------------- Project: Arquillian Ajocado (was: JBoss QA) Key: ARQAJO-14 (was: JBQA-3834) Component/s: (was: Cheiron) > Harden FailureLoggingTestListener againts SeleniumException failures > -------------------------------------------------------------------- > > Key: ARQAJO-14 > URL: https://issues.jboss.org/browse/ARQAJO-14 > Project: Arquillian Ajocado > Issue Type: Feature Request > Reporter: Lukas Fryc > Assignee: Lukas Fryc > > When selenium fails to run command in failure logging listener, all next test cases fails due to fail of listener. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Moved: (ARQAJO-15) Implement atomic call of AjaxWaiting$waitForChangeAndReturn

by Lukas Fryc (JIRA)

[ https://issues.jboss.org/browse/ARQAJO-15?page=com.atlassian.jira.plugin.... ] Lukas Fryc moved JBQA-3733 to ARQAJO-15: ---------------------------------------- Project: Arquillian Ajocado (was: JBoss QA) Key: ARQAJO-15 (was: JBQA-3733) Component/s: (was: Cheiron) > Implement atomic call of AjaxWaiting$waitForChangeAndReturn > ----------------------------------------------------------- > > Key: ARQAJO-15 > URL: https://issues.jboss.org/browse/ARQAJO-15 > Project: Arquillian Ajocado > Issue Type: Feature Request > Reporter: Lukas Fryc > Assignee: Lukas Fryc > Priority: Minor > > Currently, there need to be 2 operations to run operation "waitForChangeAndReturn": > selenium.waitForCondition(js(format("{0} != '{1}'", scriptString, oldValueString)), this.getTimeout()); > String retrieved = selenium.getEval(script); > This idea is to implement this operation atomically in meaning of Selenium. > It can a) made tests atomic and stable, b) improve run time a little > All previous methods fails: > a) call getEval evaluating doWaitForCondition followed by expression to evaluate > b) implement own method on Selenium.prototype to call doWaitForCondition and getEval in sequence (this method also lacks the possibility of passing timeout) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Moved: (ARQAJO-10) Replace selenium.keyDownNative(String) with selenium.keyDownNative(java.awt.event.KeyEvent)

by Lukas Fryc (JIRA)

[ https://issues.jboss.org/browse/ARQAJO-10?page=com.atlassian.jira.plugin.... ] Lukas Fryc moved JBQA-3938 to ARQAJO-10: ---------------------------------------- Project: Arquillian Ajocado (was: JBoss QA) Key: ARQAJO-10 (was: JBQA-3938) Issue Type: Feature Request (was: Task) Component/s: (was: Cheiron) > Replace selenium.keyDownNative(String) with selenium.keyDownNative(java.awt.event.KeyEvent) > ------------------------------------------------------------------------------------------- > > Key: ARQAJO-10 > URL: https://issues.jboss.org/browse/ARQAJO-10 > Project: Arquillian Ajocado > Issue Type: Feature Request > Reporter: Lukas Fryc > Assignee: Lukas Fryc > > Currently selenium API support String only for passing the type of native events (replayed by jawa.awt.Robot). > It will be better to use jawa.awt.event.KeyEvent enumeration instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Moved: (ARQAJO-11) Replace selenium.keyDown(String) with selenium.keyDown(KeyCode)

by Lukas Fryc (JIRA)

[ https://issues.jboss.org/browse/ARQAJO-11?page=com.atlassian.jira.plugin.... ] Lukas Fryc moved JBQA-3937 to ARQAJO-11: ---------------------------------------- Project: Arquillian Ajocado (was: JBoss QA) Key: ARQAJO-11 (was: JBQA-3937) Issue Type: Enhancement (was: Task) Component/s: (was: Cheiron) > Replace selenium.keyDown(String) with selenium.keyDown(KeyCode) > --------------------------------------------------------------- > > Key: ARQAJO-11 > URL: https://issues.jboss.org/browse/ARQAJO-11 > Project: Arquillian Ajocado > Issue Type: Enhancement > Reporter: Lukas Fryc > Assignee: Lukas Fryc > > Currently, keyDown and similar methods accepts String JavaScript key codes. > It will be better to accept enumeration or extensible enumeration instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (ARQ-366) Chained exceptions from container cannot always be deserialized

by Elias Ross (JIRA)

Chained exceptions from container cannot always be deserialized --------------------------------------------------------------- Key: ARQ-366 URL: https://issues.jboss.org/browse/ARQ-366 Project: Arquillian Issue Type: Bug Components: Weld Containers Affects Versions: 1.0.0.Alpha4 Environment: JBoss 6.0.0 Reporter: Elias Ross This is an example: org.jboss.arquillian.impl.event.FiredEventException: java.lang.IllegalStateException: Error launching test com.acme.cache.NamedCacheTest public void com.acme.cache.NamedCacheTest.testThis() at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:68) at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115) at org.jboss.arquillian.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:157) at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:244) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:207) at org.jboss.arquillian.junit.Arquillian$5$1.evaluate(Arquillian.java:225) at org.jboss.arquillian.junit.Arquillian$MultiStatementExecutor.execute(Arquillian.java:297) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:221) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:163) at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:186) at org.jboss.arquillian.junit.Arquillian$MultiStatementExecutor.execute(Arquillian.java:297) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:182) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:127) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) Caused by: java.lang.IllegalStateException: Error launching test com.acme.cache.NamedCacheTest public void com.acme.cache.NamedCacheTest.testThis() at org.jboss.arquillian.protocol.servlet_3.ServletMethodExecutor.invoke(ServletMethodExecutor.java:61) at org.jboss.arquillian.impl.handler.ContainerTestExecuter.callback(ContainerTestExecuter.java:50) at org.jboss.arquillian.impl.handler.ContainerTestExecuter.callback(ContainerTestExecuter.java:40) at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) ... 26 more Caused by: java.lang.ClassNotFoundException: org.jboss.weld.exceptions.IllegalArgumentException at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:603) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1574) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1495) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1731) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1946) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1870) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1752) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at org.jboss.arquillian.protocol.servlet_3.ServletMethodExecutor.execute(ServletMethodExecutor.java:88) at org.jboss.arquillian.protocol.servlet_3.ServletMethodExecutor.invoke(ServletMethodExecutor.java:57) ... 29 more As you can see here, "org.jboss.weld.exceptions.IllegalArgumentException" isn't in the classpath of the client. It shouldn't be necessary to include the Weld jarfiles in my build path to receive this exception. Instead, Arquillian could convert these exceptions into more generic ones. (On the server, logging something useful would be appreciated.) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (ARQ-307) In an EAR deployment, allow the customization of test.war

by Marius Bogoevici (JIRA)

In an EAR deployment, allow the customization of test.war --------------------------------------------------------- Key: ARQ-307 URL: https://jira.jboss.org/browse/ARQ-307 Project: Arquillian Issue Type: Feature Request Affects Versions: 1.0.0.Alpha4 Reporter: Marius Bogoevici In an EAR deployment, the test.war attached by arquillian replaces a test.war configuration provided by the user. Ideally, it should be possible to allow test writers to attach artifacts to it. -- 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, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (ARQ-176) Create integration tests for all CDI related deployment scenarios

by Aslak Knutsen (JIRA)

Create integration tests for all CDI related deployment scenarios ----------------------------------------------------------------- Key: ARQ-176 URL: https://jira.jboss.org/browse/ARQ-176 Project: Arquillian Issue Type: Task Components: Integration Test Suite Reporter: Aslak Knutsen Create a deployment integration test suite for all possible CDI related deployment types. EJB, WAR, JAR 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, 4 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues February 2011