pageobjects

Over the past year I built a very nice WebDriver framework for my group. Pretty standard fare: Page classes typically encapsulate the full functionality of a page in on our platform (controls as By objects, methods as needed) & extend a base class with some global methods, multiple pages are invoked within JUnit test classes, typical assertion methods, yada yada. Nothing extravagant-very by the books but very functional and flexible. Recently, however, I have been asked to use the framework to automate a large number of pages with forms that can hold 100 or even more inputs, selects, options,

So a coworker and I were discussing making a data object for our e2e tests. From my understanding about data objects they are used for decoupling your test suites. For example, my first test suite is to create an account and to test if the fields are valid and the second test suite logins into the account and does its own tests. I am told it is good to use data objects (not a page object) just incase the first test suite fails when making an account. That way we can use the data object in the second test suite to create a new user just for testing login. My problem is that if my first test

Hello all NightWatch adopters, I am trying to parse a table with the following format to get a a list of rows and the cell in each rows <tbody> <tr> // 1 row <td>Item A</td> // name <td>John</td> // owner <td>Monday</td> // create date </tr> <tr> // 2 row <td>Item B</td> <td>Mary</td> <td>Tuesday</td> </tr> </tbody> The code now looks like this which calls the function below. browser.elements('css selector', 'tbody tr', getResultsList); Where my function for parsing now looks like this. function getResultsList(rowResults){ // Here we get the correct set of rows console.log(rowResults.length +

I have built various Test Automation frameworks using the Page Object Pattern with Java ( https://code.google.com/p/selenium/wiki/PageObjects ). Two of the big benefits I have found are: 1) You can see what methods are available when you have an instance of a page (e.g. typing homepage. will show me all the actions/methods you can call from the homepage) 2) Because navigation methods (e.g. goToHomepage()) return an instance of the subsequent page (e.g. homepage), you can navigate through your tests simply by writing the code and seeing where it takes you. e.g. WelcomePage welcomePage =

I'm writing some protractor tests for our application. There is one place where is non-angular page as iframe in angular page. Problem: I'm unable to map fields from non-angular page in Page Object object and use them in right time in my test specs. Notes: I tried write Page Object as object (var DamagePage: {}) and as function (var DamagePage = function() {}) too. Both works bad in this situation. Calling fields from non-angular page in spec works obviously fine, but I want to have it in Page Object for correct project organization. I have set browser.driver.ignoreSynchronization = true; Here

How to implement the pageObject pattern(Selenium) for frames in a page..I have a home page and there is a left frame and Right frame and i would like to create page object for each frame.. For example, I have the LeftFrame Page Object as below: Public Class HomePageLeftFrame{ private WebElement link; private WebElement textField; } How to write the @FindBy annotation for the two elements in the HomePageLeftFrame object...Is there a way? Note: As per the documentation on the selenium for pageObjects it is mentioned that page objects can be a whole HTML page or part of a page..Is my

My question is: do webelements decorated with findby attributes call the findelement function upon each reference to them? If not, when? And what is the procedure with List< webelement > which is also decorated? Does it trigger when you reference the list, or when you reference an element inside that list? I'm asking because I have some situations where I'm getting stale element exceptions and I want to know how to deal with them. WebElements are evaluated lazily. That is, if you never use a WebElement field in a PageObject, there will never be a call to "findElement" for it. Reference . If