There is a closed RFC with the future of Angular E2E & Plans for Protractor on GitHub with more details about this. Only PRs that address security issues and fixes for browser releases that break Protractor tests will be merged. ![]() ![]() Angular CLI will not include Protractor for new projects.The current deprecation timeline looks like this: There are different testing solutions today, and they offer better stability and improved support for features like cross-browser testing. Protractor is dependent on selenium-webdriver, and is not able to upgrade to the new version without introducing a huge breaking change, and forcing users to do a migration for all their tests. Some of the reasons behind these deprecation plans are: The Angular team has announced the deprecation of Protractor in May 2021. In this post, I'll give you some reasons to migrate to Cypress since it's one of the best alternatives for E2E testing. Is this the right time to think of other alternatives? In fact, Protractor was created in 2013 when AngularJS was the most popular web framework, and it allowed developers to run tests through a web application in a real browser, along with interaction commands to mimic the user behavior.Īs expected, the ecosystem around JavaScript technologies has been changing continuously, with new tools emerging that afford developers more modern options for writing tests. ![]() I remember those days when I was working actively using the AngularJS framework to build Single-Page Applications, and Protractor was the most viable option for writing E2E(End-to-End) tests. Great memories come to my mind when I read about Protractor.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |