From 1d63d656e26f6230d8797cc1590e2a18e1da6cce Mon Sep 17 00:00:00 2001 From: Tim Carr Date: Wed, 22 Apr 2026 15:51:30 +0800 Subject: [PATCH 1/3] Setup: Add step to install WP-CLI This is used in `composer create-release-assets` to compile the i18n .pot file --- SETUP.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/SETUP.md b/SETUP.md index 2368806c5..8da58ef2e 100644 --- a/SETUP.md +++ b/SETUP.md @@ -42,6 +42,15 @@ curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash nvm install 24 ``` +### WP-CLI + +If [wp-cli](https://wp-cli.org/) is not installed on your local environment, install it using: +```bash +curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar +chmod +x wp-cli.phar +sudo mv wp-cli.phar /usr/local/bin/wp +``` + ### Clone Repository Using your preferred Git client or command line, clone this repository into the `wp-content/plugins/` folder of your local WordPress installation. From b62e8c73f9311b70e13634d80b243c119b724c4c Mon Sep 17 00:00:00 2001 From: Tim Carr Date: Wed, 22 Apr 2026 15:52:27 +0800 Subject: [PATCH 2/3] Update chromedriver URL and command chromedriver must run on port 9515 for tests to function --- SETUP.md | 4 ++-- TESTING.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/SETUP.md b/SETUP.md index 8da58ef2e..a084825ef 100644 --- a/SETUP.md +++ b/SETUP.md @@ -146,7 +146,7 @@ Our change above tells WordPress to use the test database for our test requests, ChromeDriver is a headless (i.e. non-GUI) browser that our test suite uses to run End to End tests, interacting with the Kit Plugin just as a user would - including full JavaScript execution, user inputs etc. -Download ChromeDriver for your Google Chrome version and OS from https://sites.google.com/chromium.org/driver/downloads?authuser=0 +Download ChromeDriver for your Google Chrome version and OS from https://googlechromelabs.github.io/chrome-for-testing/ For Mac users, copy the unzipped executable to `/usr/local/bin`. @@ -155,7 +155,7 @@ For Mac users, copy the unzipped executable to `/usr/local/bin`. First, run the ChromeDriver in a separate Terminal window: ```bash -chromedriver --url-base=/wd/hub +chromedriver --port=9515 --url-base=/wd/hub ``` ![ChromeDriver Screenshot](/.github/docs/chromedriver.png?raw=true) diff --git a/TESTING.md b/TESTING.md index 6d307d76c..0c867bd14 100644 --- a/TESTING.md +++ b/TESTING.md @@ -215,7 +215,7 @@ In a Terminal window, run the ChromeDriver. This is used by our test to mimic u and other elements just as a user would see them: ```bash -chromedriver --url-base=/wd/hub +chromedriver --port=9515 --url-base=/wd/hub ``` In a second Terminal window, run the test to confirm it works: @@ -450,7 +450,7 @@ Once you have written your code and test(s), run the tests to make sure there ar If ChromeDriver isn't running, open a new Terminal window and enter the following command: ```bash -chromedriver --url-base=/wd/hub +chromedriver --port=9515 --url-base=/wd/hub ``` To run the tests, enter the following commands in a separate Terminal window: From fdc396d439e51d1a6aaf89a1294cb000bb54d4ac Mon Sep 17 00:00:00 2001 From: Tim Carr Date: Wed, 22 Apr 2026 15:53:07 +0800 Subject: [PATCH 3/3] Use more specific link for chromedriver downloads --- SETUP.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SETUP.md b/SETUP.md index a084825ef..f91c16056 100644 --- a/SETUP.md +++ b/SETUP.md @@ -146,7 +146,7 @@ Our change above tells WordPress to use the test database for our test requests, ChromeDriver is a headless (i.e. non-GUI) browser that our test suite uses to run End to End tests, interacting with the Kit Plugin just as a user would - including full JavaScript execution, user inputs etc. -Download ChromeDriver for your Google Chrome version and OS from https://googlechromelabs.github.io/chrome-for-testing/ +Download ChromeDriver for your Google Chrome version and OS from https://googlechromelabs.github.io/chrome-for-testing/#stable For Mac users, copy the unzipped executable to `/usr/local/bin`.