-
-
Notifications
You must be signed in to change notification settings - Fork 137
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
Is there a way to not close the browser window when the test is done? #334
Comments
Hi @daniel-abramov, not sure if this is available in the go bindings, because I couldn't geht playwright to run. But with node.js, I use the page pause API for this purpose. It seems to exist in the go API as well: playwright-go/generated-interfaces.go Line 1647 in 989def6
|
Thanks, @marc136. Yeah, I've tried I went for a workaround by rewriting it in Rust using |
I'm using
playwright-go
in the following way. I create 10 contexts. Each context creates its page, performs a log-in operation in the app, and then joins chat rooms with fake audio and video devices that I've configured with Chromium flags. The app continues to run until I send aSIGTERM
to it.After some tests, I've noticed that the test clients that are being created in such a way do disappear shortly after being started (despite the test application with playwright running).
That was a bummer as I expected the Chromium instances to remain open until the app ended or the playwright, context, or page are closed.
I removed the headless flag to see what happens and noticed that the Chromium windows just get closed by the playwright for some unknown reason.
I tried to work with the persistent context to workaround it, but it did not change anything, unfortunately.
The text was updated successfully, but these errors were encountered: