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
There is no good way to keep install-wp-tests.sh in sync with the version here. Developers miss out on important updates.
Even just adding a link to this repo at the top of the file, maybe with a "Last updated" date, would be helpful
Sometimes I had to add a User-Agent header to cURL requests as WordPress.org seemed to block requests otherwise.
e.g. curl -H "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (K HTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36" -s "$1" > "$2";
The script could have built-in MariaDB support, e.g. checking for mariadb-admin
The text was updated successfully, but these errors were encountered:
On macOS the files in the tmo wordpress and wordpress-tests-lib can get wiped sometimes, but the folders are still there. But because the script only checks if the folders exist and not the files, it won't recreate the setup.
To make that more robust, we can check if files like "$WP_TESTS_DIR"/includes/functions.php and "$WP_CORE_DIR"/wp-includs.php exist.
Feature Request
Describe your use case and the problem you are facing
This script hasn't really seen any major updates, because they haven't been necessary, but I think there's still some room for improvements.
Describe the solution you'd like
Some thoughts and ideas:
WP_USE_EXT_MYSQL
tofalse
) anymore.install-wp-tests.sh
in sync with the version here. Developers miss out on important updates.Even just adding a link to this repo at the top of the file, maybe with a "Last updated" date, would be helpful
User-Agent
header to cURL requests as WordPress.org seemed to block requests otherwise.e.g.
curl -H "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (K HTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36" -s "$1" > "$2";
mariadb-admin
The text was updated successfully, but these errors were encountered: