Feature: Manage WP-CLI packages Scenario: Package CRUD Given an empty directory When I run `wp package browse` Then STDOUT should contain: """ runcommand/hook """ When I run `wp package install runcommand/hook` Then STDERR should be empty When I run `wp help hook` Then STDERR should be empty And STDOUT should contain: """ List callbacks registered to a given action or filter. """ When I try `wp --skip-packages --debug help hook` Then STDERR should contain: """ Debug (bootstrap): Skipped loading packages. """ And STDERR should contain: """ Warning: No WordPress install """ When I run `wp package list` Then STDOUT should contain: """ runcommand/hook """ When I run `wp package uninstall runcommand/hook` Then STDERR should be empty When I run `wp package list` Then STDOUT should not contain: """ runcommand/hook """ Scenario: Run package commands early, before any bad code can break them Given an empty directory And a bad-command.php file: """