New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Protractor 5.1 - Wrong IgnoreSynchronization Behavior? #4187
Comments
faced similar issue with Protractor 5.1.1 which was not reproducible on 4.0.14 |
It is better now to use http://www.protractortest.org/#/api?view=ProtractorBrowser.prototype.waitForAngularEnabled Also try to put this into describe('my suite', ()=>{
beforeEach(()=> {
browser.waitForAngularEnabled(false)
})
it('my test', ()=> {
...
})
}) I can suggest to put this into //Your protractor configuration file
let conf = {
// Some other options ...
onPrepare: () => {
browser.waitForAngularEnabled(false)
}
} |
Ok, both (waitforAngularEnabled() and ignoreSynchronization) work inside of the beforeEach content. |
Setting waitForAngularEnabled now involves working with the control flow. I'm not exactly sure what's going on here, but it's probably some weird interaction with using the controlflow at the wrong time. Everything in the describe() block (but outside of a beforeEach(), it(), etc) is going to be run when the tests are set up, not when they're actually executed. All that stuff is run when Jasmine is setting up your tests, not when they're executing. In general, put anything that interacts with the browser inside an |
Hi!
we have some problems with the behavior of IgnoreSynchronization since Protractor 5 and I was not able to find something regarding this in the changelog.
Here is a lightly adapted default protractor test case:
The default console output outsite of it code block prints, that the internalIgnoreSynchronization value is set to true. After the entrance inside of the TC, the internalIgnoreSynchronization value changes to false.
Is it the correct behavior? Is it possible to find a workaround for it, otherwise we have to adapt a lot of testcases to set the ignoreSynchronization inside of each tc.
Thanks!
Regards,
Waldemar
The text was updated successfully, but these errors were encountered: