The protractor.waitForAngular() also suggests that you wait for area changes using protractor.waitForAngular() , which, I think, may or may not be implemented using Selenium. You still have to beat around your head to simulate the same function using selenium.
My opinion
If you just want to do user interface testing and are not interested in listening for scope changes or any specific angular events, you can continue selenium. But this is a HUGE advantage of using Protractor for e2e tests for Angular.
source share