Clean up a couple things in //docs/testing/web_tests.md.
There was a stray (really old!) reference to `xcodebuild` instead
of //out for build directories, and I changed a couple places from
talking about //out/Debug or //out/Release to //out/Default just
to be more consistent with how we talk about build directory names
elsewhere.
Change-Id: I5410c5abc7a57bb4c71d42839a3efc142ab152c4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3138433
Reviewed-by: Christian Biesinger <[email protected]>
Commit-Queue: Dirk Pranke <[email protected]>
Cr-Commit-Position: refs/heads/main@{#917368}
diff --git a/docs/testing/web_tests.md b/docs/testing/web_tests.md
index e2a01ab1..50915a7 100644
--- a/docs/testing/web_tests.md
+++ b/docs/testing/web_tests.md
@@ -47,15 +47,15 @@
where they normally don't occur.
```bash
-strip ./xcodebuild/{Debug,Release}/content_shell.app/Contents/MacOS/content_shell
+strip ./out/Default/content_shell.app/Contents/MacOS/content_shell
```
### Running the Tests
The test runner script is in `third_party/blink/tools/run_web_tests.py`.
-To specify which build directory to use (e.g. out/Default, out/Release,
-out/Debug) you should pass the `-t` or `--target` parameter. For example, to
+To specify which build directory to use (e.g. out/Default, etc.)
+you should pass the `-t` or `--target` parameter. For example, to
use the build in `out/Default`, use:
```bash
@@ -242,13 +242,13 @@
"args": ["--blocking-repaint", "--another-flag"]
}
```
-
+
`web_tests/FlagSpecificConfig` is preferred when you need multiple flags,
or the flag is long.
With the config, you can use `--flag-specific=short-name` as a shortcut
of `--additional-driver-flag=--blocking-repaint --additional-driver-flag=--another-flag`.
-
+
`--additional-driver-flags` still works with `web_tests/FlagSpecificConfig`.
For example, when at least `--additional-driver-flag=--blocking-repaint` and
`--additional-driver-flag=--another-flag` are specified, `short-name` will
