Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upConsider removing protractor as the default E2E tool #18844
Assignees
Milestone
Comments
I've seen that, however that doesn't really mean anything by itself. It's too vague. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Command (mark with an
x)Description
The default E2E tool that is provided is protractor, which appears to be effectively unmaintained and doesn't seem to have any kind of road map or any communications from the maintainers that would make me think that's going to change any time soon.
I think that there is a high chance that new users will either just use the provided tool by default and not think twice about it, or they would give extra weight to the provided solution when weighing up options (I know I have done that in the past) and then go on to possibly regret that choice (or resent the default they didn't realise they could change).
I think we should stop steering people in that direction.
Describe the solution you'd like
I think it would be preferable to either ship with a tool that is actively maintained or to ship without a default tool at all and just provide documentation on how to configure the tool of their choice (just the Angular specific docs, they can get tool specific docs from the tool they choose).
Describe alternatives you've considered
If I'm wrong about the maintenance status of protractor, then a possible alternative is that it becomes an actively maintained,
user friendly solution that's worthy of the default tool status.