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

[Question] Succint list of pro and cons versus Cypress #2560

Closed
LifeIsStrange opened this issue Jun 12, 2020 · 2 comments
Closed

[Question] Succint list of pro and cons versus Cypress #2560

LifeIsStrange opened this issue Jun 12, 2020 · 2 comments
Assignees

Comments

@LifeIsStrange
Copy link

It seems that playwright is an alternative to Cypress right?

If so you should communicate how do they compare in order to reach users.
A strength that I see is that you supports Firefox for example. In what other ways would playwright be better? And in what other ways does it has to catch up?

@arjunattam arjunattam self-assigned this Jun 12, 2020
@pavelfeldman
Copy link
Member

I would not want the comparison to originate from the Playwright team, I'd rather trust third party to perform this analysis! We would do our best at describing our features, but we won't be issuing a checkbox matrix where we have more checks than the others!

@LifeIsStrange
Copy link
Author

LifeIsStrange commented Jun 28, 2020

@pavelfeldman

but we won't be issuing a checkbox matrix where we have more checks than the others!
I understand the basic Idea of not wanting to be perceived as a competitor or to not want to be perceived as doing oppressive or unfair marketing against cypress or competitor X.
But If you do the comparison matrix based on objective presence or absence of features (without the need of quantifying how useful the feature is) and that you accept pull requests from anybody (and from cypress) that would objectively correct a presence or an absence then I don't see any inconvenient to create such a feature matrix. But I do see an inconvenient of not having such a matrix.
If you wait for third parties, you better link them in your Readme, otherwise they would be not get visibility.
Also, I doubt third parties would actually benevolently create for you a feature matrix, they wouldn't even have the expertise that only you have. They would better write a lower quality medium blog post that would be far less objective than the ability to quickly see absence and presence of said features.

Anyway do whatever you want but you might want to reconsider.
Currently as a user I don't know why I would use your lib and if nothing happen, in a month or two I will mostly forget about its existence despite it being able to potentially improve my integration testing experience.

"We would do our best at describing our feature" I'm interested in such a list, even without a comparison it would still be better than nothing

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

No branches or pull requests

3 participants