droogans / protractorpageobjects Goto Github PK

Delete it, swap it out with the vanilla protractor test/protractor.conf.js

not to define column objects from Chpt 5 is giving a 404.

It's advertised, but not implemented

Include:

• lots of screenshots
• Chrome's cmd+option+i interface, and the console that's shown by pressing esc.
• common types of selectors (., #, =^[], =$[], etc.)
• other resources

Finally, switch all this.find.by.css to $, and this.find.all.by.css to $$.

Nobody reads books. :/

Feedback is that the master branch looks nice, but chapters are not being read.

Put highlights front and center, condense everything into how, not so much why.

Chapter 2 refers to http://beta.epikvote.com as a login page but it throws beta.epikvote.com’s server DNS address could not be found.

PS: Thanks for this amazing tutorial! Really good to understand the abstraction of Page Objects.

Hello,
first of all thank you very much Droogans for your great tutorial on page objects. You've done a GREAT work !

Question 1: Is is possible to have an JUnit/XUnit xml file generated at the end of each Suite?
Question 2: How to change the config protractor.conf.js to generate it?

Something like this:

I found some info here:
Mocha XUnit Reporter
https://github.com/visionmedia/mocha/blob/master/lib/reporters/xunit.js

npm install xunit-file
https://www.npmjs.org/package/xunit-file

Continuous Integration with Jenkins and Node.js and Mocha XUnit
https://blog.dylants.com/2013/06/21/jenkins-and-node/

best regards
damaniente

You are doing a great job! There is definitely a big gap on doing page objects well for Protractor.
Your guide is the best I have found!

Prefer instead to use the get property to denote a page attribute.

i.e., getRows() becomes rows. This bubbles up to table.rows, which are implemented as rows.all in the rows file.

I have no idea why I did this. Undo it.

Don't use the google code repo to grab selenium if brew can do it for you, and create a nice symlinked binary to launch it in a more condensed fashion.

Explain how tables are containers for rows and columns, and only expose the most useful bits found in the underlying table/rows.js and table/columns.js files.

Remove all python-ish _ prefixes to private page methods and functions.

Prefer instead to give them "obviously private" names.

Don't put page-level custom object methods as plain properties, these evaluate greedily and make things slow on invocation.

Everything should be a function.