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/contributors/code/e2e/README.md
+7-7
Original file line number
Diff line number
Diff line change
@@ -12,29 +12,29 @@ See the dedicated guide if you're working with the previous Jest + Puppeteer fra
12
12
13
13
```bash
14
14
# Run all available tests.
15
-
npm run test:e2e:playwright
15
+
npm run test:e2e
16
16
17
17
# Run in headed mode.
18
-
npm run test:e2e:playwright -- --headed
18
+
npm run test:e2e -- --headed
19
19
20
20
# Run tests with specific browsers (`chromium`, `firefox`, or `webkit`).
21
-
npm run test:e2e:playwright -- --project=webkit --project=firefox
21
+
npm run test:e2e -- --project=webkit --project=firefox
22
22
23
23
# Run a single test file.
24
-
npm run test:e2e:playwright -- <path_to_test_file># E.g., npm run test:e2e:playwright -- site-editor/title.spec.js
24
+
npm run test:e2e -- <path_to_test_file># E.g., npm run test:e2e -- site-editor/title.spec.js
25
25
26
26
# Debugging.
27
-
npm run test:e2e:playwright -- --debug
27
+
npm run test:e2e -- --debug
28
28
```
29
29
30
30
If you're developing in Linux, it currently requires testing Webkit browsers in headed mode. If you don't want to or can't run it with the GUI (e.g. if you don't have a graphic interface), prepend the command with [`xvfb-run`](https://manpages.ubuntu.com/manpages/xenial/man1/xvfb-run.1.html) to run it in a virtual environment.
31
31
32
32
```bash
33
33
# Run all available tests.
34
-
xvfb-run npm run test:e2e:playwright
34
+
xvfb-run npm run test:e2e
35
35
36
36
# Only run webkit tests.
37
-
xvfb-run -- npm run test:e2e:playwright -- --project=webkit
Copy file name to clipboardexpand all lines: docs/getting-started/glossary.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -70,7 +70,7 @@ This refers to a collection of features that ultimately allows users to edit the
70
70
71
71
The CSS styles generated by WordPress and enqueued as an embedded stylesheet in the front end of the site. The stylesheet ID is `global-styles-inline-css`. The contents of this stylesheet come from the default `theme.json` of WordPress, the theme's `theme.json`, and the styles provided by the user via the global styles sidebar in the site editor.
72
72
73
-
See [theme.json reference docs](/docs/reference-guides/theme-json-reference.md)</a>, the [how to guide](/docs/how-to-guides/themes/global-settings-and-styles.md), and an introduction to [styles in the block editor](/docs/explanations/architecture/styles.md).
73
+
See [theme.json reference docs](/docs/reference-guides/theme-json-reference/README.md)</a>, the [how to guide](/docs/how-to-guides/themes/global-settings-and-styles.md), and an introduction to [styles in the block editor](/docs/explanations/architecture/styles.md).
74
74
75
75
Compare to <ahref="#block-styles">block styles</a>.
0 commit comments