-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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] First-class test runner support #3552
Comments
Hey @celeryclub! We are dogfooding the test runner integration on Playwright (this repo), and working on moving it to the playwright-runner repo for early adopters. Are you facing any issues/gaps with jest-playwright? |
I see. That makes sense. jest-playwright is working pretty well for me - my main issue is around debugging tests. |
@celeryclub we will move the local test runner into the playwright-runner repo shortly. Could you share more details on you debug requirements/expectations? |
@arjun27 set up a sync for the two of us next week, so I think I'll have more to share after that. |
Would be also interested in that discussion, having an easy bullet proof test runner is something which is definitely missing. |
We are addressing this with playwright-test. |
Hey team. I hope all is well. Thanks for all the great fixes recently. Things are feeling really solid.
I'm curious what the priority is for test runner support. I currently use jest-playwright, which is a great short-term solution to this issue. I'm aware of playwright-runner too, but it seems to be more of an experimental project rather than an official test runner integration.
Mind shedding some light on the status of this effort? Thanks!
The text was updated successfully, but these errors were encountered: