Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Protractor being deprecated #232

Closed
Viktor-Bredihin opened this issue Nov 9, 2021 · 1 comment · Fixed by #276
Closed

Protractor being deprecated #232

Viktor-Bredihin opened this issue Nov 9, 2021 · 1 comment · Fixed by #276

Comments

@Viktor-Bredihin
Copy link

Any plans/advices regarding this news?

https://applitools.com/blog/migrating-protractor-tests-angular/

@jan-molak
Copy link
Collaborator

jan-molak commented Nov 25, 2021

Hi @Viktor-Bredihin - protractor-cucumber-framework is powered by Serenity/JS, so my suggestion for test suites using Protractor is to adopt Serenity/JS Screenplay Pattern before Protractor gets deprecated. The difference between adopting Screenplay and simply re-writing your tests to use Cypress/Playwright/WebriverIO etc is that (apart from benefits related to code reuse, greater readability, better handling of async code and more) it will allow you to abstract your tests away from the underlying integration library, such as Protractor.

To get a feel of what's involved please see my TodoMVC demo for comparison of Protractor test script, Page Object-based implementation, and Screenplay Pattern-based implementation.

Please also have a look at the Serenity/JS Protractor Cucumber boilerplate project.

If you have any questions about the approach, please feel free to join our Serenity/JS Community Chat on Gitter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants