An Introduction to AngularJS End to End Testing with Protractor
Why Stack Overflow recommends it
Stack Overflow users link it when answering Protractor setup, Selenium configuration and element locator questions, since it was one of the few walkthroughs available when Protractor was new.
Recommended by 3 people across 3 different months, 2013 to 2014.
What it is
A recording of the August 2013 DFW Area AngularJS Meetup in which Jim Lavin gives an overview of using the Protractor framework for end-to-end testing of AngularJS applications. It covers setting up Protractor with Selenium and writing tests, and comes with linked slides.
What people said
Recommends Foo · 2013-10 · Stack Overflow · on “Getting an errors while executing protractor e2e tests”
Did you try updating selenium port number in the configuration file? It was recommend in this video - [this video] This works for me (assuming that you are taking the relative path into account and executing tests from there) - // A reference configuration file. exports.config = { seleniumServerJar: './selenium/selenium-server-standalone-2.35.0.jar', seleniumPort: 4444, chromeDriver: './selenium/chromedriver', capabilities: { 'browserName': 'chrome' }, specs: ['./spec/*_spec.js'], jasmineNodeOpts: { onComplete: null, isVerbose: true, showColors: true, includeStackTrace: false, defaultTimeoutInterval: 30000 } };
Recommends Sirk · 2014-03 · Stack Overflow · on “How to locate the element '54' with protractor and not with xpath”
you could assign a unique ID in the html, though I think some people frown on that. heres a few links that might help you // [this video] - a video someone made going through his protractor e2e test for his angular site [LINK] - very good site with some good little tips n tricks with a video [LINK] - slides from the first video the slides are probably your best bet as slide 11 onwards talks about protractor locators and css is one of them here's what i would do for your little extract though its probably not going to be useful as the app gets bigger var labelText = ptor.findElement(protractor.By.tagName('label').getText(); console.log(labelText); that should print 54 to the console hope this help
Recommends code · 2014-05 · Stack Overflow · on “Is there a way for me to do headless testing with Protractor when I am using a Windows platform?”
selenium server is java based and should run fine on a Windows machine. [LINK] This youtube video explains how to setup protractor and selenium to work together. [this video]
Cites tennisgent · 2013-10 · Stack Overflow · on “Getting an errors while executing protractor e2e tests”
+1 here. I've got the same problem. I followed the examples found on protractor's github page, as well as the in the video found here: link [this video] , but I haven't had any luck getting it to actually run my tests. The selenium server starts fine, and navigates to my site's main page but then dies when it tries to access angular saying `UnknownError: javascript error: angular is not defined`. If anyone has any ideas, that would be much appreciated.
Cites Tim Hong · 2014-08 · Stack Overflow · on “Should I use browser or ptor = protractor.getInstance()?”
I watched this video ( [this video] ) which was uploaded Aug 2013. It claims that we should use ptor.get(url) rather than browser().navigateTo(url) in future. But when I look at docs on the protractor home page (on git hub) and their newest examples are still using browser. I am wondering if any one knows the movement to use var ptor = protractor.getInstance() still happening? Thank you very much in advance!