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

Spike - Investigate using playwright for integration testing. #11322

Closed
tlabaj opened this issue Dec 5, 2024 · 1 comment
Closed

Spike - Investigate using playwright for integration testing. #11322

tlabaj opened this issue Dec 5, 2024 · 1 comment
Assignees

Comments

@tlabaj
Copy link
Contributor

tlabaj commented Dec 5, 2024

This is is to track work done for investigating replacing cypress with playwright.

@tlabaj tlabaj self-assigned this Dec 5, 2024
@tlabaj tlabaj added this to the 2025.Q4 milestone Dec 5, 2024
@github-project-automation github-project-automation bot moved this to Needs triage in PatternFly Issues Dec 5, 2024
@tlabaj tlabaj moved this from Needs triage to Not started in PatternFly Issues Dec 5, 2024
@tlabaj tlabaj added the Spike label Dec 5, 2024
@tlabaj tlabaj removed this from the 2025.Q4 milestone Dec 5, 2024
@kmcfaul kmcfaul moved this from Not started to In Progress in PatternFly Issues Dec 9, 2024
@tlabaj
Copy link
Contributor Author

tlabaj commented Jan 6, 2025

I didd not get as far as planned on this. But from initial assessment It is worth switching over. Sme take aways so far:

  • Core is planning to use playwright for visual regression test and it would be nice to align our tools
  • I tried out some tools online to convert cypress test. I still had to go in and make some update to gety the test to run.
  • Playwright is less flaky than Cypress

@tlabaj tlabaj closed this as completed Jan 6, 2025
@github-project-automation github-project-automation bot moved this from In Progress to Done in PatternFly Issues Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

1 participant