You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ci.md
+17-9Lines changed: 17 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,26 +1,34 @@
1
-
# Continuous integration
1
+
# Continuous Integration
2
2
3
3
Playwright tests can be executed to run on your CI environments. To simplify this, we have created sample configurations for common CI providers that can be used to bootstrap your setup.
4
4
5
-
#### Contents
6
-
-[Docker](#docker)
5
+
<!-- GEN:toc -->
7
6
-[GitHub Actions](#github-actions)
7
+
-[Docker](#docker)
8
8
-[Azure Pipelines](#azure-pipelines)
9
9
-[Travis CI](#travis-ci)
10
10
-[CircleCI](#circleci)
11
11
-[AppVeyor](#appveyor)
12
+
<!-- GEN:stop -->
12
13
13
14
Broadly, configuration on CI involves **ensuring system dependencies** are in place, **installing Playwright and browsers** (typically with `npm install`), and **running tests** (typically with `npm test`). Windows and macOS build agents do not require any additional system dependencies. Linux build agents can require additional dependencies, depending on the Linux distribution.
14
15
15
-
<br/>
16
+
## GitHub Actions
16
17
17
-
## Docker
18
+
The [Playwright GitHub Action](https://github.com/microsoft/playwright-github-action) can be used to run Playwright tests on GitHub Actions.
18
19
19
-
We have a [pre-built Docker image](docker/README.md) which can either be used directly, or as a reference to update your existing Docker definitions.
20
+
```yml
21
+
steps:
22
+
- uses: microsoft/playwright-github-action@v1
23
+
- name: Run your tests
24
+
run: npm test
25
+
```
20
26
21
-
## GitHub Actions
27
+
We run [our tests](/.github/workflows/tests.yml) on GitHub Actions, across a matrix of 3 platforms (Windows, Linux, macOS) and 3 browsers (Chromium, Firefox, WebKit).
28
+
29
+
## Docker
22
30
23
-
We run [our tests](/.github/workflows/tests.yml) on GitHub Actions, across a matrix of 3 platforms (Windows, Linux, macOS) and 3 browsers (Chromium, Firefox, WebKit). Use the [microsoft/playwright-github-action](https://github.com/microsoft/playwright-github-action)to bootstrap your GitHub Actions configuration.
31
+
We have a [pre-built Docker image](docker/README.md) which can either be used directly, or as a reference to update your existing Docker definitions.
24
32
25
33
## Azure Pipelines
26
34
@@ -38,4 +46,4 @@ We run our tests on CircleCI, with our [pre-built Docker image](docker/README.md
38
46
39
47
## AppVeyor
40
48
41
-
We run our tests on Windows agents in AppVeyor. Use our [AppVeyor configuration](/.appveyor.yml) to create your own.
49
+
We run our tests on Windows agents in AppVeyor. Use our [AppVeyor configuration](/.appveyor.yml) to create your own.
0 commit comments