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

E2E Automated Test Tooling Assessment #2

Closed
tooniez opened this issue Jul 15, 2023 · 2 comments · Fixed by #6
Closed

E2E Automated Test Tooling Assessment #2

tooniez opened this issue Jul 15, 2023 · 2 comments · Fixed by #6
Assignees
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@tooniez
Copy link
Owner

tooniez commented Jul 15, 2023

📝 Proposed Documentation

Test Automation Framework: Choose a test automation framework suitable for this application. Explain why you have chosen it over others.

💡 Possible Solution

Add differences of Cypress and Playwright

📑 Additional Context

🔗 Related Issues/PRs

@tooniez tooniez modified the milestone: Planning Jul 15, 2023
@tooniez tooniez self-assigned this Jul 15, 2023
@tooniez tooniez added the documentation Improvements or additions to documentation label Jul 15, 2023
@tooniez tooniez added this to the Planning milestone Jul 15, 2023
@tooniez
Copy link
Owner Author

tooniez commented Jul 15, 2023

Have gone through similar task, was in the process of writing a post on key differences of Cypress and Playwright (I consider these 2 E2E test frameworks to be most popular).

The choice is to go with Playwright. The reasons of selection were below:

  • Multi-threaded architecture
  • Various Test Types
  • Flexibility
  • Various Languages
  • Mobile Devices

I'll go through my notes and see

@tooniez tooniez linked a pull request Jul 15, 2023 that will close this issue
2 tasks
@tooniez tooniez changed the title E2E Automation Tooling Assessment E2E Automated Test Tooling Assessment Jul 15, 2023
@tooniez
Copy link
Owner Author

tooniez commented Jul 15, 2023

Below is a table to show some comparisons of Cypress vs Playwright.

Aspect Cypress Playwright
Language Support JavaScript JavaScript, TypeScript, Python, and more
Browser Support Chromium-based only (headless or full browser) Chromium, Firefox, WebKit (headless or headed)
Test Types End-to-end (E2E) tests End-to-end (E2E), integration, and unit tests
Architecture Single-threaded Multi-threaded
Execution Speed Fast Fast
Cross-Browser Limited support Robust cross-browser support
Mobile Testing Not natively supported Native support for mobile testing
Test Runner Built-in Cypress Test Runner Can integrate with custom test runners
Test Debugging Built-in interactive mode for debugging Built-in interactive mode for debugging
Community Support Large and active community Growing community support
Learning Curve Relatively easy to get started Requires some learning curve
Assertions Powerful built-in assertions Flexibility to use any assertion library
Ecosystem Limited ecosystem compared to Playwright Growing ecosystem with various integrations
Documentation Well-documented with comprehensive guides Well-documented with comprehensive guides
Vendor Lock-In Potential vendor lock-in No vendor lock-in, can switch frameworks
Commercial Support Cypress offers paid options for support Playwright offers paid options for support

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Development

Successfully merging a pull request may close this issue.

1 participant