March 2011 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Updated: (ARQAJO-17) fix JQueryLocator.getNthOccurence and .getNthChild() methods to return proper values

by Lukas Fryc (JIRA)

[ https://issues.jboss.org/browse/ARQAJO-17?page=com.atlassian.jira.plugin.... ] Lukas Fryc updated ARQAJO-17: ----------------------------- Fix Version/s: 1.0.0.Alpha3 (was: 1.0.0.Alpha2) > fix JQueryLocator.getNthOccurence and .getNthChild() methods to return proper values > ------------------------------------------------------------------------------------ > > Key: ARQAJO-17 > URL: https://issues.jboss.org/browse/ARQAJO-17 > Project: Arquillian Ajocado > Issue Type: Bug > Environment: richfaces-selenium:1.5.0.Final > Reporter: Lukas Fryc > Assignee: Lukas Fryc > Fix For: 1.0.0.Alpha3 > > > The getNthChild internally uses :nth-child jQuery selector, but it isn't proper meaning for such operation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (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 updated ARQAJO-15: ----------------------------- Fix Version/s: 1.0.0.Alpha3 (was: 1.0.0.Alpha2) > 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 > Fix For: 1.0.0.Alpha3 > > > 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (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 updated ARQAJO-14: ----------------------------- Fix Version/s: 1.0.0.Alpha3 (was: 1.0.0.Alpha2) > 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 > Fix For: 1.0.0.Alpha3 > > > 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (ARQ-396) OpenEJB test enricher does not load jndi.properties unless specified in arq.xml

by David Allen (JIRA)

OpenEJB test enricher does not load jndi.properties unless specified in arq.xml ------------------------------------------------------------------------------- Key: ARQ-396 URL: https://issues.jboss.org/browse/ARQ-396 Project: Arquillian Issue Type: Bug Affects Versions: 1.0.0.Alpha5 Reporter: David Allen Assignee: David Allen Priority: Minor During work on ARQ-379, the ability to load jndi.properties from the classpath is gone. It must be specified in arquillian.xml as a file path. For this fix, if no jndi.properties path is specified in arq.xml, it should at least default to the classpath again. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (ARQ-399) Allow for configurable Jetty Configuration classes

by Ales Justin (JIRA)

Allow for configurable Jetty Configuration classes -------------------------------------------------- Key: ARQ-399 URL: https://issues.jboss.org/browse/ARQ-399 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Jetty Containers Affects Versions: 1.0.0.Alpha5 Reporter: Ales Justin Assignee: Aslak Knutsen Fix For: 1.0.0.Beta1 Current Jetty Embeddable Container 7 works on all v7 and v8 releases, but its usage of Jetty Configuration classes is hardcoded, which conflicts with renamed classes in in v7.2+. If this was configurable, user could change which Configuration classes should be used. Perhaps providing both default would be good; e.g. one for pre-7.2, one for 7.2+ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (ARQ-55) TestNG @Test(dependsOnMethods="") does not work when running inside the container

by Aslak Knutsen (JIRA)

TestNG @Test(dependsOnMethods="") does not work when running inside the container --------------------------------------------------------------------------------- Key: ARQ-55 URL: https://jira.jboss.org/jira/browse/ARQ-55 Project: Arquillian Issue Type: Bug Components: TestNG Reporter: Aslak Knutsen "methodX is not allowed to depend on methodY" The way Arquillian invokes the remote container it creates a new 'suite' pr TestCase pr test method. Since only one test method is invoked pr suite, TestNGs dependsOnMethods fail. -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-167) Support @EJB.mappedName for TestClass injection

by Aslak Knutsen (JIRA)

Support @EJB.mappedName for TestClass injection ----------------------------------------------- Key: ARQ-167 URL: https://jira.jboss.org/browse/ARQ-167 Project: Arquillian Issue Type: Feature Request Components: Runtime Enricher SPI Affects Versions: 1.0.0.Alpha2 Reporter: Aslak Knutsen We should support letting the user set the mappedName on the injection in the test case to avoid having to follow our naming standards. (until we can do it more reliable, https://jira.jboss.org/browse/ARQ-77) Needs to document the potential jndi naming changes between Embedded EJB containers and Remote Containers(packaging).. -- 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, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (ARQ-374) Consider renaming Selenium extension to more general name

by Karel Piwko (JIRA)

Consider renaming Selenium extension to more general name --------------------------------------------------------- Key: ARQ-374 URL: https://issues.jboss.org/browse/ARQ-374 Project: Arquillian Issue Type: Task Components: Extension - Selenium Reporter: Karel Piwko Assignee: Aslak Knutsen Fix For: 1.0.0.Beta1 I'm considering renaming Arquillian Selenium extension to Arquillian Web Test extension or something similar. It would show that the extension is able to hold multiple test frameworks apart from Selenium. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (ARQ-356) JBoss AS Managed does not allow to set RMI port used for deployment. Forces users to use 1099

by Aslak Knutsen (JIRA)

JBoss AS Managed does not allow to set RMI port used for deployment. Forces users to use 1099 --------------------------------------------------------------------------------------------- Key: ARQ-356 URL: https://issues.jboss.org/browse/ARQ-356 Project: Arquillian Issue Type: Feature Request Components: JBoss Containers Affects Versions: 1.0.0.Alpha4 Reporter: Aslak Knutsen Priority: Minor The RMIPort has to be set specifically on the ServerManager for it to be able to connect to anything else then the default: 1099. Open up for RMIPort configuration in arquillian.xml for the JBoss Managed containers. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
5
0 / 0

[JBoss JIRA] Created: (ARQ-384) Prepare Alpha-5 release

by Aslak Knutsen (JIRA)

Prepare Alpha-5 release ----------------------- Key: ARQ-384 URL: https://issues.jboss.org/browse/ARQ-384 Project: Arquillian Issue Type: Task Reporter: Aslak Knutsen Assignee: Aslak Knutsen -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues March 2011