Wala shell

Advanced PHP File Manager

Server IP: 127.0.0.1 | PHP Version: 8.3.30 | Domains Hosted: 54

Name	Size	Last Modified
📁 ..	-	2025-09-06 07:07
📄 extension-install.feature Feature: Manage WordPress extension installation @require-wp-5.1.1 Scenario: Installing Extensions theme or plugin Given a WP install When I try `wp theme install test-ext --activate` Then STDERR should be: """ Warning: test-ext: Theme not found Warning: The 'test-ext' theme could not be found. Error: No themes installed. """ When I try `wp plugin install test-ext --activate` Then STDERR should be: """ Warning: test-ext: Plugin not found. Warning: The 'test-ext' plugin could not be found. Error: No plugins installed. """	614 B	2025-09-06 07:07
📄 plugin-activate.feature Feature: Activate WordPress plugins Background: Given a WP install Scenario: Activate a plugin that's already installed When I run `wp plugin activate akismet` Then STDOUT should be: """ Plugin 'akismet' activated. Success: Activated 1 of 1 plugins. """ And the return code should be 0 Scenario: Attempt to activate a plugin that's not installed When I try `wp plugin activate debug-bar` Then STDERR should be: """ Warning: The 'debug-bar' plugin could not be found. Error: No plugins activated. """ And the return code should be 1 When I try `wp plugin activate akismet hello debug-bar` Then STDERR should be: """ Warning: The 'debug-bar' plugin could not be found. Error: Only activated 2 of 3 plugins. """ And STDOUT should be: """ Plugin 'akismet' activated. Plugin 'hello' activated. """ And the return code should be 1 Scenario: Activate all when one plugin is hidden by "all_plugins" filter Given I run `wp plugin install site-secrets` And a wp-content/mu-plugins/hide-us-plugin.php file: """ <?php /** * Plugin Name: Hide Site Secrets on Production * Description: Hides the Site Secrets plugin on production sites * Author: WP-CLI tests / add_filter( 'all_plugins', function( $all_plugins ) { unset( $all_plugins['site-secrets/site-secrets.php'] ); return $all_plugins; } ); """ When I run `wp plugin activate --all` Then STDOUT should contain: """ Plugin 'akismet' activated. Plugin 'hello' activated. """ And STDOUT should not contain: """ Plugin 'site-secrets' activated. """ @require-php-7 Scenario: Activating a plugin with no network wide option passes down correct types Given a wp-content/plugins/example-plugin.php file: """ <?php // Plugin Name: Example Plugin function example_plugin_activate( bool $network_wide = false ) { // Doesn't matter what we do here, we just need a function definition to check the type return; } register_activation_hook( __FILE__, 'example_plugin_activate' ); """ When I run `wp plugin activate example-plugin` Then STDOUT should be: """ Plugin 'example-plugin' activated. Success: Activated 1 of 1 plugins. """ And STDERR should be empty Scenario: Not giving a slug on activate should throw an error unless --all given When I try `wp plugin activate` Then the return code should be 1 And STDERR should be: """ Error: Please specify one or more plugins, or use --all. """ And STDOUT should be empty # But don't give an error if no plugins and --all given for BC. Given I run `wp plugin path` And save STDOUT as {PLUGIN_DIR} And an empty {PLUGIN_DIR} directory When I run `wp plugin activate --all` Then STDOUT should be: """ Success: No plugins activated. """ @require-wp-5.2 Scenario: Activating a plugin that does not meet PHP minimum throws a warning Given a wp-content/plugins/high-requirements.php file: """ <?php /* * Plugin Name: High PHP Requirements * Description: This is meant to not activate because PHP version is too low. * Author: WP-CLI tests * Requires PHP: 99.99 */ """ And I run `wp plugin deactivate --all` And I run `wp cli info \| grep "PHP version" \| awk '{print $3}'` And save STDOUT as {PHP_VERSION} When I try `wp plugin activate high-requirements` Then STDERR should contain: """ Failed to activate plugin. Current PHP version ({PHP_VERSION}) does not meet minimum requirements for High PHP Requirements. The plugin requires PHP 99.99. """ And STDOUT should not contain: """ 1 out of 1 """ And STDOUT should not contain: """ Success: """ Scenario: Adding --exclude with plugin activate --all should exclude the plugins specified via --exclude When I try `wp plugin activate --all --exclude=hello` Then STDOUT should be: """ Plugin 'akismet' activated. Success: Activated 1 of 1 plugins. """ And the return code should be 0 Scenario: Excluding a missing plugin should not throw an error Given a WP install And I run `wp plugin activate --all --exclude=missing-plugin` Then STDERR should be empty And STDOUT should contain: """ Success: """ And the return code should be 0	4.56 KB	2025-09-06 07:07
📄 plugin-auto-updates-disable.feature Feature: Disable auto-updates for WordPress plugins Background: Given a WP install And I run `wp plugin install duplicate-post --ignore-requirements` And I run `wp plugin auto-updates enable --all` @require-wp-5.5 Scenario: Show an error if required params are missing When I try `wp plugin auto-updates disable` Then STDOUT should be empty And STDERR should contain: """ Error: Please specify one or more plugins, or use --all. """ @require-wp-5.5 Scenario: Disable auto-updates for a single plugin When I run `wp plugin auto-updates disable hello` Then STDOUT should be: """ Success: Disabled 1 of 1 plugin auto-updates. """ And the return code should be 0 @require-wp-5.5 Scenario: Disable auto-updates for multiple plugins When I run `wp plugin auto-updates disable hello duplicate-post` Then STDOUT should be: """ Success: Disabled 2 of 2 plugin auto-updates. """ And the return code should be 0 @require-wp-5.5 Scenario: Disable auto-updates for all plugins When I run `wp plugin list --status=inactive --format=count` Then save STDOUT as {PLUGIN_COUNT} When I run `wp plugin auto-updates disable --all` Then STDOUT should be: """ Success: Disabled {PLUGIN_COUNT} of {PLUGIN_COUNT} plugin auto-updates. """ And the return code should be 0 @require-wp-5.5 Scenario: Disable auto-updates for already disabled plugins When I run `wp plugin auto-updates disable hello` And I try `wp plugin auto-updates disable --all` Then STDERR should contain: """ Warning: Auto-updates already disabled for plugin hello. """ And STDERR should contain: """ Error: Only disabled 2 of 3 plugin auto-updates. """ @require-wp-5.5 Scenario: Filter when disabling auto-updates for already enabled plugins When I run `wp plugin auto-updates disable hello` And I run `wp plugin list --auto_update=on --format=count` Then save STDOUT as {PLUGIN_COUNT} When I run `wp plugin auto-updates disable --all --enabled-only` Then STDOUT should be: """ Success: Disabled {PLUGIN_COUNT} of {PLUGIN_COUNT} plugin auto-updates. """ And the return code should be 0 @require-wp-5.5 Scenario: Filter when disabling auto-updates for already disabled selection of plugins When I run `wp plugin auto-updates disable hello` And I run `wp plugin auto-updates disable hello duplicate-post --enabled-only` Then STDOUT should be: """ Success: Disabled 1 of 1 plugin auto-updates. """ And the return code should be 0 @require-wp-5.5 Scenario: Filtering everything away produces an error When I run `wp plugin auto-updates disable hello` And I try `wp plugin auto-updates disable hello --enabled-only` Then STDERR should be: """ Error: No plugins provided to disable auto-updates for. """	2.92 KB	2025-09-06 07:07
📄 plugin-auto-updates-enable.feature Feature: Enable auto-updates for WordPress plugins Background: Given a WP install And I run `wp plugin install duplicate-post --ignore-requirements` @require-wp-5.5 Scenario: Show an error if required params are missing When I try `wp plugin auto-updates enable` Then STDOUT should be empty And STDERR should contain: """ Error: Please specify one or more plugins, or use --all. """ @require-wp-5.5 Scenario: Enable auto-updates for a single plugin When I run `wp plugin auto-updates enable hello` Then STDOUT should be: """ Success: Enabled 1 of 1 plugin auto-updates. """ And the return code should be 0 @require-wp-5.5 Scenario: Enable auto-updates for multiple plugins When I run `wp plugin auto-updates enable hello duplicate-post` Then STDOUT should be: """ Success: Enabled 2 of 2 plugin auto-updates. """ And the return code should be 0 @require-wp-5.5 Scenario: Enable auto-updates for all plugins When I run `wp plugin list --status=inactive --format=count` Then save STDOUT as {PLUGIN_COUNT} When I run `wp plugin auto-updates enable --all` Then STDOUT should be: """ Success: Enabled {PLUGIN_COUNT} of {PLUGIN_COUNT} plugin auto-updates. """ And the return code should be 0 @require-wp-5.5 Scenario: Enable auto-updates for already enabled plugins When I run `wp plugin auto-updates enable hello` And I try `wp plugin auto-updates enable --all` Then STDERR should contain: """ Warning: Auto-updates already enabled for plugin hello. """ And STDERR should contain: """ Error: Only enabled 2 of 3 plugin auto-updates. """ @require-wp-5.5 Scenario: Filter when enabling auto-updates for already enabled plugins When I run `wp plugin auto-updates enable hello` And I run `wp plugin list --status=inactive --auto_update=off --format=count` Then save STDOUT as {PLUGIN_COUNT} When I run `wp plugin auto-updates enable --all --disabled-only` Then STDOUT should be: """ Success: Enabled {PLUGIN_COUNT} of {PLUGIN_COUNT} plugin auto-updates. """ And the return code should be 0 @require-wp-5.5 Scenario: Filter when enabling auto-updates for already enabled selection of plugins When I run `wp plugin auto-updates enable hello` And I run `wp plugin auto-updates enable hello duplicate-post --disabled-only` Then STDOUT should be: """ Success: Enabled 1 of 1 plugin auto-updates. """ And the return code should be 0 @require-wp-5.5 Scenario: Filtering everything away produces an error When I run `wp plugin auto-updates enable hello` And I try `wp plugin auto-updates enable hello --disabled-only` Then STDERR should be: """ Error: No plugins provided to enable auto-updates for. """	2.86 KB	2025-09-06 07:07
📄 plugin-auto-updates-status.feature Feature: Show the status of auto-updates for WordPress plugins Background: Given a WP install And I run `wp plugin install duplicate-post --ignore-requirements` @require-wp-5.5 Scenario: Show an error if required params are missing When I try `wp plugin auto-updates status` Then STDOUT should be empty And STDERR should contain: """ Error: Please specify one or more plugins, or use --all. """ @require-wp-5.5 Scenario: Show the status of auto-updates of a single plugin When I run `wp plugin auto-updates status hello` Then STDOUT should be a table containing rows: \| name \| status \| \| hello \| disabled \| And the return code should be 0 @require-wp-5.5 Scenario: Show the status of auto-updates multiple plugins When I run `wp plugin auto-updates status duplicate-post hello` Then STDOUT should be a table containing rows: \| name \| status \| \| duplicate-post \| disabled \| \| hello \| disabled \| And the return code should be 0 @require-wp-5.5 Scenario: Show the status of auto-updates all installed plugins When I run `wp plugin auto-updates status --all` Then STDOUT should be a table containing rows: \| name \| status \| \| akismet \| disabled \| \| duplicate-post \| disabled \| \| hello \| disabled \| And the return code should be 0 When I run `wp plugin auto-updates enable --all` And I run `wp plugin auto-updates status --all` Then STDOUT should be a table containing rows: \| name \| status \| \| akismet \| enabled \| \| duplicate-post \| enabled \| \| hello \| enabled \| And the return code should be 0 @require-wp-5.5 Scenario: The status can be filtered to only show enabled or disabled plugins Given I run `wp plugin auto-updates enable hello` When I run `wp plugin auto-updates status --all` Then STDOUT should be a table containing rows: \| name \| status \| \| akismet \| disabled \| \| duplicate-post \| disabled \| \| hello \| enabled \| And the return code should be 0 When I run `wp plugin auto-updates status --all --enabled-only` Then STDOUT should be a table containing rows: \| name \| status \| \| hello \| enabled \| And the return code should be 0 When I run `wp plugin auto-updates status --all --disabled-only` Then STDOUT should be a table containing rows: \| name \| status \| \| akismet \| disabled \| \| duplicate-post \| disabled \| And the return code should be 0 When I try `wp plugin auto-updates status --all --enabled-only --disabled-only` Then STDOUT should be empty And STDERR should contain: """ Error: --enabled-only and --disabled-only are mutually exclusive and cannot be used at the same time. """ @require-wp-5.5 Scenario: The fields can be shown individually Given I run `wp plugin auto-updates enable hello` When I run `wp plugin auto-updates status --all --disabled-only --field=name` Then STDOUT should be: """ akismet duplicate-post """ When I run `wp plugin auto-updates status hello --field=status` Then STDOUT should be: """ enabled """ @require-wp-5.5 Scenario: Formatting options work When I run `wp plugin auto-updates status --all --format=json` Then STDOUT should be: """ [{"name":"akismet","status":"disabled"},{"name":"hello","status":"disabled"},{"name":"duplicate-post","status":"disabled"}] """ When I run `wp plugin auto-updates status --all --format=csv` Then STDOUT should be: """ name,status akismet,disabled hello,disabled duplicate-post,disabled """ @require-wp-5.5 Scenario: Handle malformed option value When I run `wp option update auto_update_plugins ""` And I try `wp plugin auto-updates status hello` Then the return code should be 0 And STDERR should be empty	4.05 KB	2025-09-06 07:07
📄 plugin-deactivate.feature Feature: Deactivate WordPress plugins Background: Given a WP install And I run `wp plugin activate akismet hello` Scenario: Deactivate a plugin that's already activated When I run `wp plugin deactivate akismet` Then STDOUT should be: """ Plugin 'akismet' deactivated. Success: Deactivated 1 of 1 plugins. """ And the return code should be 0 Scenario: Attempt to deactivate a plugin that's not installed When I try `wp plugin deactivate debug-bar` Then STDERR should be: """ Warning: The 'debug-bar' plugin could not be found. Error: No plugins deactivated. """ And STDOUT should be empty And the return code should be 1 When I try `wp plugin deactivate akismet hello debug-bar` Then STDERR should be: """ Warning: The 'debug-bar' plugin could not be found. Error: Only deactivated 2 of 3 plugins. """ And STDOUT should be: """ Plugin 'akismet' deactivated. Plugin 'hello' deactivated. """ And the return code should be 1 Scenario: Deactivate all when a previously active plugin is hidden by "all_plugins" filter Given a wp-content/mu-plugins/hide-active-plugin.php file: """ <?php /** * Plugin Name: Hide an Active Plugin * Description: Hides Akismet plugin, which is already active * Author: WP-CLI tests */ add_filter( 'all_plugins', function( $all_plugins ) { unset( $all_plugins['akismet/akismet.php'] ); return $all_plugins; } ); """ When I run `wp plugin deactivate --all` Then STDOUT should not contain: """ Plugin 'akismet' deactivated. """ Scenario: Not giving a slug on deactivate should throw an error unless --all given When I try `wp plugin deactivate` Then the return code should be 1 And STDERR should be: """ Error: Please specify one or more plugins, or use --all. """ And STDOUT should be empty # But don't give an error if no plugins and --all given for BC. Given I run `wp plugin path` And save STDOUT as {PLUGIN_DIR} And an empty {PLUGIN_DIR} directory When I run `wp plugin deactivate --all` Then STDOUT should be: """ Success: No plugins deactivated. """ Scenario: Adding --exclude with plugin deactivate --all should exclude the plugins specified via --exclude When I try `wp plugin deactivate --all --exclude=hello` Then STDOUT should be: """ Plugin 'akismet' deactivated. Success: Deactivated 1 of 1 plugins. """ And the return code should be 0 Scenario: Adding --exclude with plugin deactivate should throw an error unless --all given When I try `wp plugin deactivate --exclude=hello` Then the return code should be 1 And STDERR should be: """ Error: Please specify one or more plugins, or use --all. """ And STDOUT should be empty Scenario: Excluding a missing plugin should not throw an error Given a WP install And I run `wp plugin deactivate --all --exclude=missing-plugin` Then STDERR should be empty And STDOUT should contain: """ Success: """ And the return code should be 0	3.21 KB	2025-09-06 07:07
📄 plugin-delete.feature Feature: Delete WordPress plugins Background: Given a WP install Scenario: Delete an installed plugin When I run `wp plugin delete akismet` Then STDOUT should be: """ Deleted 'akismet' plugin. Success: Deleted 1 of 1 plugins. """ And the return code should be 0 Scenario: Delete all installed plugins When I run `wp plugin delete --all` Then STDOUT should be: """ Deleted 'akismet' plugin. Deleted 'hello' plugin. Success: Deleted 2 of 2 plugins. """ And the return code should be 0 When I run the previous command again Then STDOUT should be: """ Success: No plugins deleted. """ Scenario: Attempting to delete a plugin that doesn't exist When I try `wp plugin delete debug-bar` Then STDOUT should be: """ Success: Plugin already deleted. """ And STDERR should be: """ Warning: The 'debug-bar' plugin could not be found. """ And the return code should be 0 Scenario: Excluding a plugin from deletion when using --all switch When I try `wp plugin delete --all --exclude=akismet,hello` Then STDOUT should be: """ Success: No plugins deleted. """ And the return code should be 0 Scenario: Excluding a missing plugin should not throw an error Given a WP install And I run `wp plugin delete --all --exclude=missing-plugin` Then STDERR should be empty And STDOUT should contain: """ Success: """ And the return code should be 0 Scenario: Reports a failure for a plugin that can't be deleted Given a WP install When I run `chmod -w wp-content/plugins/akismet` And I try `wp plugin delete akismet` Then STDERR should contain: """ Warning: The 'akismet' plugin could not be deleted. """ And STDERR should contain: """ Error: No plugins deleted. """ And STDOUT should not contain: """ Success: """ When I run `chmod +w wp-content/plugins/akismet` And I run `wp plugin delete akismet` Then STDERR should not contain: """ Error: """ And STDOUT should contain: """ Success: """	2.2 KB	2025-09-06 07:07
📄 plugin-get.feature Feature: Get WordPress plugin Scenario: Get plugin info Given a WP install And a wp-content/plugins/foo.php file: """ /** * Plugin Name: Sample Plugin * Description: Description for sample plugin. * Requires at least: 6.0 * Requires PHP: 5.6 * Version: 1.0.0 * Author: John Doe * Author URI: https://example.com/ * License: GPLv2 or later * License URI: https://www.gnu.org/licenses/old-licenses/gpl-2.0.html * Text Domain: sample-plugin / """ When I run `wp plugin get foo --fields=name,author,version,status` Then STDOUT should be a table containing rows: \| Field \| Value \| \| name \| foo \| \| author \| John Doe \| \| version \| 1.0.0 \| \| status \| inactive \| When I run `wp plugin get foo --format=json` Then STDOUT should be: """ {"name":"foo","title":"Sample Plugin","author":"John Doe","version":"1.0.0","description":"Description for sample plugin.","status":"inactive"} """ @require-wp-6.5 Scenario: Get Requires Plugins header of plugin Given a WP install And a wp-content/plugins/foo.php file: """ <?php /* * Plugin Name: Foo * Description: Foo plugin * Author: John Doe * Requires Plugins: jetpack, woocommerce / """ When I run `wp plugin get foo --field=requires_plugins` Then STDOUT should be: """ jetpack, woocommerce """ @require-wp-5.3 Scenario: Get Requires PHP and Requires WP header of plugin Given a WP install And a wp-content/plugins/foo.php file: """ <?php /* * Plugin Name: Foo * Description: Foo plugin * Author: John Doe * Requires at least: 6.2 * Requires PHP: 7.4 */ """ When I run `wp plugin get foo --fields=requires_wp,requires_php` Then STDOUT should be a table containing rows: \| Field \| Value \| \| requires_wp \| 6.2 \| \| requires_php \| 7.4 \|	2.03 KB	2025-09-06 07:07
📄 plugin-install-github-latest.feature Feature: Install WordPress plugins from GitHub Scenario: Verify that providing a plugin releases/latest GitHub URL will get the latest ZIP Given a WP install When I run `wp plugin install https://github.com/danielbachhuber/one-time-login/releases/latest` Then STDOUT should contain: """ Latest release resolved to Version """ And STDOUT should contain: """ package from https://api.github.com/repos/danielbachhuber/one-time-login/zipball/ """ And STDOUT should contain: """ Plugin installed successfully. Success: Installed 1 of 1 plugins. """	627 B	2025-09-06 07:07
📄 plugin-install.feature Feature: Install WordPress plugins Background: Given an empty cache Scenario: Branch names should be removed from Github projects Given a WP install When I run `wp plugin install https://github.com/wp-cli-test/generic-example-plugin/archive/refs/heads/master.zip --activate` Then STDOUT should contain: """ Downloading install """ And STDOUT should contain: """ package from https://github.com/wp-cli-test/generic-example-plugin/archive/refs/heads/master.zip """ And STDOUT should contain: """ Renamed Github-based project from 'generic-example-plugin-master' to 'generic-example-plugin'. """ And STDOUT should contain: """ Plugin installed successfully. """ And the wp-content/plugins/generic-example-plugin directory should exist And the wp-content/plugins/generic-example-plugin-master directory should not exist When I try `wp plugin install https://github.com/wp-cli-test/generic-example-plugin/archive/refs/heads/master.zip` Then STDERR should contain: """ Warning: Destination folder already exists """ And STDERR should contain: """ Error: No plugins installed. """ And the wp-content/plugins/generic-example-plugin directory should exist And the wp-content/plugins/generic-example-plugin-master directory should not exist And the return code should be 1 When I run `wp plugin install https://github.com/wp-cli-test/generic-example-plugin/archive/refs/heads/master.zip --force` Then STDOUT should contain: """ Plugin updated successfully. """ And the wp-content/plugins/generic-example-plugin directory should exist And the wp-content/plugins/generic-example-plugin-master directory should not exist # However if the plugin slug ('modern-framework') does not match the project name then it's downloaded to wrong directory. When I run `wp plugin install https://github.com/Miller-Media/modern-wordpress/archive/master.zip` Then STDOUT should contain: """ Plugin installed successfully. """ And STDOUT should match /Renamed Github-based project from 'modern-(?:wordpress\|framework)-master' to 'modern-wordpress'/ # Wrong directory. And the wp-content/plugins/modern-wordpress directory should exist And the wp-content/plugins/modern-framework directory should not exist Scenario: Don't attempt to rename ZIPs uploaded to GitHub's releases page Given a WP install When I run `wp plugin install https://github.com/wp-cli-test/generic-example-plugin/releases/download/v0.1.0/generic-example-plugin.0.1.0.zip` Then STDOUT should contain: """ Plugin installed successfully. """ And STDOUT should not contain: """ Renamed Github-based project from 'generic-example-plugin-0.1.0' to 'generic-example-plugin'. """ And the wp-content/plugins/generic-example-plugin directory should exist Scenario: Don't attempt to rename ZIPs coming from a GitHub raw source Given a WP install When I run `wp plugin install https://github.com/Miller-Media/modern-wordpress/raw/master/builds/modern-framework-stable.zip` Then STDOUT should contain: """ Plugin installed successfully. """ And STDOUT should not contain: """ Renamed Github-based project from 'modern-framework-stable' to 'modern-framework'. """ And the wp-content/plugins/modern-framework directory should exist Scenario: Installing respects WP_PROXY_HOST and WP_PROXY_PORT Given a WP install And a invalid-proxy-details.php file: """ <?php define( 'WP_PROXY_HOST', 'https://wp-cli.org' ); define( 'WP_PROXY_PORT', '443' ); """ When I try `wp --require=invalid-proxy-details.php plugin install debug-bar` Then STDERR should contain: """ Warning: debug-bar: An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. """ And STDERR should contain: """ Error: No plugins installed. """ And STDOUT should be empty And the return code should be 1 When I run `wp plugin install debug-bar` Then STDOUT should contain: """ Plugin installed successfully. """ Scenario: Return code is 1 when one or more plugin installations fail Given a WP install When I try `wp plugin install site-secrets site-secrets-not-a-plugin` Then STDERR should contain: """ Warning: """ And STDERR should contain: """ site-secrets-not-a-plugin """ And STDERR should contain: """ Error: Only installed 1 of 2 plugins. """ And STDOUT should contain: """ Installing Site Secrets """ And STDOUT should contain: """ Plugin installed successfully. """ And the return code should be 1 When I try `wp plugin install site-secrets` Then STDOUT should be: """ Success: Plugin already installed. """ And STDERR should be: """ Warning: site-secrets: Plugin already installed. """ And the return code should be 0 When I try `wp plugin install site-secrets-not-a-plugin` Then STDERR should contain: """ Warning: """ And STDERR should contain: """ site-secrets-not-a-plugin """ And STDERR should contain: """ Error: No plugins installed. """ And the return code should be 1 Scenario: Paths aren't backslashed when destination folder already exists Given a WP install When I run `pwd` Then save STDOUT as {WORKING_DIR} When I run `rm wp-content/plugins/akismet/akismet.php` Then the return code should be 0 When I try `wp plugin install akismet --ignore-requirements` Then STDERR should contain: """ Warning: Destination folder already exists. "{WORKING_DIR}/wp-content/plugins/akismet/" """ And STDERR should contain: """ Error: No plugins installed. """ And the return code should be 1 Scenario: For Github archive URLs use the Github project name as the plugin directory Given a WP install When I run `wp plugin install https://github.com/wp-cli-test/generic-example-plugin/archive/v0.1.0.zip` Then STDOUT should contain: """ Plugin installed successfully. """ And STDOUT should contain: """ package from https://github.com/wp-cli-test/generic-example-plugin/archive/v0.1.0.zip """ And STDOUT should contain: """ Renamed Github-based project from 'generic-example-plugin-0.1.0' to 'generic-example-plugin'. """ And the wp-content/plugins/generic-example-plugin directory should exist And the wp-content/plugins/generic-example-plugi directory should not exist And the wp-content/plugins/generic-example-plugin-0.1.0 directory should not exist When I run `wp plugin install https://github.com/Automattic/sensei/archive/version/1.9.19.zip` Then STDOUT should contain: """ Plugin installed successfully. """ And STDOUT should contain: """ package from https://github.com/Automattic/sensei/archive/version/1.9.19.zip """ And STDOUT should contain: """ Renamed Github-based project from 'sensei-version-1.9.19' to 'sensei'. """ And the wp-content/plugins/sensei directory should exist And the wp-content/plugins/archive directory should not exist And the wp-content/plugins/sensei-version-1.9.19 directory should not exist Scenario: Verify installed plugin activation Given a WP install When I run `wp plugin install site-secrets` Then STDOUT should not be empty When I try `wp plugin install site-secrets --activate` Then STDERR should contain: """ Warning: site-secrets: Plugin already installed. """ And STDOUT should contain: """ Activating 'site-secrets'... Plugin 'site-secrets' activated. Success: Plugin already installed. """ @require-php-7 Scenario: Can't install plugin that requires a newer version of WordPress Given a WP install When I run `wp core download --version=6.4 --force` And I run `rm -r wp-content/themes/*` And I try `wp plugin install wp-super-cache` Then STDERR should contain: """ Warning: wp-super-cache: This plugin does not work with your version of WordPress """ And STDERR should contain: """ Error: No plugins installed. """ @less-than-php-7.4 @require-wp-6.6 Scenario: Can't install plugin that requires a newer version of PHP Given a WP install And I try `wp plugin install contact-form-7` Then STDERR should contain: """ Warning: contact-form-7: This plugin does not work with your version of PHP """ And STDERR should contain: """ Error: No plugins installed. """	8.85 KB	2025-09-06 07:07
📄 plugin-list-recently-active.feature Feature: List recently active WordPress plugins Scenario: Verify plugin installation, activation, deactivation and confirm listing recently active plugins list is correct Given a WP install When I run `wp plugin install site-secrets debug-bar p2-by-email --activate` Then STDOUT should contain: """ Plugin 'site-secrets' activated. """ And STDOUT should contain: """ Plugin 'debug-bar' activated. """ And STDOUT should contain: """ Plugin 'p2-by-email' activated. """ When I run `wp plugin list --recently-active --field=name --format=json` Then STDOUT should be: """ [] """ When I run `wp plugin activate akismet` Then STDOUT should contain: """ Plugin 'akismet' activated. """ When I run `wp plugin deactivate site-secrets debug-bar` Then STDOUT should contain: """ Plugin 'site-secrets' deactivated. Plugin 'debug-bar' deactivated. Success: Deactivated 2 of 2 plugins. """ When I run `wp plugin list --recently-active --field=name` Then STDOUT should be a table containing rows: \| debug-bar \| \| site-secrets \| Scenario: Use recently active plugin to activate plugins Given a WP install When I run `wp plugin install site-secrets debug-bar --activate` Then STDOUT should contain: """ Plugin 'site-secrets' activated. """ And STDOUT should contain: """ Plugin 'debug-bar' activated. """ When I run `wp plugin deactivate site-secrets debug-bar` Then STDOUT should be: """ Plugin 'site-secrets' deactivated. Plugin 'debug-bar' deactivated. Success: Deactivated 2 of 2 plugins. """ When I run `wp plugin activate $(wp plugin list --recently-active --field=name)` Then STDOUT should contain: """ Plugin 'debug-bar' activated. """ And STDOUT should contain: """ Plugin 'site-secrets' activated. """ Scenario: For a MU site, verify plugin installation, activation, deactivation and confirm listing recently active plugins list is correct Given a WP multisite install When I run `wp plugin install site-secrets debug-bar p2-by-email --activate-network` Then STDOUT should contain: """ Plugin 'site-secrets' network activated. """ And STDOUT should contain: """ Plugin 'debug-bar' network activated. """ And STDOUT should contain: """ Plugin 'p2-by-email' network activated. """ When I run `wp plugin activate akismet --network` Then STDOUT should contain: """ Plugin 'akismet' network activated. """ When I run `wp plugin list --recently-active --field=name --format=json` Then STDOUT should be: """ [] """ When I run `wp plugin deactivate site-secrets debug-bar --network` Then STDOUT should be: """ Plugin 'site-secrets' network deactivated. Plugin 'debug-bar' network deactivated. Success: Network deactivated 2 of 2 plugins. """ When I run `wp plugin list --recently-active --field=name` Then STDOUT should be a table containing rows: \| debug-bar \| \| site-secrets \| Scenario: For a MU site, use recently active plugin to activate plugins Given a WP multisite install When I run `wp plugin install site-secrets debug-bar --activate-network` Then STDOUT should contain: """ Plugin 'site-secrets' network activated. """ And STDOUT should contain: """ Plugin 'debug-bar' network activated. """ When I run `wp plugin deactivate site-secrets debug-bar --network` Then STDOUT should be: """ Plugin 'site-secrets' network deactivated. Plugin 'debug-bar' network deactivated. Success: Network deactivated 2 of 2 plugins. """ When I run `wp plugin activate $(wp plugin list --recently-active --field=name) --network` Then STDOUT should contain: """ Plugin 'site-secrets' network activated. """ And STDOUT should contain: """ Plugin 'debug-bar' network activated. """	4.13 KB	2025-05-25 12:40
📄 plugin-list-wporg-status.feature Feature: Check the status of plugins on WordPress.org @require-wp-5.2 Scenario: Install plugins and check the status on wp.org. Given a WP install And I run `wp plugin install wordpress-importer --version=0.5 --force` And I run `wp plugin install https://downloads.wordpress.org/plugin/no-longer-in-directory.1.0.62.zip` And a wp-content/plugins/never-wporg/never-wporg.php file: """ <?php /** * Plugin Name: This plugin was never in the WordPress.org plugin directory * Version: 2.0.2 */ """ When I run `wp plugin list --name=wordpress-importer --field=wporg_last_updated` Then STDOUT should not be empty And save STDOUT as {COMMIT_DATE} When I run `wp plugin list --fields=name,wporg_status` Then STDOUT should be a table containing rows: \| name \| wporg_status \| \| wordpress-importer \| active \| \| no-longer-in-directory \| closed \| \| never-wporg \| \| When I run `wp plugin list --fields=name,wporg_last_updated` Then STDOUT should be a table containing rows: \| name \| wporg_last_updated \| \| wordpress-importer \| {COMMIT_DATE} \| \| no-longer-in-directory \| 2017-11-13 \| \| never-wporg \| \| When I run `wp plugin list --fields=name,wporg_status,wporg_last_updated` Then STDOUT should be a table containing rows: \| name \| wporg_status \| wporg_last_updated \| \| wordpress-importer \| active \| {COMMIT_DATE} \| \| no-longer-in-directory \| closed \| 2017-11-13 \| \| never-wporg \| \| \|	1.75 KB	2025-09-06 07:07
📄 plugin-search.feature Feature: Search WordPress.org plugins Scenario: Search for plugins with active_installs field Given a WP install When I run `wp plugin search foo --fields=name,slug,active_installs` Then STDOUT should contain: """ Success: Showing """ When I run `wp plugin search foo --fields=name,slug,active_installs --format=csv` Then STDOUT should not contain: """ Success: Showing """ And STDOUT should contain: """ name,slug,active_installs """	518 B	2025-05-25 12:40
📄 plugin-status.feature Feature: List the status of plugins @require-wp-4.0 Scenario: Status should include drop-ins Given a WP install And a wp-content/db-error.php file: """ <?php """ When I run `wp plugin status` Then STDOUT should contain: """ D db-error.php """ And STDOUT should contain: """ D = Drop-In """ And STDERR should be empty	401 B	2025-05-25 12:40
📄 plugin-toggle.feature Feature: Toggle the activation status of a plugin Background: Given a WP install Scenario: Toggle the status of a plugin When I run `wp plugin toggle akismet` Then STDOUT should be: """ Plugin 'akismet' activated. Success: Toggled 1 of 1 plugins. """ When I run `wp plugin toggle akismet` Then STDOUT should be: """ Plugin 'akismet' deactivated. Success: Toggled 1 of 1 plugins. """ Scenario: Toggling the status of a plugin that doesn't exist When I try `wp plugin toggle akismet debug-bar` Then STDERR should be: """ Warning: The 'debug-bar' plugin could not be found. Error: Only toggled 1 of 2 plugins. """ And STDOUT should be: """ Plugin 'akismet' activated. """ And the return code should be 1 When I try `wp plugin toggle debug-bar co-authors-plus` Then STDERR should be: """ Warning: The 'debug-bar' plugin could not be found. Warning: The 'co-authors-plus' plugin could not be found. Error: No plugins toggled. """ And STDOUT should be empty And the return code should be 1	1.14 KB	2025-05-25 12:40
📄 plugin-uninstall.feature Feature: Uninstall a WordPress plugin Background: Given a WP install Scenario: Uninstall an installed plugin should uninstall, delete files When I run `wp plugin uninstall akismet` Then STDOUT should be: """ Uninstalled and deleted 'akismet' plugin. Success: Uninstalled 1 of 1 plugins. """ And the return code should be 0 And STDERR should be empty And the wp-content/plugins/akismet directory should not exist Scenario: Uninstall an installed plugin but do not delete its files When I run `wp plugin uninstall akismet --skip-delete` Then STDOUT should be: """ Ran uninstall procedure for 'akismet' plugin without deleting. Success: Uninstalled 1 of 1 plugins. """ And the return code should be 0 And STDERR should be empty And the wp-content/plugins/akismet directory should exist Scenario: Uninstall a plugin that is not in a folder and has custom name When I run `wp plugin uninstall hello` Then STDOUT should be: """ Uninstalled and deleted 'hello' plugin. Success: Uninstalled 1 of 1 plugins. """ And the return code should be 0 And STDERR should be empty And the wp-content/plugins/hello.php file should not exist Scenario: Missing required inputs When I try `wp plugin uninstall` Then STDERR should be: """ Error: Please specify one or more plugins, or use --all. """ And the return code should be 1 And STDOUT should be empty Scenario: Attempting to uninstall a plugin that's activated When I run `wp plugin activate akismet` Then STDOUT should not be empty When I try `wp plugin uninstall akismet` Then STDERR should be: """ Warning: The 'akismet' plugin is active. Error: No plugins uninstalled. """ And STDOUT should be empty And the return code should be 1 Scenario: Attempting to uninstall a plugin that's activated (using --deactivate) When I run `wp plugin activate akismet` Then STDOUT should not be empty When I try `wp plugin uninstall akismet --deactivate` Then STDOUT should be: """ Deactivating 'akismet'... Plugin 'akismet' deactivated. Uninstalled and deleted 'akismet' plugin. Success: Uninstalled 1 of 1 plugins. """ And STDERR should be empty And the return code should be 0 Scenario: Attempting to uninstall a plugin that doesn't exist When I try `wp plugin uninstall debug-bar` Then STDERR should be: """ Warning: The 'debug-bar' plugin could not be found. Error: No plugins uninstalled. """ And the return code should be 1 Scenario: Uninstall all installed plugins When I run `wp plugin uninstall --all` Then STDOUT should be: """ Uninstalled and deleted 'akismet' plugin. Uninstalled and deleted 'hello' plugin. Success: Uninstalled 2 of 2 plugins. """ And the return code should be 0 And STDERR should be empty When I run the previous command again Then STDOUT should be: """ Success: No plugins uninstalled. """ And STDERR should be empty Scenario: Uninstall all installed plugins when one or more activated When I run `wp plugin activate --all` Then STDOUT should contain: """ Success: Activated 2 of 2 plugins. """ When I try `wp plugin uninstall --all` Then STDERR should be: """ Warning: The 'akismet' plugin is active. Warning: The 'hello' plugin is active. Error: No plugins uninstalled. """ And the return code should be 1 And STDOUT should be empty When I run `wp plugin uninstall --deactivate --all` Then STDOUT should contain: """ Success: Uninstalled 2 of 2 plugins. """ And STDERR should be empty Scenario: Excluding a plugin from uninstallation when using --all switch When I try `wp plugin uninstall --all --exclude=akismet,hello` Then STDOUT should be: """ Success: No plugins uninstalled. """ And the return code should be 0 And STDERR should be empty Scenario: Excluding a missing plugin should not throw an error Given a WP install And I run `wp plugin uninstall --all --exclude=missing-plugin` Then STDERR should be empty And STDOUT should contain: """ Success: """ And the return code should be 0 @require-wp-5.2 Scenario: Uninstalling a plugin should remove its language pack Given a WP install And I run `wp plugin install wordpress-importer` And I run `wp core language install fr_FR` And I run `wp site switch-language fr_FR` When I run `wp language plugin install wordpress-importer fr_FR` Then STDOUT should contain: """ Success: """ And the wp-content/languages/plugins/wordpress-importer-fr_FR.mo file should exist And the wp-content/languages/plugins/wordpress-importer-fr_FR.po file should exist And the wp-content/languages/plugins/wordpress-importer-fr_FR.l10n.php file should exist When I run `wp plugin uninstall wordpress-importer` Then STDOUT should contain: """ Success: """ And the wp-content/languages/plugins/wordpress-importer-fr_FR.mo file should not exist And the wp-content/languages/plugins/wordpress-importer-fr_FR.po file should not exist And the wp-content/languages/plugins/wordpress-importer-fr_FR.l10n.php file should not exist And STDERR should be empty @require-wp-5.2 Scenario: Uninstalling a plugin should remove its update info Given a WP install And I run `wp plugin install wordpress-importer --version=0.6` And I run `wp plugin status wordpress-importer` And I run `wp transient get --network update_plugins` Then STDOUT should contain: """ wordpress-importer """ When I run `wp plugin uninstall wordpress-importer` Then STDOUT should contain: """ Success: """ When I run `wp transient get --network update_plugins` Then STDOUT should not contain: """ wordpress-importer """	6.03 KB	2025-09-06 07:07
📄 plugin-update.feature Feature: Update WordPress plugins @require-wp-5.2 Scenario: Updating plugin with invalid version shouldn't remove the old version Given a WP install When I run `wp plugin install wordpress-importer --version=0.5 --force` Then STDOUT should not be empty When I run `wp plugin list --name=wordpress-importer --field=update_version` Then STDOUT should not be empty And save STDOUT as {UPDATE_VERSION} When I run `wp plugin list` Then STDOUT should be a table containing rows: \| name \| status \| update \| version \| update_version \| auto_update \| \| wordpress-importer \| inactive \| available \| 0.5 \| {UPDATE_VERSION} \| off \| When I try `wp plugin update akismet --version=0.5.3` Then STDERR should be: """ Error: Can't find the requested plugin's version 0.5.3 in the WordPress.org plugin repository (HTTP code 404). """ And the return code should be 1 When I run `wp plugin list` Then STDOUT should be a table containing rows: \| name \| status \| update \| version \| update_version \| auto_update \| \| wordpress-importer \| inactive \| available \| 0.5 \| {UPDATE_VERSION} \| off \| When I run `wp plugin update wordpress-importer` Then STDOUT should not be empty When I run `wp plugin list` Then STDOUT should be a table containing rows: \| name \| status \| update \| version \| update_version \| auto_update \| \| wordpress-importer \| inactive \| none \| {UPDATE_VERSION} \| \| off \| Scenario: Error when both --minor and --patch are provided Given a WP install When I try `wp plugin update --patch --minor --all` Then STDERR should be: """ Error: --minor and --patch cannot be used together. """ And the return code should be 1 @require-wp-5.2 Scenario: Exclude plugin updates from bulk updates. Given a WP install When I run `wp plugin install wordpress-importer --version=0.5 --force` Then STDOUT should contain: """ Downloading install """ And STDOUT should contain: """ package from https://downloads.wordpress.org/plugin/wordpress-importer.0.5.zip... """ When I run `wp plugin status wordpress-importer` Then STDOUT should contain: """ Update available """ When I run `wp plugin update --all --exclude=wordpress-importer \| grep 'Skipped'` Then STDOUT should contain: """ wordpress-importer """ When I run `wp plugin status wordpress-importer` Then STDOUT should contain: """ Update available """ @require-wp-5.2 Scenario: Update a plugin to its latest patch release Given a WP install And I run `wp plugin install --force wordpress-importer --version=0.5` When I run `wp plugin update wordpress-importer --patch` Then STDOUT should contain: """ Success: Updated 1 of 1 plugins. """ When I run `wp plugin get wordpress-importer --field=version` Then STDOUT should be: """ 0.5.2 """ # Akismet currently requires WordPress 5.8 @require-wp-5.8 Scenario: Update a plugin to its latest minor release Given a WP install And I run `wp plugin install --force akismet --version=2.5.4` When I run `wp plugin update akismet --minor` Then STDOUT should contain: """ Success: Updated 1 of 1 plugins. """ When I run `wp plugin get akismet --field=version` Then STDOUT should be: """ 2.6.1 """ @require-wp-5.2 Scenario: Not giving a slug on update should throw an error unless --all given Given a WP install And I run `wp plugin path` And save STDOUT as {PLUGIN_DIR} And an empty {PLUGIN_DIR} directory # No plugins installed. Don't give an error if --all given for BC. When I run `wp plugin update --all` Then STDOUT should be: """ Success: No plugins installed. """ When I run `wp plugin update --version=0.6 --all` Then STDOUT should be: """ Success: No plugins installed. """ # One plugin installed. Given I run `wp plugin install wordpress-importer --version=0.5 --force` When I try `wp plugin update` Then the return code should be 1 And STDERR should be: """ Error: Please specify one or more plugins, or use --all. """ And STDOUT should be empty When I run `wp plugin update --all` Then STDOUT should contain: """ Success: Updated """ When I run the previous command again Then STDOUT should be: """ Success: Plugin already updated. """ # Note: if given version then re-installs. When I run `wp plugin update --version=0.6 --all` Then STDOUT should contain: """ Success: Installed 1 of 1 plugins. """ When I run the previous command again Then STDOUT should contain: """ Success: Installed 1 of 1 plugins. """ # Two plugins installed. Given I run `wp plugin install akismet --version=2.5.4` When I run `wp plugin update --all` Then STDOUT should contain: """ Success: Updated """ When I run the previous command again # BUG: note this message should be plural. Then STDOUT should be: """ Success: Plugin already updated. """ # Using version with all rarely makes sense and should probably error and do nothing. When I try `wp plugin update --version=2.5.4 --all` Then the return code should be 1 And STDOUT should contain: """ Success: Installed 1 of 1 plugins. """ And STDERR should be: """ Error: Can't find the requested plugin's version 2.5.4 in the WordPress.org plugin repository (HTTP code 404). """ # Akismet currently requires WordPress 5.8 @require-wp-5.8 Scenario: Plugin updates that error should not report a success Given a WP install And I run `wp plugin install --force akismet --version=4.0` When I run `chmod -w wp-content/plugins/akismet` And I try `wp plugin update akismet` Then STDERR should contain: """ Error: """ And STDOUT should not contain: """ Success: """ When I run `chmod +w wp-content/plugins/akismet` And I try `wp plugin update akismet` Then STDERR should not contain: """ Error: """ And STDOUT should contain: """ Success: """ # Akismet currently requires WordPress 5.8, so there's a warning because of it. @require-wp-5.8 Scenario: Excluding a missing plugin should not throw an error Given a WP install And I run `wp plugin update --all --exclude=missing-plugin` Then STDERR should be empty And STDOUT should contain: """ Success: """ And the return code should be 0 @require-wp-5.2 Scenario: Updating all plugins with some of them having an invalid version shouldn't report an error Given a WP install And I run `wp plugin delete akismet` When I run `wp plugin install health-check --version=1.5.0` Then STDOUT should not be empty When I run `wp plugin install wordpress-importer --version=0.5` Then STDOUT should not be empty When I run `sed -i.bak 's/Version: .*/Version: 10000/' $(wp plugin path health-check)` Then STDOUT should be empty And the return code should be 0 When I try `wp plugin update --all` Then STDERR should contain: """ Warning: health-check: version higher than expected. """ And STDOUT should not contain: """ Error: Only updated 1 of 1 plugins. """ And STDOUT should contain: """ Success: Updated 1 of 1 plugins (1 skipped). """	7.69 KB	2025-09-06 07:07
📄 plugin.feature Feature: Manage WordPress plugins Scenario: Create, activate and check plugin status Given a WP install And I run `wp plugin path` And save STDOUT as {PLUGIN_DIR} When I run `wp plugin scaffold --skip-tests plugin1` Then STDOUT should not be empty And the {PLUGIN_DIR}/plugin1/plugin1.php file should exist And the {PLUGIN_DIR}/zombieland/phpunit.xml.dist file should not exist When I run `wp plugin path plugin1` Then STDOUT should be: """ {PLUGIN_DIR}/plugin1/plugin1.php """ When I run `wp plugin path plugin1 --dir` Then STDOUT should be: """ {PLUGIN_DIR}/plugin1 """ When I run `wp plugin scaffold Zombieland` Then STDOUT should not be empty And the {PLUGIN_DIR}/Zombieland/Zombieland.php file should exist And the {PLUGIN_DIR}/Zombieland/phpunit.xml.dist file should exist # Ensure case sensitivity When I try `wp plugin status zombieLand` Then STDERR should contain: """ The 'zombieLand' plugin could not be found. """ And STDOUT should be empty And the return code should be 1 # Check that the inner-plugin is not picked up When I run `mv {PLUGIN_DIR}/plugin1 {PLUGIN_DIR}/Zombieland/` And I run `wp plugin status Zombieland` Then STDOUT should contain: """ Plugin Zombieland details: Name: Zombieland Status: Inactive Version: 0.1.0 Author: YOUR NAME HERE Description: PLUGIN DESCRIPTION HERE """ When I run `wp plugin activate Zombieland` Then STDOUT should not be empty When I run `wp plugin status Zombieland` Then STDOUT should contain: """ Status: Active """ When I run `wp plugin status` Then STDOUT should not be empty When I run `wp plugin list --fields=name,status,update,version,update_version,auto_update` Then STDOUT should be a table containing rows: \| name \| status \| update \| version \| update_version \| auto_update \| \| Zombieland \| active \| none \| 0.1.0 \| \| off \| When I try `wp plugin uninstall Zombieland` Then STDERR should be: """ Warning: The 'Zombieland' plugin is active. Error: No plugins uninstalled. """ And the return code should be 1 When I run `wp plugin deactivate Zombieland` Then STDOUT should not be empty When I run `wp option get recently_activated` Then STDOUT should contain: """ Zombieland/Zombieland.php """ When I run `wp plugin uninstall Zombieland` Then STDOUT should be: """ Uninstalled and deleted 'Zombieland' plugin. Success: Uninstalled 1 of 1 plugins. """ And the {PLUGIN_DIR}/zombieland file should not exist When I try the previous command again Then STDERR should contain: """ Warning: """ And STDERR should contain: """ Zombieland """ And STDERR should contain: """ Error: No plugins uninstalled. """ And STDOUT should be empty And the return code should be 1 # WordPress Importer currently requires at least WP 5.2. @require-wp-5.2 Scenario: Install a plugin, activate, then force install an older version of the plugin Given a WP install When I run `wp plugin install wordpress-importer --version=0.5 --force` Then STDOUT should not be empty When I run `wp plugin list --name=wordpress-importer --field=update_version` Then STDOUT should not be empty And save STDOUT as {UPDATE_VERSION} When I run `wp plugin list --fields=name,status,update,version,update_version` Then STDOUT should be a table containing rows: \| name \| status \| update \| version \| update_version \| \| wordpress-importer \| inactive \| available \| 0.5 \| {UPDATE_VERSION} \| When I run `wp plugin activate wordpress-importer` Then STDOUT should not be empty When I run `wp plugin install wordpress-importer --version=0.5 --force` Then STDOUT should not be empty When I run `wp plugin list` Then STDOUT should be a table containing rows: \| name \| status \| update \| version \| update_version \| auto_update \| \| wordpress-importer \| active \| available \| 0.5 \| {UPDATE_VERSION} \| off \| When I try `wp plugin update` Then STDERR should be: """ Error: Please specify one or more plugins, or use --all. """ And STDOUT should be empty And the return code should be 1 When I run `wp plugin update --all --format=summary \| grep 'updated successfully from'` Then STDOUT should contain: """ WordPress Importer updated successfully from version 0.5 to version """ When I try `wp plugin update xxx yyy` Then STDERR should contain: """ Warning: The 'xxx' plugin could not be found. """ And STDERR should contain: """ Warning: The 'yyy' plugin could not be found. """ And STDERR should contain: """ Error: No plugins updated (2 failed). """ And the return code should be 1 When I run `wp plugin install wordpress-importer --version=0.5 --force` Then STDOUT should not be empty When I try `wp plugin update xxx wordpress-importer yyy` Then STDERR should contain: """ Warning: The 'xxx' plugin could not be found. """ And STDERR should contain: """ Warning: The 'yyy' plugin could not be found. """ And STDERR should contain: """ Error: Only updated 1 of 3 plugins (2 failed). """ And the return code should be 1 Scenario: Activate a network-only plugin on single site Given a WP install And a wp-content/plugins/network-only.php file: """ <?php // Plugin Name: Example Plugin // Network: true """ When I run `wp plugin activate network-only` Then STDOUT should be: """ Plugin 'network-only' activated. Success: Activated 1 of 1 plugins. """ When I run `wp plugin status network-only` Then STDOUT should contain: """ Status: Active """ Scenario: Activate a network-only plugin on multisite Given a WP multisite install And a wp-content/plugins/network-only.php file: """ <?php // Plugin Name: Example Plugin // Network: true """ When I run `wp plugin activate network-only` Then STDOUT should be: """ Plugin 'network-only' network activated. Success: Activated 1 of 1 plugins. """ When I run `wp plugin status network-only` Then STDOUT should contain: """ Status: Network Active """ Scenario: Network activate a plugin Given a WP multisite install When I run `wp plugin activate akismet` Then STDOUT should be: """ Plugin 'akismet' activated. Success: Activated 1 of 1 plugins. """ When I run `wp plugin list --fields=name,status,file` Then STDOUT should be a table containing rows: \| name \| status \| file \| \| akismet \| active \| akismet/akismet.php \| When I try `wp plugin activate akismet` Then STDERR should contain: """ Warning: Plugin 'akismet' is already active. """ And STDOUT should be: """ Success: Plugin already activated. """ And the return code should be 0 When I run `wp plugin activate akismet --network` Then STDOUT should be: """ Plugin 'akismet' network activated. Success: Network activated 1 of 1 plugins. """ When I try `wp plugin activate akismet --network` Then STDERR should be: """ Warning: Plugin 'akismet' is already network active. """ And STDOUT should be: """ Success: Plugin already network activated. """ And the return code should be 0 When I try `wp plugin deactivate akismet` Then STDERR should be: """ Warning: Plugin 'akismet' is network active and must be deactivated with --network flag. Error: No plugins deactivated. """ And STDOUT should be empty And the return code should be 1 When I run `wp plugin deactivate akismet --network` Then STDOUT should be: """ Plugin 'akismet' network deactivated. Success: Network deactivated 1 of 1 plugins. """ And the return code should be 0 When I try `wp plugin deactivate akismet` Then STDERR should be: """ Warning: Plugin 'akismet' isn't active. """ And STDOUT should be: """ Success: Plugin already deactivated. """ And the return code should be 0 Scenario: List plugins Given a WP install When I run `wp plugin activate akismet hello` Then STDOUT should not be empty When I run `wp plugin list --status=inactive --field=name` Then STDOUT should be empty When I run `wp plugin list --status=active --fields=name,status,file` Then STDOUT should be a table containing rows: \| name \| status \| file \| \| akismet \| active \| akismet/akismet.php \| When I run `wp plugin list --status=active --field=author` Then STDOUT should contain: """ Automattic """ When I run `wp eval 'echo get_site_transient("update_plugins")->last_checked;'` Then save STDOUT as {LAST_UPDATED} When I run `wp plugin list --skip-update-check` Then STDOUT should not be empty When I run `wp eval 'echo get_site_transient("update_plugins")->last_checked;'` Then STDOUT should be: """ {LAST_UPDATED} """ When I run `wp plugin list` Then STDOUT should not be empty When I run `wp eval 'echo get_site_transient("update_plugins")->last_checked;'` Then STDOUT should not contain: """ {LAST_UPDATED} """ Scenario: List plugin by multiple statuses Given a WP multisite install And a wp-content/plugins/network-only.php file: """ <?php // Plugin Name: Example Plugin // Network: true """ When I run `wp plugin activate akismet hello` Then STDOUT should not be empty When I run `wp plugin install wordpress-importer --ignore-requirements` Then STDOUT should not be empty When I run `wp plugin activate network-only` Then STDOUT should not be empty When I run `wp plugin list --status=active-network,inactive --fields=name,status,file` Then STDOUT should be a table containing rows: \| name \| status \| file \| \| network-only \| active-network \| network-only.php \| \| wordpress-importer \| inactive \| wordpress-importer/wordpress-importer.php \| When I run `wp plugin list --status=active,inactive --fields=name,status,file` Then STDOUT should be a table containing rows: \| name \| status \| file \| \| akismet \| active \| akismet/akismet.php \| \| wordpress-importer \| inactive \| wordpress-importer/wordpress-importer.php \| @require-wp-5.2 Scenario: Flag `--skip-update-check` skips update check when running `wp plugin list` Given a WP install When I run `wp plugin install wordpress-importer --version=0.2` Then STDOUT should contain: """ Plugin installed successfully. """ When I run `wp plugin list --fields=name,status,update --status=inactive` Then STDOUT should be a table containing rows: \| name \| status \| update \| \| wordpress-importer \| inactive \| available \| When I run `wp transient delete update_plugins --network` Then STDOUT should be: """ Success: Transient deleted. """ When I run `wp plugin list --fields=name,status,update --status=inactive --skip-update-check` Then STDOUT should be a table containing rows: \| name \| status \| update \| \| wordpress-importer \| inactive \| none \| # WordPress Importer requires WP 5.2. @require-wp-5.2 Scenario: Install a plugin when directory doesn't yet exist Given a WP install When I run `rm -rf wp-content/plugins` And I run `if test -d wp-content/plugins; then echo "fail"; fi` Then STDOUT should be empty When I run `wp plugin install wordpress-importer --activate` Then STDOUT should not be empty When I run `wp plugin list --status=active --fields=name,status,file` Then STDOUT should be a table containing rows: \| name \| status \| file \| \| wordpress-importer \| active \| wordpress-importer/wordpress-importer.php \| Scenario: Plugin name with HTML entities Given a WP install When I run `wp plugin install debug-bar-list-dependencies` Then STDOUT should contain: """ Installing Debug Bar List Script & Style Dependencies """ # Not running for SQLite because it involves another must-use plugin and a drop-in. @require-mysql Scenario: Enable and disable all plugins Given a WP install When I run `wp plugin activate --all` Then STDOUT should contain: """ Plugin 'akismet' activated. Plugin 'hello' activated. Success: Activated 2 of 2 plugins. """ When I run `wp plugin activate --all` Then STDOUT should be: """ Success: Plugins already activated. """ When I run `wp plugin list --field=status` Then STDOUT should be: """ active active must-use must-use """ When I run `wp plugin deactivate --all` Then STDOUT should be: """ Plugin 'akismet' deactivated. Plugin 'hello' deactivated. Success: Deactivated 2 of 2 plugins. """ When I run `wp plugin deactivate --all` Then STDOUT should be: """ Success: Plugins already deactivated. """ When I run `wp plugin list --field=status` Then STDOUT should be: """ inactive inactive must-use must-use """ # WordPress Importer requires WP 5.2. @require-wp-5.2 Scenario: Deactivate and uninstall a plugin, part one Given a WP install And these installed and active plugins: """ wordpress-importer """ When I run `wp plugin deactivate wordpress-importer --uninstall` Then STDOUT should be: """ Plugin 'wordpress-importer' deactivated. Uninstalling 'wordpress-importer'... Uninstalled and deleted 'wordpress-importer' plugin. Success: Deactivated 1 of 1 plugins. """ When I try `wp plugin get wordpress-importer` Then STDERR should be: """ Error: The 'wordpress-importer' plugin could not be found. """ And STDOUT should be empty And the return code should be 1 # WordPress Importer requires WP 5.2. @require-wp-5.2 Scenario: Deactivate and uninstall a plugin, part two Given a WP install And these installed and active plugins: """ wordpress-importer """ When I run `wp plugin uninstall wordpress-importer --deactivate` Then STDOUT should be: """ Deactivating 'wordpress-importer'... Plugin 'wordpress-importer' deactivated. Uninstalled and deleted 'wordpress-importer' plugin. Success: Uninstalled 1 of 1 plugins. """ When I try `wp plugin get wordpress-importer` Then STDERR should be: """ Error: The 'wordpress-importer' plugin could not be found. """ And STDOUT should be empty And the return code should be 1 Scenario: Uninstall a plugin without deleting Given a WP install When I run `wp plugin install akismet --version=2.5.7 --force` Then STDOUT should not be empty When I run `wp plugin uninstall akismet --skip-delete` Then STDOUT should be: """ Ran uninstall procedure for 'akismet' plugin without deleting. Success: Uninstalled 1 of 1 plugins. """ Scenario: Two plugins, one directory Given a WP install And a wp-content/plugins/handbook/handbook.php file: """ <?php /** * Plugin Name: Handbook * Description: Features for a handbook, complete with glossary and table of contents * Author: Nacin / """ And a wp-content/plugins/handbook/functionality-for-pages.php file: """ <?php /* * Plugin Name: Handbook Functionality for Pages * Description: Adds handbook-like table of contents to all Pages for a site. Covers Table of Contents and the "watch this page" widget * Author: Nacin / """ When I run `wp plugin list --fields=name,status,file` Then STDOUT should be a table containing rows: \| name \| status \| file \| \| handbook/handbook \| inactive \| handbook/handbook.php \| \| handbook/functionality-for-pages \| inactive \| handbook/functionality-for-pages.php \| When I run `wp plugin activate handbook/functionality-for-pages` Then STDOUT should not be empty When I run `wp plugin list --fields=name,status,file` Then STDOUT should be a table containing rows: \| name \| status \| file \| \| handbook/handbook \| inactive \| handbook/handbook.php \| \| handbook/functionality-for-pages \| active \| handbook/functionality-for-pages.php \| Scenario: Install a plugin, then update to a specific version of that plugin Given a WP install When I run `wp plugin install akismet --version=2.5.7 --force` Then STDOUT should not be empty When I run `wp plugin update akismet --version=2.6.0` Then STDOUT should not be empty When I run `wp plugin list --fields=name,version,file` Then STDOUT should be a table containing rows: \| name \| version \| file \| \| akismet \| 2.6.0 \| akismet/akismet.php \| Scenario: Ignore empty slugs Given a WP install When I try `wp plugin install ''` Then STDERR should contain: """ Warning: Ignoring ambiguous empty slug value. """ And STDOUT should not contain: """ Plugin installed successfully """ And the return code should be 0 # Akismet currently requires WordPress 5.8, so there's a warning because of it. @require-wp-5.8 Scenario: Plugin hidden by "all_plugins" filter Given a WP install And these installed and active plugins: """ hello-dolly site-secrets """ And a wp-content/mu-plugins/hide-us-plugin.php file: """ <?php /* * Plugin Name: Hide Site Secrets on Production * Description: Hides the Site Secrets plugin on production sites * Author: WP-CLI tests / add_filter( 'all_plugins', function( $all_plugins ) { unset( $all_plugins['site-secrets/site-secrets.php'] ); return $all_plugins; } ); """ When I run `wp plugin list --fields=name` Then STDOUT should not contain: """ site-secrets """ Scenario: Show dropins plugin list Given a WP install And a wp-content/db-error.php file: """ <?php """ When I run `wp plugin list --status=active` Then STDOUT should not contain: """ db-error.php """ When I run `wp plugin list --status=dropin --fields=name,title,description,file` Then STDOUT should be a table containing rows: \| name \| title \| description \| file \| \| db-error.php \| \| Custom database error message. \| db-error.php \| @require-wp-4.0 Scenario: Validate installed plugin's version. Given a WP installation And I run `wp plugin uninstall --all` And I run `wp plugin install hello-dolly` And a wp-content/mu-plugins/test-plugin-update.php file: """ <?php /* * Plugin Name: Test Plugin Update * Description: Fakes installed plugin's data to verify plugin version mismatch * Author: WP-CLI tests / add_filter( 'site_transient_update_plugins', function( $value ) { if ( ! is_object( $value ) ) { return $value; } unset( $value->response['hello-dolly/hello.php'] ); $value->no_update['hello-dolly/hello.php']->new_version = '1.5'; return $value; } ); ?> """ When I run `wp plugin list --name=hello-dolly --field=version` Then save STDOUT as {PLUGIN_VERSION} When I run `wp plugin list --name=hello-dolly --field=update_version` Then save STDOUT as {UPDATE_VERSION} When I run `wp plugin list` Then STDOUT should be a table containing rows: \| name \| status \| update \| version \| update_version \| auto_update \| \| hello-dolly \| inactive \| version higher than expected \| {PLUGIN_VERSION} \| {UPDATE_VERSION} \| off \| When I try `wp plugin update --all` Then STDERR should be: """ Warning: hello-dolly: version higher than expected. Error: No plugins updated. """ When I try `wp plugin update hello-dolly` Then STDERR should be: """ Warning: hello-dolly: version higher than expected. Error: No plugins updated. """ Scenario: Only valid status filters are accepted when listing plugins Given a WP install When I run `wp plugin list` Then STDERR should be empty When I run `wp plugin list --status=active` Then STDERR should be empty When I try `wp plugin list --status=invalid-status` Then STDERR should be: """ Error: Parameter errors: Invalid value specified for 'status' (Filter the output by plugin status.) """ Scenario: Listing mu-plugins should include name and title Given a WP install And a wp-content/mu-plugins/test-mu.php file: """ <?php // Plugin Name: Test mu-plugin // Description: Test mu-plugin description """ When I run `wp plugin list --fields=name,title` Then STDOUT should be a table containing rows: \| name \| title \| \| test-mu \| Test mu-plugin \| When I run `wp plugin list --fields=name,title,description` Then STDOUT should be a table containing rows: \| name \| title \| description \| \| test-mu \| Test mu-plugin \| Test mu-plugin description \| @require-wp-5.5 Scenario: Listing plugins should include name and auto_update Given a WP install When I run `wp plugin list --fields=name,auto_update` Then STDOUT should be a table containing rows: \| name \| auto_update \| \| hello \| off \| When I run `wp plugin auto-updates enable hello` And I try `wp plugin list --fields=name,auto_update` Then STDOUT should be a table containing rows: \| name \| auto_update \| \| hello \| on \| Scenario: Listing plugins should include tested_up_to from the 'tested up to' header Given a WP install And a wp-content/plugins/foo/foo.php file: """ <?php /* * Plugin Name: Foo * Description: A plugin for foo * Author: Matt / """ And a wp-content/plugins/foo/readme.txt file: """ === Foo === Contributors: matt Donate link: https://example.com/ Tags: tag1, tag2 Requires at least: 4.7 Tested up to: 3.4 Stable tag: 4.3 Requires PHP: 7.0 License: GPLv2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html """ And I run `wp plugin activate foo` When I run `wp plugin list --fields=name,status,update,version,update_version,auto_update` Then STDOUT should be a table containing rows: \| name \| status \| update \| version \| update_version \| auto_update \| \| foo \| active \| none \| \| \| off \| When I run `wp plugin list --fields=name,tested_up_to` Then STDOUT should be a table containing rows: \| name \| tested_up_to \| \| foo \| 3.4 \| When I run `wp plugin list --name=foo --field=tested_up_to` Then STDOUT should be: """ 3.4 """ Scenario: Listing plugins should include tested_up_to from the 'tested' header Given a WP install And a wp-content/plugins/foo/foo.php file: """ <?php /* * Plugin Name: Foo * Description: A plugin for foo * Author: Matt / """ And a wp-content/plugins/foo/readme.txt file: """ === Foo === Tested: 5.5 Contributors: matt Donate link: https://example.com/ Tags: tag1, tag2 Requires at least: 4.7 Stable tag: 4.3 Requires PHP: 7.0 License: GPLv2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html """ And I run `wp plugin activate foo` When I run `wp plugin list --fields=name,status,update,version,update_version,auto_update` Then STDOUT should be a table containing rows: \| name \| status \| update \| version \| update_version \| auto_update \| \| foo \| active \| none \| \| \| off \| When I run `wp plugin list --fields=name,tested_up_to` Then STDOUT should be a table containing rows: \| name \| tested_up_to \| \| foo \| 5.5 \| When I run `wp plugin list --name=foo --field=tested_up_to` Then STDOUT should be: """ 5.5 """ @require-wp-4.0 Scenario: Show plugin update as unavailable if it doesn't meet WordPress requirements Given a WP install And a wp-content/plugins/example/example.php file: """ <?php /* * Plugin Name: Example Plugin * Version: 1.0.0 * Requires at least: 3.7 * Tested up to: 6.7 """ And that HTTP requests to https://api.wordpress.org/plugins/update-check/1.1/ will respond with: """ HTTP/1.1 200 OK { "plugins": [], "translations": [], "no_update": { "example/example.php": { "id": "w.org/plugins/example", "slug": "example", "plugin": "example/example.php", "new_version": "2.0.0", "requires": "100", "requires_php": "7.2", "requires_plugins": [], "compatibility": [] } } } """ When I run `wp plugin list` Then STDOUT should be a table containing rows: \| name \| status \| update \| version \| update_version \| auto_update \| requires \| requires_php \| \| example \| inactive \| unavailable \| 1.0.0 \| 2.0.0 \| off \| 100 \| 7.2 \| When I try `wp plugin update example` Then STDERR should contain: """ Warning: example: This update requires WordPress version 100 """ @require-wp-4.0 Scenario: Show plugin update as unavailable if it doesn't meet PHP requirements Given a WP install And a wp-content/plugins/example/example.php file: """ <?php /** * Plugin Name: Example Plugin * Version: 1.0.0 * Requires at least: 3.7 * Tested up to: 6.7 """ And that HTTP requests to https://api.wordpress.org/plugins/update-check/1.1/ will respond with: """ HTTP/1.1 200 OK { "plugins": { "example/example.php": { "id": "w.org/plugins/example", "slug": "example", "plugin": "example/example.php", "new_version": "2.0.0", "requires": "3.7", "tested": "6.6", "requires_php": "100", "requires_plugins": [], "compatibility": [] } }, "translations": [], "no_update": [] } """ When I run `wp plugin list` Then STDOUT should be a table containing rows: \| name \| status \| update \| version \| update_version \| auto_update \| requires \| requires_php \| \| example \| inactive \| unavailable \| 1.0.0 \| 2.0.0 \| off \| 3.7 \| 100 \| When I try `wp plugin update example` Then STDERR should contain: """ Warning: example: This update requires PHP version 100 """	28.4 KB	2025-09-06 07:07
📄 theme-auto-update-status.feature Feature: Show the status of auto-updates for WordPress themes Background: Given a WP install And I run `wp theme delete --all --force` And I run `wp theme install twentysixteen` And I run `wp theme install twentyseventeen` And I run `wp theme install twentynineteen` @require-wp-5.5 Scenario: Show an error if required params are missing When I try `wp theme auto-updates status` Then STDOUT should be empty And STDERR should contain: """ Error: Please specify one or more themes, or use --all. """ @require-wp-5.5 Scenario: Show the status of auto-updates of a single theme When I run `wp theme auto-updates status twentysixteen` Then STDOUT should be a table containing rows: \| name \| status \| \| twentysixteen \| disabled \| And the return code should be 0 @require-wp-5.5 Scenario: Show the status of auto-updates multiple themes When I run `wp theme auto-updates status twentyseventeen twentysixteen` Then STDOUT should be a table containing rows: \| name \| status \| \| twentyseventeen \| disabled \| \| twentysixteen \| disabled \| And the return code should be 0 @require-wp-5.5 Scenario: Show the status of auto-updates all installed themes When I run `wp theme auto-updates status --all` Then STDOUT should be a table containing rows: \| name \| status \| \| twentynineteen \| disabled \| \| twentyseventeen \| disabled \| \| twentysixteen \| disabled \| And the return code should be 0 When I run `wp theme auto-updates enable --all` And I run `wp theme auto-updates status --all` Then STDOUT should be a table containing rows: \| name \| status \| \| twentynineteen \| enabled \| \| twentyseventeen \| enabled \| \| twentysixteen \| enabled \| And the return code should be 0 @require-wp-5.5 Scenario: The status can be filtered to only show enabled or disabled themes Given I run `wp theme auto-updates enable twentysixteen` When I run `wp theme auto-updates status --all` Then STDOUT should be a table containing rows: \| name \| status \| \| twentynineteen \| disabled \| \| twentyseventeen \| disabled \| \| twentysixteen \| enabled \| And the return code should be 0 When I run `wp theme auto-updates status --all --enabled-only` Then STDOUT should be a table containing rows: \| name \| status \| \| twentysixteen \| enabled \| And the return code should be 0 When I run `wp theme auto-updates status --all --disabled-only` Then STDOUT should be a table containing rows: \| name \| status \| \| twentynineteen \| disabled \| \| twentyseventeen \| disabled \| And the return code should be 0 When I try `wp theme auto-updates status --all --enabled-only --disabled-only` Then STDOUT should be empty And STDERR should contain: """ Error: --enabled-only and --disabled-only are mutually exclusive and cannot be used at the same time. """ @require-wp-5.5 Scenario: The fields can be shown individually Given I run `wp theme auto-updates enable twentysixteen` When I run `wp theme auto-updates status --all --disabled-only --field=name` Then STDOUT should be: """ twentynineteen twentyseventeen """ When I run `wp theme auto-updates status twentysixteen --field=status` Then STDOUT should be: """ enabled """ @require-wp-5.5 Scenario: Formatting options work When I run `wp theme auto-updates status --all --format=json` Then STDOUT should be: """ [{"name":"twentynineteen","status":"disabled"},{"name":"twentyseventeen","status":"disabled"},{"name":"twentysixteen","status":"disabled"}] """ When I run `wp theme auto-updates status --all --format=csv` Then STDOUT should be: """ name,status twentynineteen,disabled twentyseventeen,disabled twentysixteen,disabled """	4.02 KB	2025-05-25 12:40
📄 theme-auto-updates-disable.feature Feature: Disable auto-updates for WordPress themes Background: Given a WP install And I run `wp theme delete --all --force` And I run `wp theme install twentysixteen` And I run `wp theme install twentyseventeen` And I run `wp theme install twentynineteen` And I try `wp theme auto-updates enable --all` @require-wp-5.5 Scenario: Show an error if required params are missing When I try `wp theme auto-updates disable` Then STDOUT should be empty And STDERR should contain: """ Error: Please specify one or more themes, or use --all. """ @require-wp-5.5 Scenario: Disable auto-updates for a single theme When I run `wp theme auto-updates disable twentysixteen` Then STDOUT should be: """ Success: Disabled 1 of 1 theme auto-updates. """ And the return code should be 0 @require-wp-5.5 Scenario: Disable auto-updates for multiple themes When I run `wp theme auto-updates disable twentysixteen twentyseventeen` Then STDOUT should be: """ Success: Disabled 2 of 2 theme auto-updates. """ And the return code should be 0 @require-wp-5.5 Scenario: Disable auto-updates for all themes When I run `wp theme auto-updates disable --all` Then STDOUT should be: """ Success: Disabled 3 of 3 theme auto-updates. """ And the return code should be 0 @require-wp-5.5 Scenario: Disable auto-updates for already disabled themes When I run `wp theme auto-updates disable twentysixteen` And I try `wp theme auto-updates disable --all` Then STDERR should contain: """ Warning: Auto-updates already disabled for theme twentysixteen. """ And STDERR should contain: """ Error: Only disabled 2 of 3 theme auto-updates. """ @require-wp-5.5 Scenario: Filter when enabling auto-updates for already disabled themes When I run `wp theme auto-updates disable twentysixteen` And I run `wp theme auto-updates disable --all --enabled-only` Then STDOUT should be: """ Success: Disabled 2 of 2 theme auto-updates. """ And the return code should be 0 @require-wp-5.5 Scenario: Filter when enabling auto-updates for already disabled selection of themes When I run `wp theme auto-updates disable twentysixteen` And I run `wp theme auto-updates disable twentysixteen twentyseventeen --enabled-only` Then STDOUT should be: """ Success: Disabled 1 of 1 theme auto-updates. """ And the return code should be 0 @require-wp-5.5 Scenario: Filtering everything away produces an error When I run `wp theme auto-updates disable twentysixteen` And I try `wp theme auto-updates disable twentysixteen --enabled-only` Then STDERR should be: """ Error: No themes provided to disable auto-updates for. """	2.82 KB	2025-05-25 12:40
📄 theme-auto-updates-enable.feature Feature: Enable auto-updates for WordPress themes Background: Given a WP install And I run `wp theme delete --all --force` And I run `wp theme install twentysixteen` And I run `wp theme install twentyseventeen` And I run `wp theme install twentynineteen` And I try `wp theme auto-updates disable --all` @require-wp-5.5 Scenario: Show an error if required params are missing When I try `wp theme auto-updates enable` Then STDOUT should be empty And STDERR should contain: """ Error: Please specify one or more themes, or use --all. """ @require-wp-5.5 Scenario: Enable auto-updates for a single theme When I run `wp theme auto-updates enable twentysixteen` Then STDOUT should be: """ Success: Enabled 1 of 1 theme auto-updates. """ And the return code should be 0 @require-wp-5.5 Scenario: Enable auto-updates for multiple themes When I run `wp theme auto-updates enable twentysixteen twentyseventeen` Then STDOUT should be: """ Success: Enabled 2 of 2 theme auto-updates. """ And the return code should be 0 @require-wp-5.5 Scenario: Enable auto-updates for all themes When I run `wp theme auto-updates enable --all` Then STDOUT should be: """ Success: Enabled 3 of 3 theme auto-updates. """ And the return code should be 0 @require-wp-5.5 Scenario: Enable auto-updates for already enabled themes When I run `wp theme auto-updates enable twentysixteen` And I try `wp theme auto-updates enable --all` Then STDERR should contain: """ Warning: Auto-updates already enabled for theme twentysixteen. """ And STDERR should contain: """ Error: Only enabled 2 of 3 theme auto-updates. """ @require-wp-5.5 Scenario: Filter when enabling auto-updates for already enabled themes When I run `wp theme auto-updates enable twentysixteen` And I run `wp theme auto-updates enable --all --disabled-only` Then STDOUT should be: """ Success: Enabled 2 of 2 theme auto-updates. """ And the return code should be 0 @require-wp-5.5 Scenario: Filter when enabling auto-updates for already enabled selection of themes When I run `wp theme auto-updates enable twentysixteen` And I run `wp theme auto-updates enable twentysixteen twentyseventeen --disabled-only` Then STDOUT should be: """ Success: Enabled 1 of 1 theme auto-updates. """ And the return code should be 0 @require-wp-5.5 Scenario: Filtering everything away produces an error When I run `wp theme auto-updates enable twentysixteen` And I try `wp theme auto-updates enable twentysixteen --disabled-only` Then STDERR should be: """ Error: No themes provided to enable auto-updates for. """	2.8 KB	2025-05-25 12:40
📄 theme-delete.feature Feature: Delete WordPress themes Background: Given a WP install And I run `wp theme delete --all --force` And I run `wp theme install twentytwelve` And I run `wp theme install twentyeleven --activate` Scenario: Delete an installed theme When I run `wp theme delete twentytwelve` Then STDOUT should be: """ Deleted 'twentytwelve' theme. Success: Deleted 1 of 1 themes. """ And the return code should be 0 Scenario: Delete an active theme When I run `wp theme activate twentytwelve` Then STDOUT should not be empty When I try `wp theme delete twentytwelve` Then STDERR should be: """ Warning: Can't delete the currently active theme: twentytwelve Error: No themes deleted. """ When I try `wp theme delete twentytwelve --force` Then STDOUT should contain: """ Deleted 'twentytwelve' theme. """ Scenario: Delete all installed themes When I run `wp theme list --status=active --field=name --porcelain` Then save STDOUT as {ACTIVE_THEME} When I try `wp theme delete --all` Then STDOUT should contain: """ Success: Deleted """ And STDERR should be empty When I run `wp theme delete --all --force` Then STDOUT should be: """ Deleted '{ACTIVE_THEME}' theme. Success: Deleted 1 of 1 themes. """ When I try the previous command again Then STDOUT should be: """ Success: No themes deleted. """ Scenario: Delete all installed themes when active theme has a parent Given a WP install And I run `wp theme install moina-blog --activate` When I run `wp theme list --field=name` Then STDOUT should contain: """ moina-blog moina """ When I try `wp theme delete moina-blog` Then STDERR should contain: """ Can't delete the currently active theme """ And STDERR should contain: """ Error: No themes deleted. """ When I try `wp theme delete moina` Then STDERR should contain: """ Can't delete the parent of the currently active theme """ And STDERR should contain: """ Error: No themes deleted. """ When I run `wp theme delete --all` Then STDOUT should contain: """ Success: Deleted """ When I run `wp theme list --field=name` Then STDOUT should contain: """ moina-blog moina """ When I run `wp theme delete --all --force` Then STDOUT should contain: """ Success: Deleted """ When I run `wp theme list --field=name` Then STDOUT should be empty Scenario: Attempting to delete a theme that doesn't exist When I run `wp theme delete twentytwelve` Then STDOUT should not be empty When I try the previous command again Then STDOUT should be: """ Success: Theme already deleted. """ And STDERR should be: """ Warning: The 'twentytwelve' theme could not be found. """ And the return code should be 0	3.03 KB	2025-09-06 07:07
📄 theme-install.feature Feature: Install WordPress themes Background: Given a WP install And I run `wp theme delete --all --force` Scenario: Return code is 1 when one or more theme installations fail When I try `wp theme install twentytwelve twentytwelve-not-a-theme` Then STDERR should contain: """ Warning: """ And STDERR should contain: """ twentytwelve-not-a-theme """ And STDERR should contain: """ Error: Only installed 1 of 2 themes. """ And STDOUT should contain: """ Installing Twenty Twelve """ And STDOUT should contain: """ Theme installed successfully. """ And the return code should be 1 When I try `wp theme install twentytwelve` Then STDOUT should be: """ Success: Theme already installed. """ And STDERR should be: """ Warning: twentytwelve: Theme already installed. """ And the return code should be 0 When I try `wp theme install twentytwelve-not-a-theme` Then STDERR should contain: """ Warning: """ And STDERR should contain: """ twentytwelve-not-a-theme """ And STDERR should contain: """ Error: No themes installed. """ And STDOUT should be empty And the return code should be 1 Scenario: Ensure automatic parent theme installation uses http cacher Given a WP install And an empty cache When I run `wp theme install moina` Then STDOUT should contain: """ Success: Installed 1 of 1 themes. """ And STDOUT should not contain: """ Using cached file """ When I run `wp theme uninstall moina` Then STDOUT should contain: """ Success: Deleted 1 of 1 themes. """ When I run `wp theme install moina-blog` Then STDOUT should contain: """ Success: Installed 1 of 1 themes. """ And STDOUT should contain: """ This theme requires a parent theme. """ And STDOUT should contain: """ Using cached file """ Scenario: Verify installed theme activation When I run `wp theme install twentytwelve` Then STDOUT should not be empty When I try `wp theme install twentytwelve --activate` Then STDERR should contain: """ Warning: twentytwelve: Theme already installed. """ And STDOUT should contain: """ Activating 'twentytwelve'... Success: Switched to 'Twenty Twelve' theme. Success: Theme already installed. """ Scenario: Installation of multiple themes with activate When I try `wp theme install twentytwelve twentyeleven --activate` Then STDERR should contain: """ Warning: Only this single theme will be activated: twentyeleven """ When I run `wp theme list --field=name` Then STDOUT should contain: """ twentyeleven twentytwelve """ When I run `wp theme list --field=name --status=active` Then STDOUT should contain: """ twentyeleven """ @require-php-7 Scenario: Can't install theme that requires a newer version of WordPress Given a WP install When I run `wp core download --version=6.4 --force` And I run `rm -r wp-content/themes/*` And I try `wp theme install twentytwentyfive` Then STDERR should contain: """ Warning: twentytwentyfive: This theme does not work with your version of WordPress. """ And STDERR should contain: """ Error: No themes installed. """ @less-than-php-7.4 @require-wp-5.6 Scenario: Can't install theme that requires a newer version of PHP Given a WP install And I try `wp theme install oceanwp` Then STDERR should contain: """ Warning: oceanwp: This theme does not work with your version of PHP. """ And STDERR should contain: """ Error: No themes installed. """	3.89 KB	2025-09-06 07:07
📄 theme-mod-list.feature Feature: Manage WordPress theme mods list Background: Given a WP install And I run `wp theme mod set key_a value_a` And I run `wp theme mod set key_b value_b` Scenario: Getting theme mods When I run `wp theme mod list` Then STDOUT should be a table containing rows: \| key \| value \| When I run `wp theme mod list --field=key` Then STDOUT should be: """ key_a key_b """ When I run `wp theme mod list --field=value` Then STDOUT should be: """ value_a value_b """ When I run `wp theme mod list --format=json` Then STDOUT should be: """ [{"key":"key_a","value":"value_a"},{"key":"key_b","value":"value_b"}] """ When I run `wp theme mod list --format=csv` Then STDOUT should be: """ key,value key_a,value_a key_b,value_b """ When I run `wp theme mod list --format=yaml` Then STDOUT should be: """ --- - key: key_a value: value_a - key: key_b value: value_b """	1.07 KB	2025-09-06 07:07
📄 theme-mod.feature Feature: Manage WordPress theme mods Scenario: Getting theme mods Given a WP install When I run `wp theme mod get --all` Then STDOUT should be a table containing rows: \| key \| value \| When I try `wp theme mod get` Then STDERR should contain: """ You must specify at least one mod or use --all. """ And STDOUT should be empty And the return code should be 1 When I run `wp theme mod set background_color 123456` And I run `wp theme mod get --all` Then STDOUT should be a table containing rows: \| key \| value \| \| background_color \| 123456 \| When I run `wp theme mod get background_color --field=value` Then STDOUT should be: """ 123456 """ When I run `wp theme mod set background_color 123456` And I run `wp theme mod get background_color header_textcolor` Then STDOUT should be a table containing rows: \| key \| value \| \| background_color \| 123456 \| \| header_textcolor \| \| Scenario: Setting theme mods Given a WP install When I run `wp theme mod set background_color 123456` Then STDOUT should be: """ Success: Theme mod background_color set to 123456. """ Scenario: Removing theme mods Given a WP install When I run `wp theme mod remove --all` Then STDOUT should be: """ Success: Theme mods removed. """ When I try `wp theme mod remove` Then STDERR should contain: """ You must specify at least one mod or use --all. """ And STDOUT should be empty And the return code should be 1 When I run `wp theme mod remove background_color` Then STDOUT should be: """ Success: 1 mod removed. """ When I run `wp theme mod remove background_color header_textcolor` Then STDOUT should be: """ Success: 2 mods removed. """	1.91 KB	2025-05-25 12:40
📄 theme-update.feature Feature: Update WordPress themes Scenario: Updating a theme with no version in the WordPress.org directory shouldn't delete the original theme Given a WP install When I run `wp scaffold underscores wpclitesttheme` Then STDOUT should contain: """ Success: Created theme """ And the wp-content/themes/wpclitesttheme directory should exist When I try `wp theme update wpclitesttheme --version=100.0.0` Then STDERR should contain: """ Error: No themes installed """ And the wp-content/themes/wpclitesttheme directory should exist Scenario: Install a theme, then update to a specific version of that theme Given a WP install And I run `wp theme delete --all --force` When I run `wp theme install twentytwelve --version=3.0` Then STDOUT should not be empty When I run `wp theme update twentytwelve --version=4.0` Then STDOUT should not be empty When I run `wp theme list --fields=name,version` Then STDOUT should be a table containing rows: \| name \| version \| \| twentytwelve \| 4.0 \| @require-wp-4.5 Scenario: Not giving a slug on update should throw an error unless --all given Given a WP install And I run `wp theme path` And save STDOUT as {THEME_DIR} And an empty {THEME_DIR} directory # No themes installed. Don't give an error if --all given for BC. When I run `wp theme update --all` Then STDOUT should be: """ Success: No themes installed. """ When I run `wp theme update --version=0.6 --all` Then STDOUT should be: """ Success: No themes installed. """ # One theme installed. Given I run `wp theme install moina --version=1.0.2` When I try `wp theme update` Then the return code should be 1 And STDERR should be: """ Error: Please specify one or more themes, or use --all. """ And STDOUT should be empty When I run `wp theme update --all` Then STDOUT should contain: """ Success: Updated """ When I run the previous command again Then STDOUT should be: """ Success: Theme already updated. """ # Note: if given version then re-installs. When I run `wp theme update --version=1.0.2 --all` Then STDOUT should contain: """ Success: Installed 1 of 1 themes. """ When I run the previous command again Then STDOUT should contain: """ Success: Installed 1 of 1 themes. """ # Two themes installed. Given I run `wp theme install --force twentytwelve --version=1.0` When I run `wp theme update --all` Then STDOUT should contain: """ Success: Updated """ When I run the previous command again # BUG: Message should be in plural. Then STDOUT should be: """ Success: Theme already updated. """ # Using version with all rarely makes sense and should probably error and do nothing. When I try `wp theme update --version=1.0.3 --all` Then the return code should be 1 And STDOUT should contain: """ Success: Installed 1 of 1 themes. """ And STDERR should be: """ Error: Can't find the requested theme's version 1.0.3 in the WordPress.org theme repository (HTTP code 404). """ Scenario: Error when both --minor and --patch are provided Given a WP install When I try `wp theme update --patch --minor --all` Then STDERR should be: """ Error: --minor and --patch cannot be used together. """ And the return code should be 1 Scenario: Update a theme to its latest minor release Given a WP install And I run `wp theme install --force twentytwelve --version=3.0` When I run `wp theme update twentytwelve --minor` Then STDOUT should contain: """ Success: Updated 1 of 1 themes. """ When I run `wp theme get twentytwelve --field=version` Then STDOUT should be: """ 3.9 """ Scenario: Update a theme to its latest patch release Given a WP install And I run `wp theme install --force twentytwelve --version=1.1` When I run `wp theme update twentytwelve --patch` Then STDOUT should contain: """ Success: Updated 1 of 1 themes. """ When I run `wp theme get twentytwelve --field=version` Then STDOUT should be: """ 1.1.1 """	4.35 KB	2025-09-06 07:07
📄 theme.feature Feature: Manage WordPress themes Scenario: Installing and deleting theme Given a WP install And I run `wp theme delete --all --force` And I run `wp theme install twentyeleven --activate` When I run `wp theme install twentytwelve` Then STDOUT should not be empty When I run `wp theme status twentytwelve` Then STDOUT should contain: """ Theme twentytwelve details: Name: Twenty Twelve """ When I run `wp theme path twentytwelve` Then STDOUT should contain: """ /themes/twentytwelve/style.css """ When I run `wp option get stylesheet` Then save STDOUT as {PREVIOUS_THEME} When I run `wp theme activate twentytwelve` Then STDOUT should be: """ Success: Switched to 'Twenty Twelve' theme. """ When I try `wp theme delete twentytwelve` Then STDERR should be: """ Warning: Can't delete the currently active theme: twentytwelve Error: No themes deleted. """ And STDOUT should be empty And the return code should be 1 When I run `wp theme activate {PREVIOUS_THEME}` Then STDOUT should not be empty When I run `wp theme delete twentytwelve` Then STDOUT should not be empty When I try the previous command again Then STDERR should be: """ Warning: The 'twentytwelve' theme could not be found. """ And STDOUT should be: """ Success: Theme already deleted. """ And the return code should be 0 When I run `wp theme list` Then STDOUT should not be empty Scenario: Checking theme status without theme parameter Given a WP install When I run `wp theme install classic --activate` And I run `wp theme list --field=name --status=inactive \| xargs wp theme delete` And I run `wp theme status` Then STDOUT should be: """ 1 installed theme: A classic 1.6 Legend: A = Active """ Scenario: Install a theme, activate, then force install an older version of the theme Given a WP install And I run `wp theme delete --all --force` And I run `wp theme install twentyeleven --activate` When I run `wp theme install twentytwelve --version=1.4` Then STDOUT should not be empty When I run `wp theme list --name=twentytwelve --field=update_version` Then STDOUT should not be empty And save STDOUT as {UPDATE_VERSION} When I run `wp theme list` Then STDOUT should be a table containing rows: \| name \| status \| update \| version \| update_version \| auto_update \| \| twentytwelve \| inactive \| available \| 1.4 \| {UPDATE_VERSION} \| off \| When I run `wp theme activate twentytwelve` Then STDOUT should not be empty # Ensure no other themes interfere with update. When I run `wp theme list --status=inactive --field=name \| xargs wp theme delete` Then STDOUT should contain: """ Success: Deleted """ When I run `wp theme install twentytwelve --version=1.5 --force` Then STDOUT should not be empty When I run `wp theme list` Then STDOUT should be a table containing rows: \| name \| status \| update \| version \| update_version \| auto_update \| \| twentytwelve \| active \| available \| 1.5 \| {UPDATE_VERSION} \| off \| When I try `wp theme update` Then STDERR should be: """ Error: Please specify one or more themes, or use --all. """ And the return code should be 1 When I run `wp theme update --all --format=summary \| grep 'updated successfully from'` Then STDOUT should contain: """ Twenty Twelve updated successfully from version 1.5 to version """ When I run `wp theme install twentytwelve --version=1.4 --force` Then STDOUT should not be empty When I run `wp theme update --all` Then STDOUT should contain: """ Success: Updated 1 of 1 themes. """ Scenario: Exclude theme from bulk updates. Given a WP install And I run `wp theme delete --all --force` And I run `wp theme install twentyeleven --activate` When I run `wp theme install twentytwelve --version=1.4 --force` Then STDOUT should contain: """ Downloading install """ And STDOUT should contain: """ package from https://downloads.wordpress.org/theme/twentytwelve.1.4.zip... """ When I run `wp theme activate twentytwelve` Then STDOUT should not be empty # Ensure no other themes interfere with update. When I run `wp theme list --status=inactive --field=name \| xargs wp theme delete` Then STDOUT should contain: """ Success: Deleted """ When I run `wp theme status twentytwelve` Then STDOUT should contain: """ Update available """ When I run `wp theme update --all --exclude=twentytwelve \| grep 'Skipped'` Then STDOUT should contain: """ twentytwelve """ When I run `wp theme status twentytwelve` Then STDOUT should contain: """ Update available """ Scenario: Get the path of an installed theme Given a WP install And I run `wp theme delete --all --force` When I run `wp theme install twentytwelve` Then STDOUT should not be empty When I run `wp theme path twentytwelve --dir` Then STDOUT should contain: """ wp-content/themes/twentytwelve """ Scenario: Activate an already active theme Given a WP install And I run `wp theme delete --all --force` When I run `wp theme install twentytwelve` Then STDOUT should not be empty When I run `wp theme activate twentytwelve` Then STDOUT should be: """ Success: Switched to 'Twenty Twelve' theme. """ When I try `wp theme activate twentytwelve` Then STDERR should be: """ Warning: The 'Twenty Twelve' theme is already active. """ And STDOUT should be empty And the return code should be 0 @require-wp-5.3 Scenario: Flag `--skip-update-check` skips update check when running `wp theme list` Given a WP install When I run `wp theme install astra --version=1.0.0` Then STDOUT should contain: """ Theme installed successfully. """ When I run `wp theme list --fields=name,status,update` Then STDOUT should be a table containing rows: \| name \| status \| update \| \| astra \| inactive \| available \| When I run `wp transient delete update_themes --network` Then STDOUT should be: """ Success: Transient deleted. """ When I run `wp theme list --fields=name,status,update --skip-update-check` Then STDOUT should be a table containing rows: \| name \| status \| update \| \| astra \| inactive \| none \| Scenario: Doing wp theme list does a force check by default, deleting any existing transient values Given a WP install When I run `wp theme list` Then STDOUT should not be empty When I run `wp eval 'echo get_site_transient("update_themes")->last_checked;'` Then save STDOUT as {LAST_UPDATED} When I run `wp theme list --skip-update-check` Then STDOUT should not be empty When I run `wp eval 'echo get_site_transient("update_themes")->last_checked;'` Then STDOUT should be: """ {LAST_UPDATED} """ When I run `wp theme list` Then STDOUT should not be empty When I run `wp eval 'echo get_site_transient("update_themes")->last_checked;'` Then STDOUT should not contain: """ {LAST_UPDATED} """ Scenario: Install a theme when the theme directory doesn't yet exist Given a WP install And I run `wp theme delete --all --force` When I run `rm -rf wp-content/themes` And I run `if test -d wp-content/themes; then echo "fail"; fi` Then STDOUT should be empty When I run `wp theme install twentytwelve --activate` Then STDOUT should not be empty When I run `wp theme list --fields=name,status` Then STDOUT should be a table containing rows: \| name \| status \| \| twentytwelve \| active \| Scenario: Attempt to activate or fetch a broken theme Given a WP install When I run `mkdir -pv wp-content/themes/myth` Then the wp-content/themes/myth directory should exist When I try `wp theme activate myth` Then STDERR should contain: """ Error: Stylesheet is missing. """ And STDOUT should be empty And the return code should be 1 When I try `wp theme get myth` Then STDERR should contain: """ Error: Stylesheet is missing. """ And STDOUT should be empty And the return code should be 1 When I try `wp theme status myth` Then STDERR should be: """ Error: Stylesheet is missing. """ And STDOUT should be empty And the return code should be 1 When I run `wp theme install myth --force` Then STDOUT should contain: """ Theme updated successfully. """ @require-wp-5.7 Scenario: Enabling and disabling a theme Given a WP multisite install And I run `wp theme install moina` And I run `wp theme install moina-blog` When I try `wp option get allowedthemes` Then the return code should be 1 # STDERR may or may not be empty, depending on WP-CLI version. And STDOUT should be empty When I run `wp theme enable moina-blog` Then STDOUT should contain: """ Success: Enabled the 'Moina Blog' theme. """ When I run `wp option get allowedthemes` Then STDOUT should contain: """ 'moina-blog' => true """ When I run `wp theme disable moina-blog` Then STDOUT should contain: """ Success: Disabled the 'Moina Blog' theme. """ When I run `wp option get allowedthemes` Then STDOUT should not contain: """ 'moina-blog' => true """ When I run `wp theme enable moina-blog --activate` Then STDOUT should contain: """ Success: Enabled the 'Moina Blog' theme. Success: Switched to 'Moina Blog' theme. """ # Hybrid_Registry throws warning for PHP 8+. When I try `wp network-meta get 1 allowedthemes` Then STDOUT should not contain: """ 'moina-blog' => true """ # Hybrid_Registry throws warning for PHP 8+. When I try `wp theme enable moina-blog --network` Then STDOUT should contain: """ Success: Network enabled the 'Moina Blog' theme. """ # Hybrid_Registry throws warning for PHP 8+. When I try `wp network-meta get 1 allowedthemes` Then STDOUT should contain: """ 'moina-blog' => true """ # Hybrid_Registry throws warning for PHP 8+. When I try `wp theme disable moina-blog --network` Then STDOUT should contain: """ Success: Network disabled the 'Moina Blog' theme. """ # Hybrid_Registry throws warning for PHP 8+. When I try `wp network-meta get 1 allowedthemes` Then STDOUT should not contain: """ 'moina-blog' => true """ Scenario: Enabling and disabling a theme without multisite Given a WP install When I try `wp theme enable twentytwelve` Then STDERR should contain: """ Error: This is not a multisite install """ And STDOUT should be empty And the return code should be 1 When I try `wp theme disable twentytwelve` Then STDERR should contain: """ Error: This is not a multisite install """ And STDOUT should be empty And the return code should be 1 @require-wp-5.7 Scenario: Install and attempt to activate a child theme without its parent Given a WP install And I run `wp theme install moina-blog` And I run `rm -rf wp-content/themes/moina` When I try `wp theme activate moina-blog` Then STDERR should contain: """ Error: The parent theme is missing. Please install the "moina" parent theme. """ And STDOUT should be empty And the return code should be 1 @require-wp-5.7 Scenario: List an active theme with its parent Given a WP install And I run `wp theme install moina` And I run `wp theme install --activate moina-blog` # Hybrid_Registry throws warning for PHP 8+. When I try `wp theme list --fields=name,status` Then STDOUT should be a table containing rows: \| name \| status \| \| moina-blog \| active \| \| moina \| parent \| Scenario: When updating a theme --format should be the same when using --dry-run Given a WP install And I run `wp theme delete --all --force` When I run `wp theme install --force twentytwelve --version=1.0` Then STDOUT should not be empty When I run `wp theme list --name=twentytwelve --field=update_version` Then save STDOUT as {UPDATE_VERSION} When I run `wp theme update twentytwelve --format=summary --dry-run` Then STDOUT should contain: """ Available theme updates: Twenty Twelve update from version 1.0 to version {UPDATE_VERSION} """ When I run `wp theme update twentytwelve --format=json --dry-run` Then STDOUT should be JSON containing: """ [{"name":"twentytwelve","status":"inactive","version":"1.0","update_version":"{UPDATE_VERSION}"}] """ When I run `wp theme update twentytwelve --format=csv --dry-run` Then STDOUT should contain: """ name,status,version,update_version twentytwelve,inactive,1.0,{UPDATE_VERSION} """ Scenario: When updating a theme --dry-run cannot be used when specifying a specific version. Given a WP install When I try `wp theme update --all --version=whatever --dry-run` Then STDERR should be: """ Error: --dry-run cannot be used together with --version. """ And the return code should be 1 Scenario: Check json and csv formats when updating a theme Given a WP install And I run `wp theme delete --all --force` When I run `wp theme install --force twentytwelve --version=1.0` Then STDOUT should not be empty When I run `wp theme list --name=twentytwelve --field=update_version` Then save STDOUT as {UPDATE_VERSION} When I run `wp theme update twentytwelve --format=json` Then STDOUT should contain: """ [{"name":"twentytwelve","old_version":"1.0","new_version":"{UPDATE_VERSION}","status":"Updated"}] """ When I run `wp theme install --force twentytwelve --version=1.0` Then STDOUT should not be empty When I run `wp theme update twentytwelve --format=csv` Then STDOUT should contain: """ name,old_version,new_version,status twentytwelve,1.0,{UPDATE_VERSION},Updated """ @require-wp-5.7 Scenario: Automatically install parent theme for a child theme Given a WP install When I try `wp theme status moina` Then STDERR should contain: """ Error: The 'moina' theme could not be found. """ And STDOUT should be empty And the return code should be 1 When I run `wp theme install moina-blog` Then STDOUT should contain: """ This theme requires a parent theme. Checking if it is installed """ When I run `wp theme status moina` Then STDOUT should contain: """ Theme moina details: """ And STDERR should be empty Scenario: Get status field in theme detail Given a WP install And I run `wp theme delete --all --force` When I run `wp theme install twentytwelve` Then STDOUT should not be empty When I run `wp theme get twentytwelve` Then STDOUT should be a table containing rows: \| Field \| Value \| \| status \| inactive \| When I run `wp theme get twentytwelve --field=status` Then STDOUT should be: """ inactive """ When I run `wp theme activate twentytwelve` Then STDOUT should not be empty When I run `wp theme get twentytwelve --field=status` Then STDOUT should be: """ active """ Scenario: Theme activation fails when slug does not match exactly Given a WP install And I run `wp theme delete --all --force` When I run `wp theme install twentytwelve` Then the return code should be 0 When I try `wp theme activate TwentyTwelve` Then STDERR should contain: """ Error: The 'TwentyTwelve' theme could not be found. Did you mean 'twentytwelve'? """ And STDOUT should be empty And the return code should be 1 When I try `wp theme activate twentytwelve3` Then STDERR should contain: """ Error: The 'twentytwelve3' theme could not be found. Did you mean 'twentytwelve'? """ And STDOUT should be empty And the return code should be 1 When I try `wp theme activate twentytwelves2` Then STDERR should contain: """ Error: The 'twentytwelves2' theme could not be found. Did you mean 'twentytwelve'? """ And STDOUT should be empty And the return code should be 1 When I try `wp theme activate completelyoff` Then STDERR should contain: """ Error: The 'completelyoff' theme could not be found. """ And STDERR should not contain: """ Did you mean """ And STDOUT should be empty And the return code should be 1 Scenario: Only valid status filters are accepted when listing themes Given a WP install When I run `wp theme list` Then STDERR should be empty When I run `wp theme list --status=active` Then STDERR should be empty When I try `wp theme list --status=invalid-status` Then STDERR should be: """ Error: Parameter errors: Invalid value specified for 'status' (Filter the output by theme status.) """ @require-wp-5.7 Scenario: Parent theme is active when its child is active Given a WP install And I run `wp theme delete --all --force` And I run `wp theme install twentytwelve` And I run `wp theme install moina-blog --activate` When I run `wp theme is-active moina-blog` Then the return code should be 0 When I run `wp theme is-active moina` Then the return code should be 0 When I try `wp theme is-active twentytwelve` Then the return code should be 1 Scenario: Excluding a missing theme should not throw an error Given a WP install And I run `wp theme delete --all --force` And I run `wp theme install twentytwelve --version=1.5 --activate` And I run `wp theme update --all --exclude=missing-theme` Then STDERR should be empty And STDOUT should contain: """ Success: """ And the return code should be 0 @require-wp-5.5 Scenario: Listing themes should include auto_update Given a WP install When I run `wp theme list --fields=auto_update` Then STDOUT should be a table containing rows: \| auto_update \| \| off \| When I run `wp theme auto-updates enable --all` And I try `wp theme list --fields=auto_update` Then STDOUT should be a table containing rows: \| auto_update \| \| on \| Scenario: Show theme update as unavailable if it doesn't meet WordPress requirements Given a WP install And a wp-content/themes/example/style.css file: """ /* Theme Name: example Version: 1.0.0 / """ And a wp-content/themes/example/index.php file: """ <?php // Silence is golden. """ And that HTTP requests to https://api.wordpress.org/themes/update-check/1.1/ will respond with: """ HTTP/1.1 200 OK { "themes": { "example": { "theme": "example", "new_version": "2.0.0", "requires": "100", "requires_php": "5.6" } }, "translations": [], "no_update": [] } """ When I run `wp theme list` Then STDOUT should be a table containing rows: \| name \| status \| update \| version \| update_version \| auto_update \| requires \| requires_php \| \| example \| inactive \| unavailable \| 1.0.0 \| 2.0.0 \| off \| 100 \| 5.6 \| When I try `wp theme update example` Then STDERR should contain: """ Warning: example: This update requires WordPress version 100 """ Scenario: Show theme update as unavailable if it doesn't meet PHP requirements Given a WP install And a wp-content/themes/example/style.css file: """ / Theme Name: example Version: 1.0.0 */ """ And a wp-content/themes/example/index.php file: """ <?php // Silence is golden. """ And that HTTP requests to https://api.wordpress.org/themes/update-check/1.1/ will respond with: """ HTTP/1.1 200 OK { "themes": { "example": { "theme": "example", "new_version": "2.0.0", "requires": "3.7", "requires_php": "100" } }, "translations": [], "no_update": [] } """ When I run `wp theme list` Then STDOUT should be a table containing rows: \| name \| status \| update \| version \| update_version \| auto_update \| requires \| requires_php \| \| example \| inactive \| unavailable \| 1.0.0 \| 2.0.0 \| off \| 3.7 \| 100 \| When I try `wp theme update example` Then STDERR should contain: """ Warning: example: This update requires PHP version 100 """	21.32 KB	2025-09-06 07:07
📄 upgradables.feature Feature: Manage WordPress themes and plugins Background: Given an empty cache @require-wp-4.5 Scenario Outline: Installing, upgrading and deleting a theme or plugin Given a WP install # Akismet ships with WordPress but does not work with older versions we test And I run `wp plugin delete akismet` And I run `wp <type> path` And save STDOUT as {CONTENT_DIR} When I try `wp <type> is-installed <item>` Then the return code should be 1 And STDERR should be empty And STDOUT should be empty When I try `wp <type> is-active <item>` Then the return code should be 1 And STDERR should be empty And STDOUT should be empty When I try `wp <type> get <item>` Then the return code should be 1 And STDERR should not be empty And STDOUT should be empty # Install an out of date <item> from WordPress.org repository When I run `wp <type> install <item> --version=<version>` Then STDOUT should contain: """ <type_name> installed successfully """ And the {SUITE_CACHE_DIR}/<type>/<item>-<version>.zip file should exist When I run `wp <type> is-installed <item>` Then the return code should be 0 When I run `wp <type> get <item>` Then STDOUT should be a table containing rows: \| Field \| Value \| \| title \| <item_title> \| When I run `wp <type> get <item> --field=title` Then STDOUT should contain: """ <item_title> """ When I run `wp <type> get <item> --field=title --format=json` Then STDOUT should contain: """ "<item_title>" """ When I run `wp <type> list --name=<item> --field=update_version` Then STDOUT should not be empty And save STDOUT as {UPDATE_VERSION} When I run `wp <type> list` Then STDOUT should be a table containing rows: \| name \| status \| update \| version \| update_version \| auto_update \| \| <item> \| inactive \| available \| <version> \| {UPDATE_VERSION} \| off \| When I run `wp <type> list --field=name` Then STDOUT should contain: """ <item> """ When I run `wp <type> list --field=name --format=json` Then STDOUT should be a JSON array containing: """ ["<item>"] """ When I run `wp <type> status` Then STDOUT should contain: """ U = Update Available """ When I run `wp <type> status <item>` Then STDOUT should contain: """ Status: Inactive Version: <version> (Update available) """ When I run `wp <type> update <item>` And save STDOUT 'Downloading update from .*\/<item>\.%s\.zip' as {NEW_VERSION} And STDOUT should not be empty Then STDOUT should not contain: """ Error """ And the {SUITE_CACHE_DIR}/<type>/<item>-{NEW_VERSION}.zip file should exist # This can throw warnings about versions being higher than expected. When I try `wp <type> update --all 2>&1` Then STDOUT should contain: """ updated """ When I run `wp <type> status <item>` Then STDOUT should not contain: """ (Update available) """ When I run `wp <type> delete <item>` Then STDOUT should contain: """ Deleted '<item>' <type>. """ When I try `wp <type> status <item>` Then the return code should be 1 And STDERR should not be empty And STDOUT should be empty # Install and update <item> from cache When I run `wp <type> install <item> --version=<version>` Then STDOUT should contain: """ Using cached file '{SUITE_CACHE_DIR}/<type>/<item>-<version>.zip'... """ When I run `wp <type> update <item>` Then STDOUT should contain: """ Using cached file '{SUITE_CACHE_DIR}/<type>/<item>-{NEW_VERSION}.zip'... """ When I run `wp <type> delete <item>` Then STDOUT should contain: """ Deleted '<item>' <type>. """ And the <file_to_check> file should not exist # Install <item> from a local zip file When I run `wp <type> install {SUITE_CACHE_DIR}/<type>/<item>-<version>.zip` Then STDOUT should contain: """ <type_name> installed successfully. """ And the <file_to_check> file should exist When I run `wp <type> delete <item>` Then STDOUT should contain: """ Deleted '<item>' <type>. """ And the <file_to_check> file should not exist # Install <item> from a remote zip file (standard URL with no GET parameters) When I run `wp <type> install <zip_file>` Then STDOUT should contain: """ <type_name> installed successfully. """ And the <file_to_check> file should exist When I run `wp <type> delete <item>` Then STDOUT should contain: """ Deleted '<item>' <type>. """ And the <file_to_check> file should not exist # Install <item> from a remote zip file (complex URL with GET parameters) When I run `wp <type> install '<zip_file>?AWSAccessKeyId=123&Expires=456&Signature=abcdef'` Then STDOUT should contain: """ <type_name> installed successfully. """ And the <file_to_check> file should exist When I run `wp <type> delete <item>` Then STDOUT should contain: """ Deleted '<item>' <type>. """ And the <file_to_check> file should not exist When I run `wp <type> list --fields=name` Then STDOUT should not contain: """ <item> """ When I try `wp <type> install an-impossible-slug-because-abc3fr` Then STDERR should contain: """ Warning: """ And STDERR should contain: """ an-impossible-slug-because-abc3fr """ And STDERR should contain: """ Error: No <type>s installed. """ And STDOUT should be empty And the return code should be 1 Examples: \| type \| type_name \| item \| item_title \| version \| zip_file \| file_to_check \| \| theme \| Theme \| moina \| Moina \| 1.1.2 \| https://wordpress.org/themes/download/moina.1.1.2.zip \| {CONTENT_DIR}/moina/style.css \| \| plugin \| Plugin \| category-checklist-tree \| Category Checklist Tree \| 1.2 \| https://downloads.wordpress.org/plugin/category-checklist-tree.1.2.zip \| {CONTENT_DIR}/category-checklist-tree/category-checklist-tree.php \| @require-wp-4.5 Scenario Outline: Caches certain GitHub URLs Given a WP install And I run `wp plugin delete --all` When I run `wp plugin install <zip_file>` Then STDOUT should contain: """ Plugin installed successfully """ And STDOUT should not contain: """ Using cached file '{SUITE_CACHE_DIR}/plugin/<item>-<version> """ When I run `wp plugin delete --all` And I run `wp plugin install <zip_file>` Then STDOUT should contain: """ Plugin installed successfully """ And STDOUT should contain: """ Using cached file '{SUITE_CACHE_DIR}/plugin/<item>-<version> """ Examples: \| item \| version \| zip_file \| \| one-time-login \| 0.4.0 \| https://github.com/danielbachhuber/one-time-login/releases/latest \| \| preferred-languages \| 1.8.0 \| https://github.com/swissspidy/preferred-languages/releases/download/1.8.0/preferred-languages.zip \| \| generic-example-plugin \| 0.1.1 \| https://github.com/wp-cli-test/generic-example-plugin/archive/v0.1.1.zip \|	7.69 KB	2025-09-06 07:07

Edit File:

Terminal