May 2017 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQGRA-504) Implemented a new method "clickable" in wait API

by Matous Jobanek (JIRA)

Matous Jobanek created ARQGRA-504: ------------------------------------- Summary: Implemented a new method "clickable" in wait API Key: ARQGRA-504 URL: https://issues.jboss.org/browse/ARQGRA-504 Project: Arquillian Graphene Issue Type: Enhancement Components: api Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: 2.2.2 It should wait till an element is visible & enabled -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-504) Implemented a new method "clickable" in wait API

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-504?page=com.atlassian.jira.plugin... ] Matous Jobanek updated ARQGRA-504: ---------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/166 > Implemented a new method "clickable" in wait API > -------------------------------------------------- > > Key: ARQGRA-504 > URL: https://issues.jboss.org/browse/ARQGRA-504 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: api > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.2.2 > > > It should wait till an element is visible & enabled -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-501) Error when checking for the invisibility of elements

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-501?page=com.atlassian.jira.plugin... ] Matous Jobanek commented on ARQGRA-501: --------------------------------------- Hi, thank you for reporting this. I was trying to reproduce the issue, but without any success - everything is working in my case... However, when I take a look at the code where the exception was thrown - there could be one corner case when this could occur. Here is my proposal how I would fix the issue: https://github.com/arquillian/arquillian-graphene/pull/168 > Error when checking for the invisibility of elements > ---------------------------------------------------- > > Key: ARQGRA-501 > URL: https://issues.jboss.org/browse/ARQGRA-501 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.2.0 > Reporter: Krassimir Valev > > I get the following error message, when waiting for an element to disappear: > {code:java} > java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 > at java.util.ArrayList.rangeCheck(ArrayList.java:653) > at java.util.ArrayList.get(ArrayList.java:429) > at org.jboss.arquillian.graphene.enricher.WebElementUtils$3.getTarget(WebElementUtils.java:104) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.getTarget(GrapheneProxyHandler.java:149) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.getTarget(GrapheneContextualHandler.java:189) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:162) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:47) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:43) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:209) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:96) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:43) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:212) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:208) > at com.sun.proxy.$Proxy316.isDisplayed(Unknown Source) > at org.openqa.selenium.support.ui.ExpectedConditions$20.apply(ExpectedConditions.java:585) > at org.openqa.selenium.support.ui.ExpectedConditions$20.apply(ExpectedConditions.java:581) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:209) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:96) > {code} > The wait condition looks like this: > {code:java} > return waitGui() > .withTimeout(timeout, TimeUnit.SECONDS) > .pollingEvery(100, TimeUnit.MILLISECONDS) > .ignoring(NoSuchElementException.class, StaleElementReferenceException.class) > .ignoring(InvocationTargetException.class) > .until(ExpectedConditions.invisibilityOfElementLocated(locator)); > {code} > The very same condition used to work with graphene-webdriver 2.0.3.Final and selenium-bom 2.50.1, but it fails now after upgrading to graphene-webdriver 2.2.0 and selenium-bom 3.3.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-928) Automation Test

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-928?page=com.atlassian.jira.plugin.sy... ] Bartosz Majsak closed ARQ-928. ------------------------------ Resolution: Won't Do > Automation Test > --------------- > > Key: ARQ-928 > URL: https://issues.jboss.org/browse/ARQ-928 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1868) JVM waits for Spacelift's cached threads to timeout causing its termination delay

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1868?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak closed ARQ-1868. ------------------------------- Resolution: Out of Date > JVM waits for Spacelift's cached threads to timeout causing its termination delay > --------------------------------------------------------------------------------- > > Key: ARQ-1868 > URL: https://issues.jboss.org/browse/ARQ-1868 > Project: Arquillian > Issue Type: Bug > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Attachments: spacelift_thread_dump.txt > > > In the current implementation of ExecutorService there is this constructor:; > {code} > public ExecutionServiceImpl() { > this.service = Executors.newCachedThreadPool(); > this.scheduledService = Executors.newScheduledThreadPool(1); > } > {code} > JavaDoc for cachedThreadPool says: > {quote} > Threads that have not been used for sixty seconds are terminated and removed from the cache. Thus, a pool that remains idle for long enough will not consume any resources. > {quote} > While this is indeed useful, it seems that even JVM has nothing to do, it waits for these cached threads to timeout (so they are not used some time (60 seconds by default) so they are destroyed eventually) and only after their destruction whole JVM terminates properly. > Please consider to lower the timeout so user does not have to wait or figure out other pooling mechanism. > This issue effects mainly command line tools which hangs without obvious reason and debugging it why is a nightmare. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2066) Support for JUnit 5

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2066?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak commented on ARQ-2066: ------------------------------------- Totally agree with you! This will require new test runner and the work has been started in the community https://developer.jboss.org/message/970675?et=watches.email.thread#970675 > Support for JUnit 5 > ------------------- > > Key: ARQ-2066 > URL: https://issues.jboss.org/browse/ARQ-2066 > Project: Arquillian > Issue Type: Feature Request > Reporter: Tobias Stadler > > The final relase of JUnit 5 is scheduled for Q1 2017. It would be nice if Arquillian would support it then. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2110) DBUnit Config allowEmptyFields

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2110?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak resolved ARQ-2110. --------------------------------- Resolution: Done > DBUnit Config allowEmptyFields > ------------------------------ > > Key: ARQ-2110 > URL: https://issues.jboss.org/browse/ARQ-2110 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Derek Foster > Assignee: Bartosz Majsak > > The current version of the persistence extension is based on DbUnit 2.4.8, but since then DbUnit has updated to 2.5.3 which has included a feature of allowing empty fields, as opposed to forcing null fields in databases. This feature is quite useful for seeding data. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2110) DBUnit Config allowEmptyFields

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2110?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak edited comment on ARQ-2110 at 5/23/17 5:01 AM: -------------------------------------------------------------- Thank you for the report! In fact we are already on 2.5.3 version, just not released yet. was (Author: bmajsak): Thank you for the report! > DBUnit Config allowEmptyFields > ------------------------------ > > Key: ARQ-2110 > URL: https://issues.jboss.org/browse/ARQ-2110 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Derek Foster > Assignee: Bartosz Majsak > > The current version of the persistence extension is based on DbUnit 2.4.8, but since then DbUnit has updated to 2.5.3 which has included a feature of allowing empty fields, as opposed to forcing null fields in databases. This feature is quite useful for seeding data. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2110) DBUnit Config allowEmptyFields

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2110?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak commented on ARQ-2110: ------------------------------------- Thank you for the report! > DBUnit Config allowEmptyFields > ------------------------------ > > Key: ARQ-2110 > URL: https://issues.jboss.org/browse/ARQ-2110 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Derek Foster > Assignee: Bartosz Majsak > > The current version of the persistence extension is based on DbUnit 2.4.8, but since then DbUnit has updated to 2.5.3 which has included a feature of allowing empty fields, as opposed to forcing null fields in databases. This feature is quite useful for seeding data. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2088) When test is skipped because of an assumption, Arquillian's test result is passed

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2088?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak closed ARQ-2088. ------------------------------- Resolution: Won't Fix As discussed above - not related to core and fixed in the other project. > When test is skipped because of an assumption, Arquillian's test result is passed > --------------------------------------------------------------------------------- > > Key: ARQ-2088 > URL: https://issues.jboss.org/browse/ARQ-2088 > Project: Arquillian > Issue Type: Enhancement > Components: core > Affects Versions: 1.1.13.Final > Reporter: Matous Jobanek > Assignee: Dipak Pawar > > When you run Arquillian test with an assumption: {{Assume.assumeFalse(true);}} then the test is skipped. The same also say both IDE and maven surefire, but Arquillian's {{TestResult}} retrieved in {{After}} phase contains status Passed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues May 2017