May 2017 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-2116) Open DSL to configure DBUnit

by Alex Soto (JIRA)

[ https://issues.jboss.org/browse/ARQ-2116?page=com.atlassian.jira.plugin.s... ] Alex Soto reassigned ARQ-2116: ------------------------------ Assignee: Alex Soto > Open DSL to configure DBUnit > ---------------------------- > > Key: ARQ-2116 > URL: https://issues.jboss.org/browse/ARQ-2116 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > > Currently we only rely on default DBUnit settings which makes it usable only for simple cases such as HSQL DB. For other db engines such as MySQL this is not enough, as we don't have a way to define more specific settings such as DataType, case sensitivity or more db engine specific tweaks. > http://dbunit.sourceforge.net/properties.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2116) Open DSL to configure DBUnit

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-2116: ----------------------------------- Summary: Open DSL to configure DBUnit Key: ARQ-2116 URL: https://issues.jboss.org/browse/ARQ-2116 Project: Arquillian Issue Type: Sub-task Reporter: Bartosz Majsak Currently we only rely on default DBUnit settings which makes it usable only for simple cases such as HSQL DB. For other db engines such as MySQL this is not enough, as we don't have a way to define more specific settings such as DataType, case sensitivity or more db engine specific tweaks. http://dbunit.sourceforge.net/properties.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2116) Open DSL to configure DBUnit

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2116?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-2116: -------------------------------- Fix Version/s: persistence_1.0.0.next > Open DSL to configure DBUnit > ---------------------------- > > Key: ARQ-2116 > URL: https://issues.jboss.org/browse/ARQ-2116 > Project: Arquillian > Issue Type: Sub-task > Reporter: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > Currently we only rely on default DBUnit settings which makes it usable only for simple cases such as HSQL DB. For other db engines such as MySQL this is not enough, as we don't have a way to define more specific settings such as DataType, case sensitivity or more db engine specific tweaks. > http://dbunit.sourceforge.net/properties.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2116) Open DSL to configure DBUnit

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2116?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-2116: -------------------------------- Component/s: Extension - Persistence > Open DSL to configure DBUnit > ---------------------------- > > Key: ARQ-2116 > URL: https://issues.jboss.org/browse/ARQ-2116 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > Currently we only rely on default DBUnit settings which makes it usable only for simple cases such as HSQL DB. For other db engines such as MySQL this is not enough, as we don't have a way to define more specific settings such as DataType, case sensitivity or more db engine specific tweaks. > http://dbunit.sourceforge.net/properties.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2115) Create Arquillian adapter for WebSphere 9

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-2115?page=com.atlassian.jira.plugin.s... ] Gerhard Poul updated ARQ-2115: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Create Arquillian adapter for WebSphere 9 > ----------------------------------------- > > Key: ARQ-2115 > URL: https://issues.jboss.org/browse/ARQ-2115 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Reporter: Marián Macik > Assignee: Gerhard Poul > > Hi, guys, > I have created the Arquillian adapter for WebSphere 9. Here is the summary of the PR [1]: > \#### Short description of what this resolves: > Hi, guys, > my name is Marian Macik and I work at Red Hat as QE Engineer on [jBPM|https://github.com/kiegroup/jbpm] project. This PR introduces Arquillian container adapter for WebSphere 9. We have been using it at Red Hat in our QE automation for about two months without any issues. It is copied from adapter for WebSphere 8.5 (as WebSphere 8.5 was copied from WebSphere 8). There were only some minor changes when it comes to system paths pointing at WebSphere dependencies (jgss-provider and ws-admin-client). > However, since WebSphere 9, wsadmin is using jython27 by default. Jython21 is still supported and to use jython21, 'com.ibm.ws.admin.client.forJython21_9.0.jar' should be used. Moreover, the new wsadmin jar has additional libraries which are not used by Arquillian (such as Python JSR 223 implementation) and might cause issues when deploying and running tests. If this happens, simply override this property with jython21 jar: > {code} > -Dws_admin_client_jar_name=com.ibm.ws.admin.client.forJython21_9.0.jar > {code} > I added this property because the new jython27 wsadmin implementation was causing issues since it loaded unwanted classes on the classpath. Of course, by default the new jython27 wsadmin is used, override is optional. > I have also run the enclosed tests with my own arquillian.xml and they have passed. > Thanks, > Marian > [1] https://github.com/arquillian/arquillian-container-was/pull/29 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2115) Create Arquillian adapter for WebSphere 9

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-2115?page=com.atlassian.jira.plugin.s... ] Gerhard Poul updated ARQ-2115: ------------------------------ Fix Version/s: was_1.0.0.next > Create Arquillian adapter for WebSphere 9 > ----------------------------------------- > > Key: ARQ-2115 > URL: https://issues.jboss.org/browse/ARQ-2115 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Reporter: Marián Macik > Assignee: Gerhard Poul > Fix For: was_1.0.0.next > > > Hi, guys, > I have created the Arquillian adapter for WebSphere 9. Here is the summary of the PR [1]: > \#### Short description of what this resolves: > Hi, guys, > my name is Marian Macik and I work at Red Hat as QE Engineer on [jBPM|https://github.com/kiegroup/jbpm] project. This PR introduces Arquillian container adapter for WebSphere 9. We have been using it at Red Hat in our QE automation for about two months without any issues. It is copied from adapter for WebSphere 8.5 (as WebSphere 8.5 was copied from WebSphere 8). There were only some minor changes when it comes to system paths pointing at WebSphere dependencies (jgss-provider and ws-admin-client). > However, since WebSphere 9, wsadmin is using jython27 by default. Jython21 is still supported and to use jython21, 'com.ibm.ws.admin.client.forJython21_9.0.jar' should be used. Moreover, the new wsadmin jar has additional libraries which are not used by Arquillian (such as Python JSR 223 implementation) and might cause issues when deploying and running tests. If this happens, simply override this property with jython21 jar: > {code} > -Dws_admin_client_jar_name=com.ibm.ws.admin.client.forJython21_9.0.jar > {code} > I added this property because the new jython27 wsadmin implementation was causing issues since it loaded unwanted classes on the classpath. Of course, by default the new jython27 wsadmin is used, override is optional. > I have also run the enclosed tests with my own arquillian.xml and they have passed. > Thanks, > Marian > [1] https://github.com/arquillian/arquillian-container-was/pull/29 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-506) Implement "hover" functionality in Graphene API

by Matous Jobanek (JIRA)

Matous Jobanek created ARQGRA-506: ------------------------------------- Summary: Implement "hover" functionality in Graphene API Key: ARQGRA-506 URL: https://issues.jboss.org/browse/ARQGRA-506 Project: Arquillian Graphene Issue Type: Enhancement Components: api Reporter: Matous Jobanek Currently, people face challenges in accessing dropdown submenus. A current implementation of the dropdown submenu hover functionality looks like this: {code:java} @Drone private WebDriver driver; @ArquillianResource private Actions action; driver.get("https://www.bootply.com/render/6FC76YQ4Nh"); Consumer<By> hover = (By by) -> { action.moveToElement(driver.findElement(by)) .perform(); }; hover.accept(By.linkText("Dropdown")); hover.accept(By.linkText("Dropdown Link 5")); hover.accept(By.linkText("Dropdown Submenu Link 5.4")); hover.accept(By.linkText("Dropdown Submenu Link 5.4.1")); {code} An example of the usage of the new Graphene API: {code:java} Graphene.hover(WebElement element) .hover(By by) .hover(WebElement element) .toGrapheneElement() .doubleClick(); {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-506) Implement "hover" functionality in Graphene API

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-506?page=com.atlassian.jira.plugin... ] Matous Jobanek updated ARQGRA-506: ---------------------------------- Fix Version/s: 2.2.2 > Implement "hover" functionality in Graphene API > ----------------------------------------------- > > Key: ARQGRA-506 > URL: https://issues.jboss.org/browse/ARQGRA-506 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: api > Reporter: Matous Jobanek > Fix For: 2.2.2 > > > Currently, people face challenges in accessing dropdown submenus. > A current implementation of the dropdown submenu hover functionality looks like this: > {code:java} > @Drone > private WebDriver driver; > > @ArquillianResource > private Actions action; > > driver.get("https://www.bootply.com/render/6FC76YQ4Nh"); > > Consumer<By> hover = (By by) -> { > action.moveToElement(driver.findElement(by)) > .perform(); > > }; > > hover.accept(By.linkText("Dropdown")); > hover.accept(By.linkText("Dropdown Link 5")); > hover.accept(By.linkText("Dropdown Submenu Link 5.4")); > hover.accept(By.linkText("Dropdown Submenu Link 5.4.1")); > {code} > An example of the usage of the new Graphene API: > {code:java} > Graphene.hover(WebElement element) > .hover(By by) > .hover(WebElement element) > .toGrapheneElement() > .doubleClick(); > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-505) Implement additional API methods for Action operations directly into Graphene class

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-505?page=com.atlassian.jira.plugin... ] Matous Jobanek updated ARQGRA-505: ---------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/165 > Implement additional API methods for Action operations directly into Graphene class > ----------------------------------------------------------------------------------- > > Key: ARQGRA-505 > URL: https://issues.jboss.org/browse/ARQGRA-505 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: api > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.2.2 > > > Methods: > - click() > - doubleClick() > - writeIntoElement() > It should be possible just write: > {code:java} > Graphene.writeIntoElement(element, "my text"); > Graphene.doubleClick(element); > Graphene.click(element); > {code} > Or invoke it directly on {{GrapheneElement}} class -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-505) Implement additional API methods for Action operations directly into Graphene class

by Matous Jobanek (JIRA)

Matous Jobanek created ARQGRA-505: ------------------------------------- Summary: Implement additional API methods for Action operations directly into Graphene class Key: ARQGRA-505 URL: https://issues.jboss.org/browse/ARQGRA-505 Project: Arquillian Graphene Issue Type: Enhancement Components: api Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: 2.2.2 Methods: - click() - doubleClick() - writeIntoElement() It should be possible just write: {code:java} Graphene.writeIntoElement(element, "my text"); Graphene.doubleClick(element); Graphene.click(element); {code} Or invoke it directly on {{GrapheneElement}} class -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues May 2017