Skip to content
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.

Commit

Permalink
docs(website): updated reference from ignoreSynchronization to waitFo…
Browse files Browse the repository at this point in the history
…rAngularEnabled(false). (#4632)

Updated wording to relfect the content it's linked to.
- FAQ how to handle log-in page used old ignoreSynchronization but linked to waitForAngularEnabled(false).
  • Loading branch information
MichaelRijsdijk authored and qiyigg committed Dec 14, 2017
1 parent b43081f commit 65f206e
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ How do I deal with my log-in page?
If your app needs log-in, there are a couple ways to deal with it. If your login
page is not written with Angular, you'll need to interact with it via
unwrapped webdriver, which can be accessed like `browser.driver.get()`. You can also use
`browser.ignoreSynchronization` as explained [here](/docs/timeouts.md#how-to-disable-waiting-for-angular).
`browser.waitForAngularEnabled(false)` as explained [here](/docs/timeouts.md#how-to-disable-waiting-for-angular).

Another option is to put your log-in code into an `onPrepare` function, which will be run
once before any of your tests. See this example ([withLoginConf.js](https://github.com/angular/protractor/blob/master/spec/withLoginConf.js))
Expand Down

0 comments on commit 65f206e

Please sign in to comment.