cnishina on selenium4
chore(release): bumpb version t… (compare)
Hey folks, I've just created a new demo project showing how to use protractor-cucumber-framework
to produce Serenity reports:
Thoughts and feedback welcome!
wait for angular waits for angular to exit the zone. If your app does not exit the zone, the page will keep waiting and your script will timeout.
it is perfectly fine to not wait for angular. Just know that you should put browser.waits to wait for an element to appear on the page on load instead.
protractor-cucumber-framework
v8.0.3 with the latest Serenity/JS and support for Cucumber v1-v7. Please run npm update
and let me know if you spot any issues.
protractor-cucumber-framework
v8.0.4
is now available on npmjs.com and ships with the latest Serenity/JS version 2.27.0. Please run npm update
if you're using the plugin (or Serenity/JS itself ;-) )
Where did Craig go? we are glad to see him with interesting news
Craig is not at the phone right now. Please leave a message after the beep. What's up?
Yeah! btw, often got messages from unknown numbers and when hear it - just advertising from banking or credit organisations)
wait for angular waits for angular to exit the zone. If your app does not exit the zone, the page will keep waiting and your script will timeout.
it is perfectly fine to not wait for angular. Just know that you should put browser.waits to wait for an element to appear on the page on load instead.
I was just starting to use Protractor and our app requires authentication so I had to turn off wait for angular so that I could handle the redirect to tour login page (Azure ADB2C) and they login and come back to the app. First is it ok/recommended to turn wait for Angular back on or am I now relegated to doing waits with ExpectedConditions?