Should retry if angular isn't found on the page #2

juliemr · 2013-05-30T00:29:16Z

If protractor.get() gets to the page before AngularJS is loaded, it just dies with an ugly error message. It should retry once or twice, and then fail with a nice message.

…sn't give a sane error message. Fixes issue #2.

You can now give specific capabilities custom names so the output logs will be more understandable. For instance, you might name one capability "Chrome - French" and another "Chrome - English" so that the logs will read: [Chrome - French] ... [Chrome - French] ... [Chrome - French] ... [Chrome - English] ... [Chrome - English] ... [Chrome - English] ... Instead of just [chrome #1] ... [chrome #1] ... [chrome #1] ... [chrome #2] ... [chrome #2] ... [chrome #2] ... Closes #2112

juliemr added a commit that referenced this issue May 30, 2013

Wait up to 3 seconds for angular to be found on the page, and if it i…

5d7622e

…sn't give a sane error message. Fixes issue #2.

juliemr closed this as completed May 30, 2013

jpetraws mentioned this issue Jul 22, 2014

Using Protractor to run tests against multiple user roles #1088

Closed

desaip01 mentioned this issue Aug 28, 2014

Error while launching multiple browsers #1256

Closed

juliemr mentioned this issue Sep 5, 2014

New_York time-zone not supported in default capabilities for Selenium/Saucelabs? #1287

Closed

lam2558 mentioned this issue Oct 16, 2014

Feature Suggestion: Support multiple browser instances from single test #381

Closed

ghost mentioned this issue Dec 14, 2014

Tests on chrome doesn't work when an instance is already open #1636

Closed

bhawani2008 mentioned this issue Mar 12, 2015

Protractor iOS Automation: A Jasmine spec timed out. Resetting the WebDriver Control Flow. #1921

Closed

ghu21st mentioned this issue May 11, 2015

Customizing the name when running parallel tests #2112

Closed

WebhookGit mentioned this issue Jul 7, 2015

Firefox crashes on test startup, then restarts and runs test just fine. #2297

Closed

pmowrer mentioned this issue Sep 21, 2015

Expose taskId (or some way of uniquely identifying test runners) #2392

Open

Karpo72 mentioned this issue Oct 14, 2015

Error while waiting for Protractor to sync with the page #2609

Closed

vcernomschi mentioned this issue Nov 27, 2015

Unable to run tests using protractor on SauceLabs #2748

Closed

amcinerney mentioned this issue Feb 18, 2016

[issue] .isDisplayed() returning error "Failed: No element found using locator:" in Firefox, works fine in Chrome #2960

Closed

fancyhejianyang mentioned this issue Sep 7, 2016

A suddenly error! #3521

Closed

Satish152 mentioned this issue Nov 16, 2019

I'm getting two different error messages when i'm using page objects with different browser instances in a single test in Protractor #5353

Open

snyk-bot mentioned this issue May 24, 2022

[Snyk] Fix for 6 vulnerabilities lathonez/protractor#1

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Should retry if angular isn't found on the page #2

Should retry if angular isn't found on the page #2

juliemr commented May 30, 2013

Should retry if angular isn't found on the page #2

Should retry if angular isn't found on the page #2

Comments

juliemr commented May 30, 2013