Agree.
About reason #2, in our company we already updated our tests (thousands) to use async/await two years ago, just to be prepared when the upgrade comes.
We had the whole team working on that and it took us like 3 days to get the whole framework updated. Not a big deal, to be honest.
The protractor upgrade didn't arrive yet, true, but our code is much more readable and maintainable now 😍
Maintaining your tests must be part of your work IMO.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Agree.
About reason #2, in our company we already updated our tests (thousands) to use async/await two years ago, just to be prepared when the upgrade comes.
We had the whole team working on that and it took us like 3 days to get the whole framework updated. Not a big deal, to be honest.
The protractor upgrade didn't arrive yet, true, but our code is much more readable and maintainable now 😍
Maintaining your tests must be part of your work IMO.