Issue 1:
System info

Playwright Version: [v1.31.1]

Operating System: [Windows 10]

Browser: [Chromium]

Other info:

Command npx playwright install chrome

Log from Terminal:

Downloading Google Chrome
Installing Google Chrome
ERROR: failed to install Google Chrome
Failed to install browsers
Error: Failed to install chrome

Chrome is installed on my machine.

Unable to run tests on Chrome Browser.

Issue 2:
Table of Contents

(Feature Request) The case for installing Playwright globally on a machine

problem statement

use cases

1. Using Playwright like a standard installed application.

2. Situations like classrooms and labs where a single installation of Playwright is simpler to maintain.

3. Docker images that do not bake in the tests

close to technically feasible

(Feature Request) The case for installing Playwright globally on a machine

problem statement

Based on my understanding, there are 3 layers to utilizing Playwright

L1. playwright proper or what is known as @playwright/test

L2. browser dependencies

L3. tests

The current installation process of Playwright exposes all 3 layers because L2 is a specific step that needs

to be performed for each Playwright folder. This is ideal for developers because it allows them to deal with

problems of each layer appropriately by installing L1 and L2 in each development folder.

However, there is also a case to be made for combining L1 and L2, as a single step and presenting Playwright

as a global testing tool.

use cases

1. Using Playwright like a standard installed application.

An analogous example : we install Word and then invoke it on any file anywhere on our PC. There is no special dependencies

that the user need to do.

The Playwright and browser support is part of one environment that the use of PATH is sufficient

This results in only one copy of Playwright and browser support layer needed instead of being duplicated in each Playwright folder.

This also allows many test sources to be run against a single Playwright install.

2. Situations like classrooms and labs where a single installation of Playwright is simpler to maintain.

This is where one person/teacher deals with the install of Playwright and the browser dependencies and all users/students point

to that installation and just write tests.

3. Docker images that do not bake in the tests

So instead of creating custom docker images from Docker Focal, each with its own copy of tests,

the Docker image can reference arbitary test volumes and therefore only one image ( but as many containers as needed ) is needed.

The advent of WSL2 allows the running of Linux apps that interopreate with Windows in a seamless manner. Accessing Playwright via Docker is an extension of this type of seamless use.

See #14179

close to technically feasible

There are also several technical reasons that suggests that installing Playwright globally close to being feasible.

npm supports installing packages globally

However, installing Playwright globally is not currently supported.

Playwright already has functionality that seems to be allowing running tests in other directories

that is, –config {dir} or testDir in configuration files

The current problem appears to be if the {dir} is outside the Playwright folder, the tests cannot run properly.

See #14039