-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Description
Page(s)
https://playwright.dev/docs/docker#remote-connection - this is the only place in the entire docs that ever mentions the "run-server" capability so it could be here or rather the server should have its own page.
Description
There is zero information on what one should expect from the PW server. I'm trying to create an infrastructure where PW servers could be reused between multiple users/CI workers but besides experimenting, there is no way to know how it will behave.
Does it have any startup options?
What are and aren't intended use cases of it?
What happens if more then one client tries to connect to a single server and execute tests on it? Especially with concurrency in mind, the server can only spawn a limited number of workers before it runs out of resources, but is there a way to control that?
Does the server just blindly accept instructions from clients or there is some queuing mechanism?
What browsers are preinstalled in the docker image and how to run "branded" versions of the browsers with PW server?
These are only my most pressing questions now and I could probably have way more. My point is that it should have more explanations about it in general ^^' It's very useful for taking consistent screenshots between multiple platforms and sounds like it could be useful in CI/CD scenarios if it was better documented.