👨🏫 Co-Founder of This is Learning, Organizer of AarhusJS
✍️ Writer, Speaker, FOSS Maintainer 📗 Author
🏆 Microsoft MVP 🌟 GitHub Star
🌊 Nx Champion 🦸 Angular Hero of Education
The end-to-end test suite generated when creating an Angular application project with Angular CLI is using Protractor.
Protractor has the benefit of hooking into NgZone. Cypress sometimes has issues with waiting for an element to appear. You end up having to put random timeouts into your tests to wait for Angular to stabilize. Sometimes it works, but it's a flaky test waiting to fail.
Protractor is able to support legacy browsers like Internet Explorer and Edge Legacy.
The end-to-end test suite generated when creating an Angular application project with Angular CLI is using Protractor.
Protractor has the benefit of hooking into NgZone. Cypress sometimes has issues with waiting for an element to appear. You end up having to put random timeouts into your tests to wait for Angular to stabilize. Sometimes it works, but it's a flaky test waiting to fail.
Protractor is able to support legacy browsers like Internet Explorer and Edge Legacy.
Thanks for the reminder Lars, yes Angular sees Protractor as E2E and not unit test.