Open ganeshkodali opened 3 years ago
My suggestion to not rely on Protractor or any angular solutions. If you still using Protractor and want to use it in future - just make your own fork and update/maintain it from time to time with latest upstream dependencies. This approach will work.
My suggestion to not rely on Protractor or any angular solutions. If you still using Protractor and want to use it in future - just make your own fork and update/maintain it from time to time with latest upstream dependencies. This approach will work.
Thank you Stan for your suggestions.
Are there any prominent forks out there yet that have committed teams behind them? My company is considering continuing with Protractor, but would prefer not to manage the fork ourselves.
Perhaps @mgechev or @aaronfrost could say smth regarding this.
I'll delegate to @aaronfrost who has expressed interest to maintain a fork in XLTS.dev.
At the very least, security patches would be welcome. Dependabot is starting to complain...
A supported fork of Protractor will be available for free by the team at HeroDevs starting August 2023: https://www.herodevs.com/support/nes-protractor
HeroDevs is a third party provider working to support Protractor post EOL: https://blog.angular.io/the-state-of-end-to-end-testing-with-angular-d175f751cb9c
Hi team,
We are using Protractor since 2018 and continuing the same. We would like to know the support after 2022 and any plans for licensed version or any alternate business model to continue with Protractor. Appreciate for quicker response.
Thanks, Ganesh