graphene2

Initialize Page Objects - Arquillian - Selenium

由 被刻印的时光 ゝ 提交于 2019-12-08 04:30:01
问题 I am new to Selenium and Arquillian framework. I am trying to implement Page Object Model. Webdriver browser capabilities are saved in arquillian xml file. I am using TestNG and created the following classes: public class Test{ @Drone Webdriver driver; @Page Login login; @Page Home home; public void createOrderTest(){ login.navigateURL(); login.setcredentials(); home.createOrder(); } } public class Login{ // Webelements needed in methods below are declared here public void navigateURL(){

Initialize Page Objects - Arquillian - Selenium

由 柔情痞子 提交于 2019-12-06 19:47:42
I am new to Selenium and Arquillian framework. I am trying to implement Page Object Model. Webdriver browser capabilities are saved in arquillian xml file. I am using TestNG and created the following classes: public class Test{ @Drone Webdriver driver; @Page Login login; @Page Home home; public void createOrderTest(){ login.navigateURL(); login.setcredentials(); home.createOrder(); } } public class Login{ // Webelements needed in methods below are declared here public void navigateURL(){ driver.get("//url/login.aspx"); } public void setCredentials(){ // code to enter username, password and

Why can I click an input with type=radio of a h:selectOneRadio, but not one of a p:selectOneRadio with Graphene/Selenium?

由 别等时光非礼了梦想. 提交于 2019-12-06 06:02:28
问题 A h:selectOneRadio results in <input type="radio"> in a table and p:selectOneRadio in <input type="radio"> in a table with some div s around the input . The id for both is [form id]:[selectOneRadio id]:[option number] which I can use successfully for the plain JSF in a Graphene functional test when accessing it with @FindBy(id="[...]") whereas the PrimeFaces variant fails due to org.openqa.selenium.ElementNotInteractableException . Investigating the generated HTML I don't see the difference

Why can I click an input with type=radio of a h:selectOneRadio, but not one of a p:selectOneRadio with Graphene/Selenium?

由 元气小坏坏 提交于 2019-12-04 09:04:02
A h:selectOneRadio results in <input type="radio"> in a table and p:selectOneRadio in <input type="radio"> in a table with some div s around the input . The id for both is [form id]:[selectOneRadio id]:[option number] which I can use successfully for the plain JSF in a Graphene functional test when accessing it with @FindBy(id="[...]") whereas the PrimeFaces variant fails due to org.openqa.selenium.ElementNotInteractableException . Investigating the generated HTML I don't see the difference <html xmlns="http://www.w3.org/1999/xhtml"> <head> <link type="text/css" rel="stylesheet" href="

How to access PrimeFaces components through Graphene in the most portable way?

由 ▼魔方 西西 提交于 2019-12-04 05:48:59
问题 I'm writing Arquillian+Graphene functional tests for a Java EE web client with Primefaces 6.1 components and would like to write them in the most portable way from the beginning. I noticed that there's no possibility to perform operations like WebElement.click on any PrimeFaces component which is clickable (e.g. not on p:selectBooleanCheckbox since the WebElement is a div containing another div containing an input ), so that I have to figure out how a clickable component is structured for

How to access PrimeFaces components through Graphene in the most portable way?

由 女生的网名这么多〃 提交于 2019-12-02 11:53:53
I'm writing Arquillian+Graphene functional tests for a Java EE web client with Primefaces 6.1 components and would like to write them in the most portable way from the beginning. I noticed that there's no possibility to perform operations like WebElement.click on any PrimeFaces component which is clickable (e.g. not on p:selectBooleanCheckbox since the WebElement is a div containing another div containing an input ), so that I have to figure out how a clickable component is structured for every component and access it via XPath figure the above out for every component after I change the
订阅 graphene2