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
📄 comment-generate.feature Feature: Generate comments Background: Given a WP install Scenario: Generate a specific number of comments When I run `wp comment generate --count=20` And I run `wp comment list --format=count` Then STDOUT should be: """ 21 """ Scenario: Generate comments assigned to a specific post When I run `wp comment generate --count=4 --post_id=2` And I run `wp comment list --post_id=2 --format=count` Then STDOUT should be: """ 4 """ When I run `wp comment list --post_id=1 --format=count` Then STDOUT should be: """ 1 """ Scenario: Generating comments and outputting ids When I run `wp comment generate --count=1 --format=ids` Then save STDOUT as {COMMENT_ID} When I run `wp comment update {COMMENT_ID} --comment_content="foo"` Then STDOUT should contain: """ Success: """	905 B	2025-05-25 12:40
📄 comment-list.feature Feature: List WordPress comments @require-wp-4.1 Scenario: Filter comments based on `comment__in` and `comment__not_in` Given a WP install When I run `wp comment create --comment_post_ID=1 --porcelain` Then save STDOUT as {COMMENT_ID} When I run `wp comment list --comment__in=1,{COMMENT_ID} --format=ids --orderby=comment_ID --order=ASC` Then STDOUT should be: """ 1 {COMMENT_ID} """ When I run `wp comment list --comment__in=1 --format=ids --orderby=comment_ID --order=ASC` Then STDOUT should be: """ 1 """ When I run `wp comment list --comment__not_in=1,{COMMENT_ID} --format=ids --orderby=comment_ID --order=ASC` Then STDOUT should be: """ """ When I run `wp comment list --comment__not_in=1 --format=ids --orderby=comment_ID --order=ASC` Then STDOUT should be: """ {COMMENT_ID} """ Scenario: Count comments Given a WP install When I run `wp comment list --format=count` Then STDOUT should be: """ 1 """	1.04 KB	2025-05-25 12:40
📄 comment-meta.feature Feature: Manage comment custom fields Scenario: Comment meta CRUD Given a WP install When I run `wp comment-meta add 1 foo 'bar'` Then STDOUT should not be empty When I run `wp comment-meta get 1 foo` Then STDOUT should be: """ bar """ When I try `wp comment meta get 999999 foo` Then STDERR should be: """ Error: Could not find the comment with ID 999999. """ And the return code should be 1 When I run `wp comment-meta set 1 foo '[ "1", "2" ]' --format=json` Then STDOUT should not be empty When I run `wp comment-meta get 1 foo --format=json` Then STDOUT should be: """ ["1","2"] """ When I run `wp comment-meta delete 1 foo` Then STDOUT should not be empty When I try `wp comment-meta get 1 foo` Then the return code should be 1 Scenario: Add comment meta with JSON serialization Given a WP install When I try `wp comment meta add 1 foo '-- hi'` Then STDERR should be: """ Error: Parameter errors: unknown -- hi parameter """ And the return code should be 1 When I run `wp comment meta add 1 foo '"-- hi"' --format=json` Then STDOUT should contain: """ Success: """ When I run `wp comment meta get 1 foo` Then STDOUT should be: """ -- hi """ Scenario: List comment meta Given a WP install When I run `wp comment meta add 1 apple banana` And I run `wp comment meta add 1 apple banana` Then STDOUT should not be empty When I run `wp comment meta set 1 banana '["apple", "apple"]' --format=json` Then STDOUT should not be empty When I run `wp comment meta list 1` Then STDOUT should be a table containing rows: \| comment_id \| meta_key \| meta_value \| \| 1 \| apple \| banana \| \| 1 \| apple \| banana \| \| 1 \| banana \| a:2:{i:0;s:5:"apple";i:1;s:5:"apple";} \| When I run `wp comment meta list 1 --unserialize` Then STDOUT should be a table containing rows: \| comment_id \| meta_key \| meta_value \| \| 1 \| apple \| banana \| \| 1 \| apple \| banana \| \| 1 \| banana \| ["apple","apple"] \|	2.33 KB	2025-09-06 07:07
📄 comment-recount.feature Feature: Recount comments on a post Scenario: Recount comments on a post Given a WP install When I run `wp comment create --comment_post_ID=1 --comment_approved=1 --porcelain` And I run `wp comment create --comment_post_ID=1 --comment_approved=1 --porcelain` And I run `wp post get 1 --field=comment_count` Then STDOUT should be: """ 3 """ When I run `wp eval 'global $wpdb; $wpdb->update( $wpdb->posts, array( "comment_count" => 1 ), array( "ID" => 1 ) );'` And I run `wp post get 1 --field=comment_count` Then STDOUT should be: """ 1 """ When I run `wp comment recount 1` Then STDOUT should be: """ Updated post 1 comment count to 3. """ When I try `wp comment recount 99999999` Then STDERR should be: """ Warning: Post 99999999 doesn't exist. """	877 B	2025-05-25 12:40
📄 comment.feature Feature: Manage WordPress comments Background: Given a WP install Scenario: Creating/updating/deleting comments When I run `wp comment create --comment_post_ID=1 --comment_content='Hello' --comment_author='Billy' --porcelain` Then STDOUT should be a number And save STDOUT as {COMMENT_ID} When I run `wp comment exists {COMMENT_ID}` Then STDOUT should be: """ Success: Comment with ID {COMMENT_ID} exists. """ When I run `wp comment update {COMMENT_ID} --comment_author='Johnny'` Then STDOUT should not be empty When I run `wp comment get {COMMENT_ID} --field=author` Then STDOUT should be: """ Johnny """ When I run `wp comment delete {COMMENT_ID}` Then STDOUT should be: """ Success: Trashed comment {COMMENT_ID}. """ When I run `wp comment get {COMMENT_ID} --field=comment_approved` Then STDOUT should be: """ trash """ When I run `wp comment delete {COMMENT_ID} --force` Then STDOUT should be: """ Success: Deleted comment {COMMENT_ID}. """ When I try `wp comment get {COMMENT_ID}` Then STDERR should be: """ Error: Invalid comment ID. """ And the return code should be 1 When I run `wp comment create --comment_post_ID=1` And I run `wp comment create --comment_post_ID=1` And I run `wp comment delete 3 4` Then STDOUT should be: """ Success: Trashed comment 3. Success: Trashed comment 4. """ When I run `wp comment delete 3` Then STDOUT should be: """ Success: Deleted comment 3. """ When I try `wp comment get 3` Then STDERR should be: """ Error: Invalid comment ID. """ And the return code should be 1 Scenario: Updating an invalid comment should return an error Given a WP install When I try `wp comment update 22 --comment_author=Foo` Then the return code should be 1 And STDERR should contain: """ Warning: Could not update comment. """ Scenario: Get details about an existing comment When I run `wp comment get 1` Then STDOUT should be a table containing rows: \| Field \| Value \| \| comment_approved \| 1 \| When I run `wp comment get 1 --fields=comment_approved --format=json` Then STDOUT should be JSON containing: """ {"comment_approved":"1"} """ When I run `wp comment list --fields=comment_approved` Then STDOUT should be a table containing rows: \| comment_approved \| \| 1 \| When I run `wp comment list --field=approved` Then STDOUT should be: """ 1 """ When I run `wp comment list --format=ids` Then STDOUT should be: """ 1 """ When I run `wp comment url 1` Then STDOUT should contain: """ #comment-1 """ When I run `wp comment get 1 --field=url` Then STDOUT should contain: """ #comment-1 """ Scenario: List the URLs of comments When I run `wp comment create --comment_post_ID=1 --porcelain` Then save STDOUT as {COMMENT_ID} When I run `wp comment url 1 {COMMENT_ID}` Then STDOUT should be: """ https://example.com/?p=1#comment-1 https://example.com/?p=1#comment-{COMMENT_ID} """ When I run `wp comment url {COMMENT_ID} 1` Then STDOUT should be: """ https://example.com/?p=1#comment-{COMMENT_ID} https://example.com/?p=1#comment-1 """ Scenario: Count comments When I run `wp comment count 1` Then STDOUT should contain: """ approved: 1 """ And STDOUT should contain: """ moderated: 0 """ And STDOUT should contain: """ total_comments: 1 """ When I run `wp comment count` Then STDOUT should contain: """ approved: 1 """ And STDOUT should contain: """ moderated: 0 """ And STDOUT should contain: """ total_comments: 1 """ @require-mysql Scenario: Approving/unapproving comments Given I run `wp comment create --comment_post_ID=1 --comment_approved=0 --porcelain` And save STDOUT as {COMMENT_ID} # With site url set. When I run `wp comment approve {COMMENT_ID} --url=www.example.com` Then STDOUT should be: """ Success: Approved comment {COMMENT_ID}. """ When I try the previous command again Then STDERR should contain: """ Error: Could not update comment status """ And STDOUT should be empty And the return code should be 1 When I run `wp comment get --field=comment_approved {COMMENT_ID}` Then STDOUT should be: """ 1 """ When I run `wp comment unapprove {COMMENT_ID} --url=www.example.com` Then STDOUT should be: """ Success: Unapproved comment {COMMENT_ID}. """ When I run `wp comment get --field=comment_approved {COMMENT_ID}` Then STDOUT should be: """ 0 """ # Without site url set. When I try `wp comment approve {COMMENT_ID}` Then STDOUT should be: """ Success: Approved comment {COMMENT_ID}. """ And STDERR should be: """ Warning: Site url not set - defaulting to 'example.com'. Any notification emails sent to post author may appear to come from 'example.com'. """ And the return code should be 0 When I try `wp comment unapprove {COMMENT_ID}` Then STDOUT should be: """ Success: Unapproved comment {COMMENT_ID}. """ And STDERR should be: """ Warning: Site url not set - defaulting to 'example.com'. Any notification emails sent to post author may appear to come from 'example.com'. """ And the return code should be 0 # Approving an approved comment works in SQLite @require-sqlite Scenario: Approving/unapproving comments Given I run `wp comment create --comment_post_ID=1 --comment_approved=0 --porcelain` And save STDOUT as {COMMENT_ID} # With site url set. When I run `wp comment approve {COMMENT_ID} --url=www.example.com` Then STDOUT should be: """ Success: Approved comment {COMMENT_ID}. """ When I try the previous command again Then STDOUT should be: """ Success: Approved comment {COMMENT_ID}. """ When I run `wp comment get --field=comment_approved {COMMENT_ID}` Then STDOUT should be: """ 1 """ When I run `wp comment unapprove {COMMENT_ID} --url=www.example.com` Then STDOUT should be: """ Success: Unapproved comment {COMMENT_ID}. """ When I run `wp comment get --field=comment_approved {COMMENT_ID}` Then STDOUT should be: """ 0 """ # Without site url set. When I try `wp comment approve {COMMENT_ID}` Then STDOUT should be: """ Success: Approved comment {COMMENT_ID}. """ And STDERR should be: """ Warning: Site url not set - defaulting to 'example.com'. Any notification emails sent to post author may appear to come from 'example.com'. """ And the return code should be 0 When I try `wp comment unapprove {COMMENT_ID}` Then STDOUT should be: """ Success: Unapproved comment {COMMENT_ID}. """ And STDERR should be: """ Warning: Site url not set - defaulting to 'example.com'. Any notification emails sent to post author may appear to come from 'example.com'. """ And the return code should be 0 Scenario: Approving/unapproving comments with multidigit comment ID Given I run `wp comment delete $(wp comment list --field=ID)` And I run `wp comment generate --count=10 --quiet` And I run `wp comment create --comment_post_ID=1 --porcelain` And save STDOUT as {COMMENT_ID} # With site url set. When I run `wp comment unapprove {COMMENT_ID} --url=www.example.com` Then STDOUT should be: """ Success: Unapproved comment {COMMENT_ID}. """ When I run `wp comment list --format=count --status=approve` Then STDOUT should be: """ 10 """ When I run `wp comment approve {COMMENT_ID} --url=www.example.com` Then STDOUT should be: """ Success: Approved comment {COMMENT_ID}. """ When I run `wp comment list --format=count --status=approve` Then STDOUT should be: """ 11 """ # Without site url set. When I try `wp comment unapprove {COMMENT_ID}` Then STDOUT should be: """ Success: Unapproved comment {COMMENT_ID}. """ And STDERR should be: """ Warning: Site url not set - defaulting to 'example.com'. Any notification emails sent to post author may appear to come from 'example.com'. """ And the return code should be 0 When I try `wp comment approve {COMMENT_ID}` Then STDOUT should be: """ Success: Approved comment {COMMENT_ID}. """ And STDERR should be: """ Warning: Site url not set - defaulting to 'example.com'. Any notification emails sent to post author may appear to come from 'example.com'. """ And the return code should be 0 Scenario: Spam/unspam comments with multidigit comment ID Given I run `wp comment delete $(wp comment list --field=ID)` And I run `wp comment generate --count=10 --quiet` And I run `wp comment create --comment_post_ID=1 --porcelain` And save STDOUT as {COMMENT_ID} # With site url set. When I run `wp comment spam {COMMENT_ID}` Then STDOUT should be: """ Success: Marked comment {COMMENT_ID} as spam. """ When I run `wp comment list --format=count --status=spam` Then STDOUT should be: """ 1 """ When I run `wp comment unspam {COMMENT_ID} --url=www.example.com` Then STDOUT should be: """ Success: Unspammed comment {COMMENT_ID}. """ When I run `wp comment list --format=count --status=spam` Then STDOUT should be: """ 0 """ # Without site url set. When I run `wp comment spam {COMMENT_ID}` Then STDOUT should be: """ Success: Marked comment {COMMENT_ID} as spam. """ When I try `wp comment unspam {COMMENT_ID}` Then STDOUT should be: """ Success: Unspammed comment {COMMENT_ID}. """ And STDERR should be: """ Warning: Site url not set - defaulting to 'example.com'. Any notification emails sent to post author may appear to come from 'example.com'. """ And the return code should be 0 Scenario: Trash/untrash comments with multidigit comment ID Given I run `wp comment delete $(wp comment list --field=ID) --force` And I run `wp comment generate --count=10 --quiet` And I run `wp comment create --comment_post_ID=1 --porcelain` And save STDOUT as {COMMENT_ID} # With site url set. When I run `wp comment trash {COMMENT_ID}` Then STDOUT should be: """ Success: Trashed comment {COMMENT_ID}. """ When I run `wp comment list --format=count --status=trash` Then STDOUT should be: """ 1 """ When I run `wp comment untrash {COMMENT_ID} --url=www.example.com` Then STDOUT should be: """ Success: Untrashed comment {COMMENT_ID}. """ When I run `wp comment list --format=count --status=trash` Then STDOUT should be: """ 0 """ # Without site url set. When I run `wp comment trash {COMMENT_ID}` Then STDOUT should be: """ Success: Trashed comment {COMMENT_ID}. """ When I try `wp comment untrash {COMMENT_ID}` Then STDOUT should be: """ Success: Untrashed comment {COMMENT_ID}. """ And STDERR should be: """ Warning: Site url not set - defaulting to 'example.com'. Any notification emails sent to post author may appear to come from 'example.com'. """ And the return code should be 0 Scenario: Make sure WordPress receives the slashed data it expects When I run `wp comment create --comment_content='My\Comment' --porcelain` Then save STDOUT as {COMMENT_ID} When I run `wp comment get {COMMENT_ID} --field=comment_content` Then STDOUT should be: """ My\Comment """ When I run `wp comment update {COMMENT_ID} --comment_content='My\New\Comment'` Then STDOUT should not be empty When I run `wp comment get {COMMENT_ID} --field=comment_content` Then STDOUT should be: """ My\New\Comment """ @require-wp-4.4 Scenario: Approving/unapproving/unspamming/untrashing (approved) comments with no comment post id should not produce PHP notices for WP >= 4.4 Given I run `wp comment create --comment_approved=0 --porcelain` And save STDOUT as {COMMENT_ID} When I run `wp comment approve {COMMENT_ID} --url=www.example.com` And I run `wp comment unapprove {COMMENT_ID} --url=www.example.com` Given I run `wp comment approve {COMMENT_ID} --url=www.example.com` When I run `wp comment spam {COMMENT_ID} --url=www.example.com` And I run `wp comment unspam {COMMENT_ID} --url=www.example.com` And I run `wp comment trash {COMMENT_ID} --url=www.example.com` And I run `wp comment untrash {COMMENT_ID} --url=www.example.com`	13.17 KB	2025-09-06 07:07
📄 menu-item.feature Feature: Manage WordPress menu items Background: Given a WP install Scenario: Add / update / remove items from a menu When I run `wp post create --post_title='Test post' --porcelain` Then STDOUT should be a number And save STDOUT as {POST_ID} When I run `wp post url {POST_ID}` Then save STDOUT as {POST_LINK} When I run `wp term create post_tag 'Test term' --slug=test --description='This is a test term' --porcelain` Then STDOUT should be a number And save STDOUT as {TERM_ID} When I run `wp term url post_tag {TERM_ID}` Then save STDOUT as {TERM_LINK} When I run `wp menu create "Sidebar Menu"` Then STDOUT should not be empty When I run `wp menu item add-post sidebar-menu {POST_ID} --title="Custom Test Post" --description="Georgia peaches" --porcelain` Then save STDOUT as {POST_ITEM_ID} When I run `wp menu item update {POST_ITEM_ID} --description="Washington Apples"` Then STDOUT should be: """ Success: Menu item updated. """ When I run `wp menu item add-term sidebar-menu post_tag {TERM_ID} --porcelain` Then save STDOUT as {TERM_ITEM_ID} When I run `wp menu item add-custom sidebar-menu Apple https://apple.com --parent-id={POST_ITEM_ID} --porcelain` Then save STDOUT as {CUSTOM_ITEM_ID} When I run `wp menu item update {CUSTOM_ITEM_ID} --title=WordPress --link='https://wordpress.org' --target=_blank --position=2` Then STDOUT should be: """ Success: Menu item updated. """ When I run `wp menu item update {TERM_ITEM_ID} --position=3` Then STDOUT should be: """ Success: Menu item updated. """ When I run `wp menu item list sidebar-menu --fields=type,title,description,position,link,menu_item_parent` Then STDOUT should be a table containing rows: \| type \| title \| description \| position \| link \| menu_item_parent \| \| post_type \| Custom Test Post \| Washington Apples \| 1 \| {POST_LINK} \| 0 \| \| custom \| WordPress \| \| 2 \| https://wordpress.org \| {POST_ITEM_ID} \| \| taxonomy \| Test term \| \| 3 \| {TERM_LINK} \| 0 \| When I run `wp menu item list sidebar-menu --format=ids` Then STDOUT should not be empty When I run `wp menu item delete {CUSTOM_ITEM_ID}` Then STDOUT should be: """ Success: Deleted 1 of 1 menu items. """ And I run `wp menu item list sidebar-menu --format=count` And STDOUT should be: """ 2 """ When I run `wp menu item delete {POST_ITEM_ID} {TERM_ITEM_ID}` Then STDOUT should be: """ Success: Deleted 2 of 2 menu items. """ And I run `wp menu item list sidebar-menu --format=count` And STDOUT should be: """ 0 """ Scenario: Preserve grandparent item as ancestor of child item when parent item is removed. When I run `wp menu create "Grandparent Test"` Then STDOUT should not be empty When I run `wp menu item add-custom grandparent-test Grandparent https://example.com/grandparent --porcelain` Then save STDOUT as {GRANDPARENT_ID} When I run `wp menu item add-custom grandparent-test Parent https://example.com/parent --porcelain --parent-id={GRANDPARENT_ID}` Then save STDOUT as {PARENT_ID} When I run `wp menu item add-custom grandparent-test Child https://example.com/child --porcelain --parent-id={PARENT_ID}` Then save STDOUT as {CHILD_ID} When I run `wp menu item list grandparent-test --fields=title,db_id,menu_item_parent` Then STDOUT should be a table containing rows: \| title \| db_id \| menu_item_parent \| \| Grandparent \| {GRANDPARENT_ID} \| 0 \| \| Parent \| {PARENT_ID} \| {GRANDPARENT_ID} \| \| Child \| {CHILD_ID} \| {PARENT_ID} \| When I run `wp menu item delete {PARENT_ID}` And I run `wp menu item list grandparent-test --fields=title,db_id,menu_item_parent` Then STDOUT should be a table containing rows: \| title \| db_id \| menu_item_parent \| \| Grandparent \| {GRANDPARENT_ID} \| 0 \| \| Child \| {CHILD_ID} \| {GRANDPARENT_ID} \| Scenario: Error deleting one or more menu items When I run `wp menu create "Sidebar Menu"` Then STDOUT should not be empty When I try `wp menu item delete 99999999` Then STDERR should be: """ Warning: Couldn't delete menu item 99999999. Error: No menu items deleted. """ And the return code should be 1 When I run `wp menu item add-custom sidebar-menu Apple https://apple.com --porcelain` Then save STDOUT as {CUSTOM_ITEM_ID} When I try `wp menu item delete {CUSTOM_ITEM_ID} 99999999` Then STDERR should be: """ Warning: Couldn't delete menu item 99999999. Error: Only deleted 1 of 2 menu items. """ And the return code should be 1 Scenario: Menu order is recalculated on insertion When I run `wp menu create "Sidebar Menu"` Then STDOUT should not be empty When I run `wp menu item add-custom sidebar-menu First https://first.com --porcelain` Then save STDOUT as {ITEM_ID_1} When I run `wp menu item add-custom sidebar-menu Second https://second.com --porcelain` Then save STDOUT as {ITEM_ID_2} When I run `wp menu item add-custom sidebar-menu Third https://third.com --porcelain` Then save STDOUT as {ITEM_ID_3} When I run `wp menu item list sidebar-menu --fields=type,title,position,link` Then STDOUT should be a table containing rows: \| type \| title \| position \| link \| \| custom \| First \| 1 \| https://first.com \| \| custom \| Second \| 2 \| https://second.com \| \| custom \| Third \| 3 \| https://third.com \| When I run `wp menu item add-custom sidebar-menu Fourth https://fourth.com --position=2 --porcelain` Then save STDOUT as {ITEM_ID_4} When I run `wp menu item list sidebar-menu --fields=type,title,position,link` Then STDOUT should be a table containing rows: \| type \| title \| position \| link \| \| custom \| First \| 1 \| https://first.com \| \| custom \| Fourth \| 2 \| https://fourth.com \| \| custom \| Second \| 3 \| https://second.com \| \| custom \| Third \| 4 \| https://third.com \| Scenario: Menu order is recalculated on deletion When I run `wp menu create "Sidebar Menu"` Then STDOUT should not be empty When I run `wp menu item add-custom sidebar-menu First https://first.com --porcelain` Then save STDOUT as {ITEM_ID_1} When I run `wp menu item add-custom sidebar-menu Second https://second.com --porcelain` Then save STDOUT as {ITEM_ID_2} When I run `wp menu item add-custom sidebar-menu Third https://third.com --porcelain` Then save STDOUT as {ITEM_ID_3} When I run `wp menu item list sidebar-menu --fields=type,title,position,link` Then STDOUT should be a table containing rows: \| type \| title \| position \| link \| \| custom \| First \| 1 \| https://first.com \| \| custom \| Second \| 2 \| https://second.com \| \| custom \| Third \| 3 \| https://third.com \| When I run `wp menu item delete {ITEM_ID_2}` Then STDOUT should be: """ Success: Deleted 1 of 1 menu items. """ When I run `wp menu item list sidebar-menu --fields=type,title,position,link` Then STDOUT should be a table containing rows: \| type \| title \| position \| link \| \| custom \| First \| 1 \| https://first.com \| \| custom \| Third \| 2 \| https://third.com \|	7.68 KB	2025-09-06 07:07
📄 menu-location.feature Feature: Manage WordPress menu locations Background: Given a WP install And I run `wp theme delete --all --force` And I run `wp theme install twentytwelve --activate` Scenario: Assign / remove location from a menu When I run `wp menu location list` Then STDOUT should be a table containing rows: \| location \| description \| \| primary \| Primary Menu \| When I run `wp menu create "Primary Menu"` And I run `wp menu location assign primary-menu primary` And I run `wp menu list --fields=slug,locations` Then STDOUT should be a table containing rows: \| slug \| locations \| \| primary-menu \| primary \| When I run `wp menu location list --format=ids` Then STDOUT should be: """ primary """ When I run `wp menu location remove primary-menu primary` And I run `wp menu list --fields=slug,locations` Then STDOUT should be a table containing rows: \| slug \| locations \| \| primary-menu \| \| When I try `wp menu location assign secondary-menu secondary` Then STDERR should be: """ Error: Invalid menu secondary-menu. """ And the return code should be 1 When I run `wp menu create "Secondary Menu"` And I try `wp menu location assign secondary-menu secondary` Then STDERR should be: """ Error: Invalid location secondary. """ And the return code should be 1 When I run `wp menu location assign secondary-menu primary` Then STDOUT should be: """ Success: Assigned location primary to menu secondary-menu. """ When I run `wp menu list --fields=slug,locations` Then STDOUT should be a table containing rows: \| slug \| locations \| \| primary-menu \| \| \| secondary-menu \| primary \|	1.88 KB	2025-05-25 12:40
📄 menu.feature Feature: Manage WordPress menus Background: Given a WP install Scenario: Menu CRUD operations When I run `wp menu create "My Menu"` And I run `wp menu list --fields=name,slug` Then STDOUT should be a table containing rows: \| name \| slug \| \| My Menu \| my-menu \| When I run `wp menu delete "My Menu"` Then STDOUT should be: """ Deleted menu 'My Menu'. Success: Deleted 1 of 1 menus. """ And the return code should be 0 When I run `wp menu list --format=count` Then STDOUT should be: """ 0 """ When I run `wp menu create "First Menu"` And I run `wp menu create "Second Menu"` And I run `wp menu list --fields=name,slug` Then STDOUT should be a table containing rows: \| name \| slug \| \| First Menu \| first-menu \| \| Second Menu \| second-menu \| When I run `wp menu delete "First Menu" "Second Menu"` Then STDOUT should be: """ Deleted menu 'First Menu'. Deleted menu 'Second Menu'. Success: Deleted 2 of 2 menus. """ And the return code should be 0 When I run `wp menu list --format=count` Then STDOUT should be: """ 0 """ When I run `wp menu create "First Menu"` And I run `wp menu list --format=ids` Then STDOUT should be: """ 5 """ Scenario: Errors when deleting menus When I try `wp menu delete "Your menu"` Then STDERR should be: """ Warning: Couldn't delete menu 'Your menu'. Error: No menus deleted. """ And the return code should be 1 When I run `wp menu create "My Menu"` And I run `wp menu list --fields=name,slug` Then STDOUT should be a table containing rows: \| name \| slug \| \| My Menu \| my-menu \| When I try `wp menu delete "My Menu" "Your menu"` Then STDERR should be: """ Warning: Couldn't delete menu 'Your menu'. Error: Only deleted 1 of 2 menus. """ And the return code should be 1	2.05 KB	2025-05-25 12:40
📄 network-meta.feature Feature: Manage network-wide custom fields. Scenario: Non-multisite Given a WP install When I run `wp network-meta` Then STDOUT should contain: """ usage: wp network meta """ When I try `wp network-meta get 1 site_admins` Then STDOUT should be empty And STDERR should contain: """ This is not a multisite install """ And the return code should be 1	418 B	2025-05-25 12:40
📄 option-get-autoload.feature Feature: Get 'autoload' value for an option Scenario: Option doesn't exist Given a WP install When I try `wp option get-autoload foo` Then STDERR should be: """ Error: Could not get 'foo' option. Does it exist? """ @less-than-wp-6.6 Scenario: Displays 'autoload' value Given a WP install When I run `wp option add foo bar` Then STDOUT should contain: """ Success: """ When I run `wp option get-autoload foo` Then STDOUT should be: """ yes """ @require-wp-6.6 Scenario: Displays 'autoload' value Given a WP install When I run `wp option add foo bar` Then STDOUT should contain: """ Success: """ When I run `wp option get-autoload foo` Then STDOUT should be: """ on """	826 B	2025-05-25 12:40
📄 option-list.feature Feature: List WordPress options Scenario: Using the `--transients` flag Given a WP install And I run `wp transient set wp_transient_flag wp_transient_flag` When I run `wp option list --no-transients` Then STDOUT should not contain: """ wp_transient_flag """ And STDOUT should not contain: """ _transient """ And STDOUT should contain: """ siteurl """ When I run `wp option list --transients` Then STDOUT should contain: """ wp_transient_flag """ And STDOUT should contain: """ _transient """ And STDOUT should not contain: """ siteurl """ Scenario: List option with exclude pattern Given a WP install When I run `wp option add sample_test_field_one sample_test_field_value_one` And I run `wp option add sample_test_field_two sample_test_field_value_two` And I run `wp option list --search="sample_test_field_" --format=csv` Then STDOUT should be: """ option_name,option_value sample_test_field_one,sample_test_field_value_one sample_test_field_two,sample_test_field_value_two """ When I run `wp option list --search="sample_test_field_" --exclude="field_one" --format=csv` Then STDOUT should be: """ option_name,option_value sample_test_field_two,sample_test_field_value_two """ When I run `wp option list` Then STDOUT should contain: """ sample_test_field_one """ When I run `wp option list --exclude="sample_test_field_one"` Then STDOUT should not contain: """ sample_test_field_one """ Scenario: List option with sorting option Given a WP install And I run `wp option add sample_test_field_one sample_test_field_value_one` And I run `wp option add sample_test_field_two sample_test_field_value_two` When I run `wp option list --search="sample_test_field_" --format=csv --orderby=option_id --order=asc` Then STDOUT should be: """ option_name,option_value sample_test_field_one,sample_test_field_value_one sample_test_field_two,sample_test_field_value_two """ When I run `wp option list --search="sample_test_field_" --format=csv --orderby=option_id --order=desc` Then STDOUT should be: """ option_name,option_value sample_test_field_two,sample_test_field_value_two sample_test_field_one,sample_test_field_value_one """ When I run `wp option list --search="sample_test_field_" --format=csv --orderby=option_name --order=asc` Then STDOUT should be: """ option_name,option_value sample_test_field_one,sample_test_field_value_one sample_test_field_two,sample_test_field_value_two """ When I run `wp option list --search="sample_test_field_" --format=csv --orderby=option_name --order=desc` Then STDOUT should be: """ option_name,option_value sample_test_field_two,sample_test_field_value_two sample_test_field_one,sample_test_field_value_one """ When I run `wp option list --search="sample_test_field_" --format=csv --orderby=option_value --order=asc` Then STDOUT should be: """ option_name,option_value sample_test_field_one,sample_test_field_value_one sample_test_field_two,sample_test_field_value_two """ When I run `wp option list --search="sample_test_field_" --format=csv --orderby=option_value --order=desc` Then STDOUT should be: """ option_name,option_value sample_test_field_two,sample_test_field_value_two sample_test_field_one,sample_test_field_value_one """ Scenario: Default list option without transient Given a WP install And I run `wp transient set wp_transient_flag wp_transient_flag` When I run `wp option list` Then STDOUT should not contain: """ wp_transient_flag """ And STDOUT should not contain: """ _transient """ And STDOUT should contain: """ siteurl """ Scenario: Using the `--unserialize` flag Given a WP install When I run `wp option add --format=json sample_test_field_one '{"value": 1}'` And I run `wp option list --search="sample_test_field_" --format=yaml --unserialize` Then STDOUT should be: """ --- - option_name: sample_test_field_one option_value: value: 1 """ Scenario: Using the `--autoload=on` flag Given a WP install And I run `wp option add sample_autoload_one 'sample_value_one' --autoload=yes` And I run `wp option add sample_autoload_two 'sample_value_two' --autoload=no` And I run `wp option add sample_autoload_three 'sample_value_three' --autoload=on` And I run `wp option add sample_autoload_four 'sample_value_four' --autoload=off` When I run `wp option list --autoload=on` Then STDOUT should not contain: """ sample_value_two """ And STDOUT should not contain: """ sample_value_four """ And STDOUT should contain: """ sample_value_one """ And STDOUT should contain: """ sample_value_three """ Scenario: Using the `--autoload=off` flag Given a WP install And I run `wp option add sample_autoload_one 'sample_value_one' --autoload=yes` And I run `wp option add sample_autoload_two 'sample_value_two' --autoload=no` And I run `wp option add sample_autoload_three 'sample_value_three' --autoload=on` And I run `wp option add sample_autoload_four 'sample_value_four' --autoload=off` When I run `wp option list --autoload=off` Then STDOUT should not contain: """ sample_value_one """ And STDOUT should not contain: """ sample_value_three """ And STDOUT should contain: """ sample_value_two """ And STDOUT should contain: """ sample_value_four """	5.89 KB	2025-09-06 07:07
📄 option-pluck-patch.feature Feature: Option commands have pluck and patch. @pluck Scenario: Nested values can be retrieved. Given a WP install And an input.json file: """ { "foo": "bar" } """ And I run `wp option update option_name --format=json < input.json` When I run `wp option pluck option_name foo` Then STDOUT should be: """ bar """ @pluck @pluck-deep Scenario: A nested value can be retrieved at any depth. Given a WP install And an input.json file: """ { "foo": { "bar": { "baz": "some value" } }, "foo.com": { "visitors": 999 } } """ And I run `wp option update option_name --format=json < input.json` When I run `wp option pluck option_name foo bar baz` Then STDOUT should be: """ some value """ When I run `wp option pluck option_name foo.com visitors` Then STDOUT should be: """ 999 """ @pluck @pluck-fail Scenario: Attempting to pluck a non-existent nested value fails. Given a WP install And I run `wp option update option_name '{ "key": "value" }' --format=json` When I run `wp option pluck option_name key` Then STDOUT should be: """ value """ When I try `wp option pluck option_name foo` Then STDOUT should be empty And the return code should be 1 @pluck @pluck-fail Scenario: Attempting to pluck from a primitive value fails. Given a WP install And I run `wp option update option_name simple-value` When I try `wp option pluck option_name foo` Then STDOUT should be empty And the return code should be 1 @pluck @pluck-numeric Scenario: A nested value can be retrieved from an integer key. Given a WP install And I run `wp option update option_name '[ "foo", "bar" ]' --format=json` When I run `wp option pluck option_name 0` Then STDOUT should be: """ foo """ @patch @patch-update @patch-arg Scenario: Nested values can be changed. Given a WP install And an input.json file: """ { "foo": "bar" } """ And I run `wp option update option_name --format=json < input.json` When I run `wp option patch update option_name foo baz` Then STDOUT should be: """ Success: Updated 'option_name' option. """ When I run `wp option get option_name --format=json` Then STDOUT should be JSON containing: """ { "foo": "baz" } """ @patch @patch-update @patch-stdin Scenario: Nested values can be set with a value from STDIN. Given a WP install And an input.json file: """ { "foo": { "bar": "baz" }, "bar": "bad" } """ And a patch file: """ new value """ And I run `wp option update option_name --format=json < input.json` When I run `wp option patch update option_name foo bar < patch` Then STDOUT should be: """ Success: Updated 'option_name' option. """ When I run `wp option get option_name --format=json` Then STDOUT should be JSON containing: """ { "foo": { "bar": "new value" }, "bar": "bad" } """ @patch @patch-update @patch-fail Scenario: Attempting to update a nested value fails if a parent's key does not exist. Given a WP install And an input.json file: """ { "foo": { "bar": "baz" }, "bar": "bad" } """ And I run `wp option update option_name --format=json < input.json` When I try `wp option patch update option_name foo not-a-key new-value` Then STDOUT should be empty And STDERR should contain: """ No data exists for key "not-a-key" """ And the return code should be 1 @patch @patch-delete Scenario: A key can be deleted from a nested value. Given a WP install And an input.json file: """ { "foo": { "bar": "baz", "abe": "lincoln" } } """ And I run `wp option update option_name --format=json < input.json` When I run `wp option patch delete option_name foo bar` Then STDOUT should be: """ Success: Updated 'option_name' option. """ When I run `wp option get option_name --format=json` Then STDOUT should be JSON containing: """ { "foo": { "abe": "lincoln" } } """ @patch @patch-fail @patch-delete @patch-delete-fail Scenario: A key cannot be deleted from a nested value from a non-existent key. Given a WP install And an input.json file: """ { "foo": { "bar": "baz" } } """ And I run `wp option update option_name --format=json < input.json` When I try `wp option patch delete option_name foo not-a-key` Then STDOUT should be empty And STDERR should contain: """ No data exists for key "not-a-key" """ And the return code should be 1 @patch @patch-insert Scenario: A new key can be inserted into a nested value. Given a WP install And I run `wp option update option_name '{}' --format=json` When I run `wp option patch insert option_name foo bar` Then STDOUT should be: """ Success: Updated 'option_name' option. """ When I run `wp option get option_name --format=json` Then STDOUT should be JSON containing: """ { "foo": "bar" } """ @patch @patch-fail @patch-insert @patch-insert-fail Scenario: A new key cannot be inserted into a non-nested value. Given a WP install And I run `wp option update option_name 'a simple value'` When I try `wp option patch insert option_name foo bar` Then STDOUT should be empty And STDERR should contain: """ Cannot create key "foo" """ And the return code should be 1 When I run `wp option get option_name` Then STDOUT should be: """ a simple value """ @patch @patch-numeric Scenario: A nested value can be updated using an integer key. Given a WP install And I run `wp option update option_name '[ "foo", "bar" ]' --format=json` When I run `wp option patch update option_name 0 new` Then STDOUT should be: """ Success: Updated 'option_name' option. """ When I run `wp option get option_name --format=json` Then STDOUT should be JSON containing: """ [ "new", "bar" ] """ @patch @pluck Scenario: An object value can be updated Given a WP install And a setup.php file: """ <?php $option = new stdClass; $option->test_mode = 0; $ret = update_option( 'wp_cli_test', $option ); """ And I run `wp eval-file setup.php` When I run `wp option pluck wp_cli_test test_mode` Then STDOUT should be: """ 0 """ When I run `wp option patch update wp_cli_test test_mode 1` Then STDOUT should be: """ Success: Updated 'wp_cli_test' option. """ When I run `wp option pluck wp_cli_test test_mode` Then STDOUT should be: """ 1 """ @patch Scenario: When we don't pass all necessary argumants. Given a WP install And an input.json file: """ { "foo": "bar" } """ And I run `wp option update option_name --format=json < input.json` When I try `wp option patch update option_name foo` Then STDERR should contain: """ Please provide value to update. """ And the return code should be 1 When I run `wp option patch update option_name foo 0` Then STDOUT should be: """ Success: Updated 'option_name' option. """	7.73 KB	2025-09-06 07:07
📄 option-set-autoload.feature Feature: Set 'autoload' value for an option Scenario: Option doesn't exist Given a WP install When I try `wp option set-autoload foo yes` Then STDERR should be: """ Error: Could not get 'foo' option. Does it exist? """ Scenario: Invalid 'autoload' value provided Given a WP install When I run `wp option add foo bar` Then STDOUT should contain: """ Success: """ When I try `wp option set-autoload foo invalid` Then STDERR should be: """ Error: Invalid value specified for positional arg. """ @less-than-wp-6.6 Scenario: Successfully updates autoload value Given a WP install When I run `wp option add foo bar` Then STDOUT should contain: """ Success: """ When I run `wp option get-autoload foo` Then STDOUT should be: """ yes """ When I run `wp option set-autoload foo no` Then STDOUT should be: """ Success: Updated autoload value for 'foo' option. """ When I run the previous command again Then STDOUT should be: """ Success: Autoload value passed for 'foo' option is unchanged. """ When I run `wp option get-autoload foo` Then STDOUT should be: """ no """ @require-wp-6.6 Scenario: Successfully updates autoload value Given a WP install When I run `wp option add foo bar` Then STDOUT should contain: """ Success: """ When I run `wp option get-autoload foo` Then STDOUT should be: """ on """ When I run `wp option set-autoload foo off` Then STDOUT should be: """ Success: Updated autoload value for 'foo' option. """ When I run the previous command again Then STDOUT should be: """ Success: Autoload value passed for 'foo' option is unchanged. """ When I run `wp option get-autoload foo` Then STDOUT should be: """ off """	1.96 KB	2025-05-25 12:40
📄 option.feature Feature: Manage WordPress options Scenario: Option CRUD Given a WP install # String values When I run `wp option add str_opt 'bar'` Then STDOUT should not be empty When I run `wp option get str_opt` Then STDOUT should be: """ bar """ When I run `wp option list` Then STDOUT should not be empty When I run `wp option list` Then STDOUT should contain: """ str_opt bar """ When I run `wp option list --autoload=off` Then STDOUT should not contain: """ str_opt bar """ When I run `wp option list --search='str_o'` Then STDOUT should be a table containing rows: \| option_name \| option_value \| \| str_opt \| bar \| When I run `wp option list --search='str_o' --format=total_bytes` Then STDOUT should be: """ 3 """ When I run `wp option list` Then STDOUT should contain: """ home https://example.com """ When I run `wp option add auto_opt --autoload=no 'bar'` Then STDOUT should not be empty When I run `wp option list --search='auto_opt' --autoload=off` Then STDOUT should not be empty When I run `wp option list \| grep -q "str_opt"` Then the return code should be 0 When I run `wp option delete str_opt` Then STDOUT should not be empty When I run `wp option add option_one "ONE"` And I run `wp option add option_two "TWO"` Then STDOUT should not be empty When I try `wp option delete option_one option_two option_three` Then STDOUT should be: """ Success: Deleted 'option_one' option. Success: Deleted 'option_two' option. """ And STDERR should be: """ Warning: Could not delete 'option_three' option. Does it exist? """ When I run `wp option list` Then STDOUT should not contain: """ str_opt bar """ When I try `wp option get str_opt` Then STDERR should be: """ Error: Could not get 'str_opt' option. Does it exist? """ # Integer values When I run `wp option update blog_public 1` Then STDOUT should not be empty When I run `wp option update blog_public 0` Then STDOUT should contain: """ Success: Updated 'blog_public' option. """ When I run the previous command again Then STDOUT should contain: """ Success: Value passed for 'blog_public' option is unchanged. """ When I run `wp option get blog_public` Then STDOUT should be: """ 0 """ # JSON values When I run `wp option set json_opt '[ 1, 2 ]' --format=json` Then STDOUT should not be empty When I run the previous command again Then STDOUT should not be empty When I run `wp option get json_opt --format=json` Then STDOUT should be: """ [1,2] """ # Reading from files Given a value.json file: """ { "foo": "bar", "list": [1, 2, 3] } """ When I run `wp option set foo --format=json < value.json` And I run `wp option get foo --format=json` Then STDOUT should be JSON containing: """ { "foo": "bar", "list": [1, 2, 3] } """ @require-wp-4.2 @less-than-wp-6.6 Scenario: Update autoload value for custom option Given a WP install And I run `wp option add hello world --autoload=no` When I run `wp option update hello universe` Then STDOUT should not be empty When I run `wp option list --search='hello' --fields=option_name,option_value,autoload` Then STDOUT should be a table containing rows: \| option_name \| option_value \| autoload \| \| hello \| universe \| no \| When I run `wp option update hello island --autoload=yes` Then STDOUT should not be empty When I run `wp option list --search='hello' --fields=option_name,option_value,autoload` Then STDOUT should be a table containing rows: \| option_name \| option_value \| autoload \| \| hello \| island \| yes \| @require-wp-6.6 Scenario: Update autoload value for custom option Given a WP install And I run `wp option add hello world --autoload=off` When I run `wp option update hello universe` Then STDOUT should not be empty When I run `wp option list --search='hello' --fields=option_name,option_value,autoload` Then STDOUT should be a table containing rows: \| option_name \| option_value \| autoload \| \| hello \| universe \| off \| When I run `wp option update hello island --autoload=on` Then STDOUT should not be empty When I run `wp option list --search='hello' --fields=option_name,option_value,autoload` Then STDOUT should be a table containing rows: \| option_name \| option_value \| autoload \| \| hello \| island \| on \| @require-wp-4.2 @less-than-wp-6.6 Scenario: Managed autoloaded options Given a WP install When I run `wp option add wp_autoload_1 enabled --autoload=yes` Then STDOUT should be: """ Success: Added 'wp_autoload_1' option. """ And STDERR should be empty When I run `wp option add wp_autoload_2 implicit` Then STDOUT should be: """ Success: Added 'wp_autoload_2' option. """ And STDERR should be empty When I run `wp option add wp_autoload_3 disabled --autoload=no` Then STDOUT should be: """ Success: Added 'wp_autoload_3' option. """ And STDERR should be empty When I run `wp option list --search='wp_autoload' --fields=option_name,option_value,autoload` Then STDOUT should be a table containing rows: \| option_name \| option_value \| autoload \| \| wp_autoload_1 \| enabled \| yes \| \| wp_autoload_2 \| implicit \| yes \| \| wp_autoload_3 \| disabled \| no \| When I run `wp option update wp_autoload_1 disabled --autoload=no` Then STDOUT should be: """ Success: Updated 'wp_autoload_1' option. """ And STDERR should be empty When I run `wp option update wp_autoload_2 implicit2` Then STDOUT should be: """ Success: Updated 'wp_autoload_2' option. """ And STDERR should be empty When I run `wp option update wp_autoload_3 enabled --autoload=yes` Then STDOUT should be: """ Success: Updated 'wp_autoload_3' option. """ And STDERR should be empty When I run `wp option list --search='wp_autoload' --fields=option_name,option_value,autoload` Then STDOUT should be a table containing rows: \| option_name \| option_value \| autoload \| \| wp_autoload_1 \| disabled \| no \| \| wp_autoload_2 \| implicit2 \| yes \| \| wp_autoload_3 \| enabled \| yes \| Scenario: Extra removetrailingslash sanitization for whitelisted options Given a WP install When I run `wp option update home 'http://localhost/'` Then STDOUT should be: """ Success: Updated 'home' option. """ When I run `wp option update home 'http://localhost/'` Then STDOUT should be: """ Success: Value passed for 'home' option is unchanged. """ Scenario: Bad values for autoload Given a WP install When I run `wp option add str_opt 'bar'` Then STDOUT should not be empty When I try `wp option list --search='auto_opt' --autoload` Then STDOUT should not be empty And STDERR should be: """ Warning: --autoload parameter needs a value """ And the return code should be 0 When I try `wp option list --search='auto_opt' --autoload=nope` Then STDOUT should be empty And STDERR should contain: """ Error: Value of '--autoload' should be """ And the return code should be 1 When I try `wp option add str_opt_foo 'bar' --autoload` Then STDOUT should not be empty And STDERR should be: """ Warning: --autoload parameter needs a value """ And the return code should be 0 When I try `wp option add str_opt_foo 'bar' --autoload=bad` Then STDOUT should be empty And STDERR should contain: """ Error: Parameter errors: """ And the return code should be 1	8.17 KB	2025-09-06 07:07
📄 post-create-duplicate.feature Feature: Create Duplicate WordPress post from existing posts. Background: Given a WP install Scenario: Generate duplicate post. When I run `wp term create category "Test Category" --porcelain` Then save STDOUT as {TERM_ID} When I run `wp term create post_tag "Test Tag" --porcelain` Then save STDOUT as {TAG_ID} When I run `wp post create --post_title='Test Duplicate Post' --post_category={TERM_ID} --porcelain` Then save STDOUT as {POST_ID} When I run `wp post term add {POST_ID} post_tag {TAG_ID} --by=id` Then STDOUT should contain: """ Success: Added term. """ When I run `wp post create --from-post={POST_ID} --porcelain` Then STDOUT should be a number And save STDOUT as {DUPLICATE_POST_ID} When I run `wp post get {DUPLICATE_POST_ID} --field=title` Then STDOUT should be: """ Test Duplicate Post """ When I run `wp post term list {DUPLICATE_POST_ID} category --field=term_id` Then STDOUT should be: """ {TERM_ID} """ When I run `wp post term list {DUPLICATE_POST_ID} post_tag --field=term_id` Then STDOUT should be: """ {TAG_ID} """ @require-wp-4.4 Scenario: Generate duplicate post with post metadata. When I run `wp post create --post_title='Test Post' --meta_input='{"key1":"value1","key2":"value2"}' --porcelain` Then save STDOUT as {POST_ID} When I run `wp post create --from-post={POST_ID} --porcelain` Then save STDOUT as {DUPLICATE_POST_ID} When I run `wp post meta list {DUPLICATE_POST_ID} --format=table` Then STDOUT should be a table containing rows: \| post_id \| meta_key \| meta_value \| \| {DUPLICATE_POST_ID} \| key1 \| value1 \| \| {DUPLICATE_POST_ID} \| key2 \| value2 \| Scenario: Generate duplicate page. When I run `wp post create --post_type="page" --post_title="Test Page" --post_content="Page Content" --porcelain` Then save STDOUT as {POST_ID} When I run `wp post create --from-post={POST_ID} --post_title="Duplicate Page" --porcelain` Then save STDOUT as {DUPLICATE_POST_ID} When I run `wp post list --post_type='page' --fields="title, content, type"` Then STDOUT should be a table containing rows: \| post_title \| post_content \| post_type \| \| Test Page \| Page Content \| page \| \| Duplicate Page \| Page Content \| page \| Scenario: Change type of duplicate post. When I run `wp post create --post_title='Test Post' --porcelain` Then save STDOUT as {POST_ID} When I run `wp post create --from-post={POST_ID} --post_type=page --porcelain` Then save STDOUT as {DUPLICATE_POST_ID} When I run `wp post get {DUPLICATE_POST_ID} --fields=type` Then STDOUT should be a table containing rows: \| Field \| Value \| \| post_type \| page \|	2.79 KB	2025-09-06 07:07
📄 post-generate.feature Feature: Generate new WordPress posts Background: Given a WP install Scenario: Generating posts When I run `echo "Content generated by wp post generate" \| wp post generate --count=1 --post_content` And I run `wp post list --field=post_content` Then STDOUT should contain: """ Content generated by wp post generate """ And STDERR should be empty @broken Scenario: Using --post-content requires STDIN input When I try `wp post generate --count=1 --post_content` Then STDERR should contain: """ Error: The parameter `post_content` reads from STDIN. """ Scenario: Generating posts by a specific author When I run `wp user create dummyuser dummy@example.com --porcelain` Then save STDOUT as {AUTHOR_ID} When I run `wp post generate --post_author={AUTHOR_ID} --post_type=post --count=16` And I run `wp post list --post_type=post --author={AUTHOR_ID} --format=count` Then STDOUT should contain: """ 16 """ Scenario: Generating pages When I run `wp post generate --post_type=page --max_depth=10` And I run `wp post list --post_type=page --field=post_parent` Then STDOUT should contain: """ 1 """ Scenario: Generating posts and outputting ids When I run `wp post generate --count=1 --format=ids` Then save STDOUT as {POST_ID} When I run `wp post update {POST_ID} --post_title="foo"` Then STDOUT should contain: """ Success: """ Scenario: Generating post and outputting title and name When I run `wp post generate --count=3 --post_title=Howdy!` And I run `wp post list --field=post_title --posts_per_page=4 --orderby=ID --order=asc` Then STDOUT should contain: """ Hello world! Howdy! Howdy! 2 Howdy! 3 """ And STDERR should be empty When I run `wp post list --field=post_name --posts_per_page=4 --orderby=ID --order=asc` Then STDOUT should contain: """ hello-world howdy howdy-2 howdy-3 """ And STDERR should be empty Scenario: Generating posts with post_date argument without time When I run `wp post generate --count=1 --post_date="2018-07-01"` And I run `wp post list --field=post_date` Then STDOUT should contain: """ 2018-07-01 00:00:00 """ When I run `wp post list --field=post_date_gmt` Then STDOUT should contain: """ 2018-07-01 00:00:00 """ Scenario: Generating posts with post_date argument with time When I run `wp post generate --count=1 --post_date="2018-07-02 02:21:05"` And I run `wp post list --field=post_date` Then STDOUT should contain: """ 2018-07-02 02:21:05 """ When I run `wp post list --field=post_date_gmt` Then STDOUT should contain: """ 2018-07-02 02:21:05 """ Scenario: Generating posts with post_date_gmt argument without time When I run `wp post generate --count=1 --post_date_gmt="2018-07-03"` And I run `wp post list --field=post_date` Then STDOUT should contain: """ 2018-07-03 00:00:00 """ When I run `wp post list --field=post_date_gmt` Then STDOUT should contain: """ 2018-07-03 00:00:00 """ Scenario: Generating posts with post_date_gmt argument with time When I run `wp post generate --count=1 --post_date_gmt="2018-07-04 12:34:56"` And I run `wp post list --field=post_date` Then STDOUT should contain: """ 2018-07-04 12:34:56 """ When I run `wp post list --field=post_date_gmt` Then STDOUT should contain: """ 2018-07-04 12:34:56 """ Scenario: Generating posts with post_date argument with hyphenated time When I run `wp post generate --count=1 --post_date="2018-07-05-17:17:17"` And I run `wp post list --field=post_date` Then STDOUT should contain: """ 2018-07-05 17:17:17 """ When I run `wp post list --field=post_date_gmt` Then STDOUT should contain: """ 2018-07-05 17:17:17 """ Scenario: Generating posts with post_date_gmt argument with hyphenated time When I run `wp post generate --count=1 --post_date_gmt="2018-07-06-12:12:12"` And I run `wp post list --field=post_date` Then STDOUT should contain: """ 2018-07-06 12:12:12 """ When I run `wp post list --field=post_date_gmt` Then STDOUT should contain: """ 2018-07-06 12:12:12 """ Scenario: Generating posts with different post_date & post_date_gmt argument without time When I run `wp post generate --count=1 --post_date="1999-12-31" --post_date_gmt="2000-01-01"` And I run `wp post list --field=post_date` Then STDOUT should contain: """ 1999-12-31 00:00:00 """ When I run `wp post list --field=post_date_gmt` Then STDOUT should contain: """ 2000-01-01 00:00:00 """ Scenario: Generating posts with different post_date & post_date_gmt argument with time When I run `wp post generate --count=1 --post_date="1999-12-31 11:11:00" --post_date_gmt="2000-01-01 02:11:00"` And I run `wp post list --field=post_date` Then STDOUT should contain: """ 1999-12-31 11:11:00 """ When I run `wp post list --field=post_date_gmt` Then STDOUT should contain: """ 2000-01-01 02:11:00 """ Scenario: Generating posts when the site timezone is ahead of UTC When I run `wp option update timezone_string "Europe/Helsinki"` And I run `wp post delete 1 --force` And I run `wp post list --field=post_status` Then STDOUT should be empty When I run `wp post generate --count=1` And I run `wp post list --field=post_status` Then STDOUT should be: """ publish """	5.71 KB	2025-09-06 07:07
📄 post-meta-clean-duplicates.feature Feature: Clean up duplicate post meta values Scenario: Clean up duplicate post meta values. Given a WP install And a session_no file: """ n """ And a session_yes file: """ y """ When I run `wp post meta add 1 foo bar` Then STDOUT should be: """ Success: Added custom field. """ When I run the previous command again Then the return code should be 0 When I run the previous command again Then the return code should be 0 When I run `wp post meta list 1 --keys=foo` Then STDOUT should be a table containing rows: \| post_id \| meta_key \| meta_value \| \| 1 \| foo \| bar \| \| 1 \| foo \| bar \| \| 1 \| foo \| bar \| When I run `wp post meta clean-duplicates 1 foo < session_no` # Check for contains only, as the string contains a trailing space. Then STDOUT should contain: """ Are you sure you want to delete 2 duplicate meta values and keep 1 valid meta value? [y/n] """ When I run `wp post meta list 1 --keys=foo --format=count` Then STDOUT should be: """ 3 """ When I run `wp post meta clean-duplicates 1 foo < session_yes` Then STDOUT should contain: """ Cleaned up duplicate 'foo' meta values. """ When I try the previous command again Then STDOUT should contain: """ Success: Nothing to clean up: found 1 valid meta value and 0 duplicates. """ When I try `wp post meta clean-duplicates 1 food` Then STDERR should be: """ Error: No meta values found for 'food'. """ And the return code should be 1	1.67 KB	2025-05-25 12:40
📄 post-meta.feature Feature: Manage post custom fields Scenario: Postmeta CRUD Given a WP install When I run `wp post-meta add 1 foo 'bar'` Then STDOUT should not be empty When I run `wp post-meta get 1 foo` Then STDOUT should be: """ bar """ When I try `wp post meta get 999999 foo` Then STDERR should be: """ Error: Could not find the post with ID 999999. """ And the return code should be 1 When I run `wp post-meta set 1 foo '[ "1", "2" ]' --format=json` Then STDOUT should not be empty When I run the previous command again Then STDOUT should be: """ Success: Value passed for custom field 'foo' is unchanged. """ When I run `wp post-meta get 1 foo --format=json` Then STDOUT should be: """ ["1","2"] """ When I run `echo 'via STDIN' \| wp post-meta set 1 foo` And I run `wp post-meta get 1 foo` Then STDOUT should be: """ via STDIN """ When I run `wp post-meta delete 1 foo` Then STDOUT should not be empty When I try `wp post-meta get 1 foo` Then the return code should be 1 Scenario: List post meta Given a WP install When I run `wp post meta add 1 apple banana` And I run `wp post meta add 1 apple banana` Then STDOUT should not be empty When I run `wp post meta set 1 banana '["apple", "apple"]' --format=json` Then STDOUT should not be empty When I run `wp post meta list 1` Then STDOUT should be a table containing rows: \| post_id \| meta_key \| meta_value \| \| 1 \| apple \| banana \| \| 1 \| apple \| banana \| \| 1 \| banana \| a:2:{i:0;s:5:"apple";i:1;s:5:"apple";} \| When I run `wp post meta list 1 --unserialize` Then STDOUT should be a table containing rows: \| post_id \| meta_key \| meta_value \| \| 1 \| apple \| banana \| \| 1 \| apple \| banana \| \| 1 \| banana \| ["apple","apple"] \| When I run `wp post meta list 1 --orderby=id --order=desc` Then STDOUT should be a table containing rows: \| post_id \| meta_key \| meta_value \| \| 1 \| banana \| a:2:{i:0;s:5:"apple";i:1;s:5:"apple";} \| \| 1 \| apple \| banana \| \| 1 \| apple \| banana \| When I run `wp post meta list 1 --orderby=id --order=desc --unserialize` Then STDOUT should be a table containing rows: \| post_id \| meta_key \| meta_value \| \| 1 \| banana \| ["apple","apple"] \| \| 1 \| apple \| banana \| \| 1 \| apple \| banana \| When I run `wp post meta list 1 --orderby=meta_key --order=asc` Then STDOUT should be a table containing rows: \| post_id \| meta_key \| meta_value \| \| 1 \| apple \| banana \| \| 1 \| apple \| banana \| \| 1 \| banana \| a:2:{i:0;s:5:"apple";i:1;s:5:"apple";} \| When I run `wp post meta list 1 --orderby=meta_key --order=asc --unserialize` Then STDOUT should be a table containing rows: \| post_id \| meta_key \| meta_value \| \| 1 \| apple \| banana \| \| 1 \| apple \| banana \| \| 1 \| banana \| ["apple","apple"] \| When I run `wp post meta list 1 --orderby=meta_key --order=desc` Then STDOUT should be a table containing rows: \| post_id \| meta_key \| meta_value \| \| 1 \| banana \| a:2:{i:0;s:5:"apple";i:1;s:5:"apple";} \| \| 1 \| apple \| banana \| \| 1 \| apple \| banana \| When I run `wp post meta list 1 --orderby=meta_key --order=desc --unserialize` Then STDOUT should be a table containing rows: \| post_id \| meta_key \| meta_value \| \| 1 \| banana \| ["apple","apple"] \| \| 1 \| apple \| banana \| \| 1 \| apple \| banana \| When I run `wp post meta list 1 --orderby=meta_value --order=asc` Then STDOUT should be a table containing rows: \| post_id \| meta_key \| meta_value \| \| 1 \| apple \| banana \| \| 1 \| apple \| banana \| \| 1 \| banana \| a:2:{i:0;s:5:"apple";i:1;s:5:"apple";} \| When I run `wp post meta list 1 --orderby=meta_value --order=asc --unserialize` Then STDOUT should be a table containing rows: \| post_id \| meta_key \| meta_value \| \| 1 \| apple \| banana \| \| 1 \| apple \| banana \| \| 1 \| banana \| ["apple","apple"] \| When I run `wp post meta list 1 --orderby=meta_value --order=desc` Then STDOUT should be a table containing rows: \| post_id \| meta_key \| meta_value \| \| 1 \| banana \| a:2:{i:0;s:5:"apple";i:1;s:5:"apple";} \| \| 1 \| apple \| banana \| \| 1 \| apple \| banana \| When I run `wp post meta list 1 --orderby=meta_value --order=desc --unserialize` Then STDOUT should be a table containing rows: \| post_id \| meta_key \| meta_value \| \| 1 \| banana \| ["apple","apple"] \| \| 1 \| apple \| banana \| \| 1 \| apple \| banana \| Scenario: Delete all post meta Given a WP install When I run `wp post meta add 1 apple banana` And I run `wp post meta add 1 _foo banana` Then STDOUT should not be empty When I run `wp post meta list 1 --format=count` Then STDOUT should be: """ 2 """ When I try `wp post meta delete 1` Then STDERR should be: """ Error: Please specify a meta key, or use the --all flag. """ And the return code should be 1 When I run `wp post meta delete 1 --all` Then STDOUT should contain: """ Deleted 'apple' custom field. Deleted '_foo' custom field. Success: Deleted all custom fields. """ When I run `wp post meta list 1 --format=count` Then STDOUT should be: """ 0 """ Scenario: List post meta with a null value Given a WP install And a setup.php file: """ <?php update_post_meta( 1, 'foo', NULL ); """ And I run `wp eval-file setup.php` When I run `wp post meta list 1` Then STDOUT should be a table containing rows: \| post_id \| meta_key \| meta_value \| \| 1 \| foo \| \| Scenario: Make sure WordPress receives the slashed data it expects in meta fields Given a WP install When I run `wp post-meta add 1 foo 'My\Meta'` Then STDOUT should not be empty When I run `wp post-meta get 1 foo` Then STDOUT should be: """ My\Meta """ When I run `wp post-meta update 1 foo 'My\New\Meta'` Then STDOUT should be: """ Success: Updated custom field 'foo'. """ When I run the previous command again Then STDOUT should be: """ Success: Value passed for custom field 'foo' is unchanged. """ When I run `wp post-meta get 1 foo` Then STDOUT should be: """ My\New\Meta """ Scenario: List post meta with or without single flag Given a WP install When I run `wp post meta add 1 apple banana` And I run `wp post meta add 1 apple mango` Then STDOUT should not be empty When I run `wp post meta get 1 apple` Then STDOUT should be: """ banana """ When I run `wp post meta get 1 apple --single` Then STDOUT should be: """ banana """ When I run `wp post meta get 1 apple --no-single` Then STDOUT should be: """ array ( 0 => 'banana', 1 => 'mango', ) """ When I run `wp post meta get 1 apple --no-single --format=json` Then STDOUT should be: """ ["banana","mango"] """ @pluck Scenario: Nested values can be retrieved. Given a WP install And an input.json file: """ { "foo": "bar" } """ And I run `wp post meta set 1 meta-key --format=json < input.json` When I run `wp post meta pluck 1 meta-key foo` Then STDOUT should be: """ bar """ @pluck @pluck-deep Scenario: A nested value can be retrieved at any depth. Given a WP install And an input.json file: """ { "foo": { "bar": { "baz": "some value" } }, "foo.com": { "visitors": 999 } } """ And I run `wp post meta set 1 meta-key --format=json < input.json` When I run `wp post meta pluck 1 meta-key foo bar baz` Then STDOUT should be: """ some value """ When I run `wp post meta pluck 1 meta-key foo.com visitors` Then STDOUT should be: """ 999 """ @pluck @pluck-fail Scenario: Attempting to pluck a non-existent nested value fails. Given a WP install And I run `wp post meta set 1 meta-key '{ "key": "value" }' --format=json` When I run `wp post meta pluck 1 meta-key key` Then STDOUT should be: """ value """ When I try `wp post meta pluck 1 meta-key foo` Then STDOUT should be empty And the return code should be 1 @pluck @pluck-fail Scenario: Attempting to pluck from a primitive value fails. Given a WP install And I run `wp post meta set 1 meta-key simple-value` When I try `wp post meta pluck 1 meta-key foo` Then STDOUT should be empty And the return code should be 1 @pluck @pluck-numeric Scenario: A nested value can be retrieved from an integer key. Given a WP install And I run `wp post meta set 1 meta-key '[ "foo", "bar" ]' --format=json` When I run `wp post meta pluck 1 meta-key 0` Then STDOUT should be: """ foo """ @patch @patch-update @patch-arg Scenario: Nested values can be changed. Given a WP install And an input.json file: """ { "foo": "bar" } """ And I run `wp post meta set 1 meta-key --format=json < input.json` When I run `wp post meta patch update 1 meta-key foo baz` Then STDOUT should be: """ Success: Updated custom field 'meta-key'. """ When I run `wp post meta get 1 meta-key --format=json` Then STDOUT should be JSON containing: """ { "foo": "baz" } """ @patch @patch-update @patch-stdin Scenario: Nested values can be set with a value from STDIN. Given a WP install And an input.json file: """ { "foo": { "bar": "baz" }, "bar": "bad" } """ And a patch file: """ new value """ And I run `wp post meta set 1 meta-key --format=json < input.json` When I run `wp post meta patch update 1 meta-key foo bar < patch` Then STDOUT should be: """ Success: Updated custom field 'meta-key'. """ When I run `wp post meta get 1 meta-key --format=json` Then STDOUT should be JSON containing: """ { "foo": { "bar": "new value" }, "bar": "bad" } """ @patch @patch-update @patch-fail Scenario: Attempting to update a nested value fails if a parent's key does not exist. Given a WP install And an input.json file: """ { "foo": { "bar": "baz" }, "bar": "bad" } """ And I run `wp post meta set 1 meta-key --format=json < input.json` When I try `wp post meta patch update 1 meta-key foo not-a-key new-value` Then STDOUT should be empty And STDERR should contain: """ No data exists for key "not-a-key" """ And the return code should be 1 @patch @patch-delete Scenario: A key can be deleted from a nested value. Given a WP install And an input.json file: """ { "foo": { "bar": "baz", "abe": "lincoln" } } """ And I run `wp post meta set 1 meta-key --format=json < input.json` When I run `wp post meta patch delete 1 meta-key foo bar` Then STDOUT should be: """ Success: Updated custom field 'meta-key'. """ When I run `wp post meta get 1 meta-key --format=json` Then STDOUT should be JSON containing: """ { "foo": { "abe": "lincoln" } } """ @patch @patch-fail @patch-delete @patch-delete-fail Scenario: A key cannot be deleted from a nested value from a non-existent key. Given a WP install And an input.json file: """ { "foo": { "bar": "baz" } } """ And I run `wp post meta set 1 meta-key --format=json < input.json` When I try `wp post meta patch delete 1 meta-key foo not-a-key` Then STDOUT should be empty And STDERR should contain: """ No data exists for key "not-a-key" """ And the return code should be 1 @patch @patch-insert Scenario: A new key can be inserted into a nested value. Given a WP install And I run `wp post meta set 1 meta-key '{}' --format=json` When I run `wp post meta patch insert 1 meta-key foo bar` Then STDOUT should be: """ Success: Updated custom field 'meta-key'. """ When I run `wp post meta get 1 meta-key --format=json` Then STDOUT should be JSON containing: """ { "foo": "bar" } """ @patch @patch-fail @patch-insert @patch-insert-fail Scenario: A new key cannot be inserted into a non-nested value. Given a WP install And I run `wp post meta set 1 meta-key 'a simple value'` When I try `wp post meta patch insert 1 meta-key foo bar` Then STDOUT should be empty And STDERR should contain: """ Cannot create key "foo" """ And the return code should be 1 When I run `wp post meta get 1 meta-key` Then STDOUT should be: """ a simple value """ @patch @patch-numeric Scenario: A nested value can be updated using an integer key. Given a WP install And I run `wp post meta set 1 meta-key '[ "foo", "bar" ]' --format=json` When I run `wp post meta patch update 1 meta-key 0 new` Then STDOUT should be: """ Success: Updated custom field 'meta-key'. """ When I run `wp post meta get 1 meta-key --format=json` Then STDOUT should be JSON containing: """ [ "new", "bar" ] """	14.7 KB	2025-09-06 07:07
📄 post-term.feature Feature: Manage post term Scenario: Postterm CRUD Given a WP install When I run `wp post term add 1 category foo` Then STDOUT should be: """ Success: Added term. """ When I run `wp post term list 1 category --fields=name,slug,taxonomy` Then STDOUT should be a table containing rows: \| name \| slug \| taxonomy \| \| foo \| foo \| category \| When I run `wp post term add 1 category bar` Then STDOUT should be: """ Success: Added term. """ When I run `wp post term list 1 category --fields=name,slug,taxonomy` Then STDOUT should be a table containing rows: \| name \| slug \| taxonomy \| \| foo \| foo \| category \| \| bar \| bar \| category \| When I run `wp post term list 1 category --format=ids` Then STDOUT should be: """ 3 2 1 """ When I try `wp post term list 1 foo2` Then STDERR should be: """ Error: Invalid taxonomy foo2. """ And the return code should be 1 When I run `wp post term set 1 category new` Then STDOUT should be: """ Success: Set term. """ When I run `wp post term list 1 category --fields=name,slug,taxonomy --format=count` Then STDOUT should be: """ 1 """ When I run `wp post term list 1 category --field=slug` Then STDOUT should be: """ new """ When I run `wp post term remove 1 category new` Then STDOUT should be: """ Success: Removed term. """ When I run `wp post term list 1 category --fields=name,slug,taxonomy --format=count` Then STDOUT should be: """ 0 """ Scenario: Multiple post term Given a WP install When I run `wp post term add 1 category apple` And I run `wp post term add 1 category apple` Then STDOUT should be: """ Success: Added term. """ When I run `wp post term set 1 category apple1 apple2` Then STDOUT should be: """ Success: Set terms. """ When I run `wp post term list 1 category --fields=name,slug,taxonomy` Then STDOUT should be a table containing rows: \| name \| slug \| taxonomy \| \| apple1 \| apple1 \| category \| \| apple2 \| apple2 \| category \| Scenario: Invalid Post ID Given a WP install When I try `wp post term add 99999 category boo` Then the return code should be 1 And STDERR should be: """ Error: Could not find the post with ID 99999. """ Scenario: Postterm Add invalid tax Given a WP install When I try `wp post term add 1 foo2 boo` Then the return code should be 1 And STDERR should be: """ Error: Invalid taxonomy foo2. """ Scenario: Add terms by term id Given a WP install When I run `wp term create post_tag 3 --porcelain` Then STDOUT should be: """ 2 """ When I run `wp term create post_tag 4 --porcelain` Then STDOUT should be: """ 3 """ When I run `wp term create post_tag 2 --porcelain` Then STDOUT should be: """ 4 """ When I run `wp post term add 1 post_tag 4` Then STDOUT should contain: """ Success: Added term. """ When I run `wp post term add 1 post_tag 2` Then STDOUT should contain: """ Success: Added term. """ When I run `wp post term list 1 post_tag --fields=term_id,name,slug` Then STDOUT should be a table containing rows: \| term_id \| name \| slug \| \| 4 \| 2 \| 2 \| \| 3 \| 4 \| 4 \| When I run `wp post term remove 1 post_tag 4 2` Then STDOUT should be: """ Success: Removed terms. """ When I run `wp post term add 1 post_tag 4 --by=id` Then STDOUT should contain: """ Success: Added term. """ When I run `wp post term list 1 post_tag --fields=term_id,name,slug` Then STDOUT should be a table containing rows: \| term_id \| name \| slug \| \| 4 \| 2 \| 2 \| When I run `wp post term add 1 post_tag 3 --by=slug` Then STDOUT should contain: """ Success: Added term. """ When I run `wp post term list 1 post_tag --fields=term_id,name,slug` Then STDOUT should be a table containing rows: \| term_id \| name \| slug \| \| 2 \| 3 \| 3 \| \| 4 \| 2 \| 2 \| When I run `wp post term remove 1 post_tag 2 --by=id` Then STDOUT should be: """ Success: Removed term. """ When I run `wp post term list 1 post_tag --fields=term_id,name,slug` Then STDOUT should be a table containing rows: \| term_id \| name \| slug \| \| 4 \| 2 \| 2 \| When I run `wp post term set 1 post_tag 3 --by=id` Then STDOUT should contain: """ Success: Set term. """ When I run `wp post term list 1 post_tag --fields=term_id,name,slug` Then STDOUT should be a table containing rows: \| term_id \| name \| slug \| \| 3 \| 4 \| 4 \| Scenario: Remove all terms from post Given a WP install When I run `wp post term remove 1 category --all` Then STDOUT should be: """ Success: Removed all terms and set default term. """ When I try `wp post term remove 1 category cat1 cat2 --all` Then STDERR should be: """ Error: No need to specify terms while removing all terms. """ And the return code should be 1	5.37 KB	2025-05-25 12:40
📄 post-type.feature Feature: Manage WordPress post types Background: Given a WP install Scenario: Listing post types When I run `wp post-type list --format=csv` Then STDOUT should be CSV containing: \| name \| label \| description \| hierarchical \| public \| capability_type \| \| post \| Posts \| \| \| 1 \| post \| \| page \| Pages \| \| 1 \| 1 \| page \| @require-wp-5.0 Scenario: Listing post types with count When I run `wp post-type list --fields=name,count --format=csv` Then STDOUT should be CSV containing: \| name \| count \| \| post \| 1 \| \| page \| 2 \| Scenario: Get a post type When I try `wp post-type get invalid-post-type` Then STDERR should be: """ Error: Post type invalid-post-type doesn't exist. """ And the return code should be 1 When I run `wp post-type get page` Then STDOUT should be a table containing rows: \| Field \| Value \| \| name \| page \| \| label \| Pages \| And STDOUT should contain: """ supports """ And STDOUT should contain: """ "title":true """ @require-wp-5.0 Scenario: Get a post type with count When I try `wp post-type get page --fields=name,count` Then STDOUT should be a table containing rows: \| Field \| Value \| \| name \| page \| \| count \| 2 \|	1.46 KB	2025-05-25 12:40
📄 post-url-to-id.feature Feature: Get the post ID for a given URL Background: Given a WP install Scenario: Get the post ID for a given URL When I run `wp post get 1 --field=url` Then STDOUT should be: """ https://example.com/?p=1 """ And save STDOUT as {POST_URL} When I run `wp post url-to-id {POST_URL}` Then STDOUT should contain: """ 1 """ When I try `wp post url-to-id 'https://example.com/?p=404'` Then STDERR should contain: """ Could not get post with url https://example.com/?p=404. """	564 B	2025-05-25 12:40
📄 post.feature Feature: Manage WordPress posts Background: Given a WP install Scenario: Creating/updating/deleting posts When I run `wp post create --post_title='Test post' --porcelain` Then STDOUT should be a number And save STDOUT as {POST_ID} When I run `wp post create --post_title='Test post' --post_type="test" --porcelain` Then STDOUT should be a number And save STDOUT as {CUSTOM_POST_ID} When I run `wp post exists {CUSTOM_POST_ID}` Then STDOUT should be: """ Success: Post with ID {CUSTOM_POST_ID} exists. """ And the return code should be 0 When I try `wp post exists 1000` Then STDOUT should be empty And the return code should be 1 When I run `wp post update {POST_ID} --post_title='Updated post'` Then STDOUT should be: """ Success: Updated post {POST_ID}. """ When I run `wp post delete {POST_ID}` Then STDOUT should be: """ Success: Trashed post {POST_ID}. """ When I run the previous command again Then STDOUT should be: """ Success: Deleted post {POST_ID}. """ When I try `wp post delete {CUSTOM_POST_ID}` Then STDERR should be: """ Warning: Posts of type 'test' do not support being sent to trash. Please use the --force flag to skip trash and delete them permanently. """ When I run `wp post delete {CUSTOM_POST_ID} --force` Then STDOUT should be: """ Success: Deleted post {CUSTOM_POST_ID}. """ When I try the previous command again Then the return code should be 1 Scenario: Updating an invalid post should exit with an error Given a WP install When I try `wp post update 22 --post_title=Foo` Then the return code should be 1 And STDERR should contain: """ Warning: Invalid post ID. """ Scenario: Setting post categories When I run `wp term create category "First Category" --porcelain` Then save STDOUT as {TERM_ID} When I run `wp term create category "Second Category" --porcelain` Then save STDOUT as {SECOND_TERM_ID} When I run `wp post create --post_title="Test category" --post_category="First Category" --porcelain` Then STDOUT should be a number And save STDOUT as {POST_ID} When I run `wp post term list {POST_ID} category --field=term_id` Then STDOUT should be: """ {TERM_ID} """ When I run `wp post update {POST_ID} --post_category={SECOND_TERM_ID}` Then STDOUT should be: """ Success: Updated post {POST_ID}. """ When I run `wp post term list {POST_ID} category --field=term_id` Then STDOUT should be: """ {SECOND_TERM_ID} """ When I run `wp post update {POST_ID} --post_category='Uncategorized,{TERM_ID},Second Category'` Then STDOUT should be: """ Success: Updated post {POST_ID}. """ When I run `wp post term list {POST_ID} category --field=term_id` And save STDOUT as {MULTI_CATEGORIES_STDOUT} Then STDOUT should contain: """ {TERM_ID} """ And STDOUT should contain: """ {SECOND_TERM_ID} """ And STDOUT should contain: """ 1 """ # Blank categories with non-blank ignored. When I run `wp post update {POST_ID} --post_category='Uncategorized, ,{TERM_ID},Second Category,'` Then STDOUT should be: """ Success: Updated post {POST_ID}. """ When I run `wp post term list {POST_ID} category --field=term_id` Then STDOUT should be: """ {MULTI_CATEGORIES_STDOUT} """ # Zero category same as default Uncategorized (1) category. When I try `wp post update {POST_ID} --post_category=0` Then STDOUT should be: """ Success: Updated post {POST_ID}. """ When I run `wp post term list {POST_ID} category --field=term_id` Then STDOUT should be: """ 1 """ # Blank category/categories same as default Uncategorized (1) category. When I try `wp post update {POST_ID} --post_category=,` Then STDOUT should be: """ Success: Updated post {POST_ID}. """ When I run `wp post term list {POST_ID} category --field=term_id` Then STDOUT should be: """ 1 """ # Null category same as no categories. When I try `wp post update {POST_ID} --post_category=' '` Then STDOUT should be: """ Success: Updated post {POST_ID}. """ When I run `wp post term list {POST_ID} category --field=term_id` Then STDOUT should be empty # Non-existent category. When I try `wp post update {POST_ID} --post_category=test` Then STDERR should be: """ Error: No such post category 'test'. """ When I try `wp post create --post_title="Non-existent Category" --post_category={SECOND_TERM_ID},Test --porcelain` Then STDERR should be: """ Error: No such post category 'Test'. """ # Error on first non-existent category found. When I try `wp post create --post_title="More than one non-existent Category" --post_category={SECOND_TERM_ID},Test,Bad --porcelain` Then STDERR should be: """ Error: No such post category 'Test'. """ Scenario: Creating/getting/editing posts Given a content.html file: """ This is some content. <script> alert('This should not be stripped.'); </script> """ And a create-post.sh file: """ cat content.html \| wp post create --post_title='Test post' --post_excerpt="A multiline excerpt" --porcelain - """ When I run `bash create-post.sh` Then STDOUT should be a number And save STDOUT as {POST_ID} When I run `wp post get --field=excerpt {POST_ID}` Then STDOUT should be: """ A multiline excerpt """ When I run `wp post get --field=content {POST_ID} \| diff -Bu content.html -` Then STDOUT should be empty When I run `wp post get --format=table {POST_ID}` Then STDOUT should be a table containing rows: \| Field \| Value \| \| ID \| {POST_ID} \| \| post_title \| Test post \| \| post_name \| \| \| post_type \| post \| When I run `wp post get {POST_ID} --format=csv --fields=post_title,type \| wc -l \| tr -d ' '` Then STDOUT should be: """ 3 """ When I run `wp post get --format=json {POST_ID}` Then STDOUT should be JSON containing: """ { "ID": {POST_ID}, "post_title": "Test post" } """ When I try `EDITOR='ex -i NONE -c q!' wp post edit {POST_ID}` Then STDERR should contain: """ No change made to post content. """ And the return code should be 0 When I run `EDITOR='ex -i NONE -c %s/content/bunkum -c wq' wp post edit {POST_ID}` Then STDERR should be empty And STDOUT should contain: """ Updated post {POST_ID}. """ When I run `wp post get --field=content {POST_ID}` Then STDOUT should contain: """ This is some bunkum. """ When I run `wp post url 1 {POST_ID}` Then STDOUT should be: """ https://example.com/?p=1 https://example.com/?p={POST_ID} """ When I run `wp post get 1 --field=url` Then STDOUT should be: """ https://example.com/?p=1 """ Scenario: Update a post from file or STDIN Given a content.html file: """ Oh glorious CLI """ And a content-2.html file: """ Let it be the weekend """ When I run `wp post create --post_title="Testing update via STDIN" --porcelain` Then STDOUT should be a number And save STDOUT as {POST_ID} When I run `cat content.html \| wp post update {POST_ID} -` Then STDOUT should contain: """ Success: Updated post {POST_ID} """ When I run `wp post get --field=post_content {POST_ID}` Then STDOUT should be: """ Oh glorious CLI """ When I run `wp post create --post_title="Testing update via STDIN. Again!" --porcelain` Then STDOUT should be a number And save STDOUT as {POST_ID_TWO} When I run `wp post update {POST_ID} {POST_ID_TWO} content-2.html` Then STDOUT should contain: """ Success: Updated post {POST_ID_TWO} """ When I run `wp post get --field=post_content {POST_ID_TWO}` Then STDOUT should be: """ Let it be the weekend """ When I try `wp post update {POST_ID} invalid-file.html` Then STDERR should be: """ Error: Unable to read content from 'invalid-file.html'. """ And the return code should be 1 Scenario: Creating/listing posts When I run `wp post create --post_title='Publish post' --post_content='Publish post content' --post_status='publish' --porcelain` Then STDOUT should be a number And save STDOUT as {POST_ID} When I run `wp post create --post_title='Draft post' --post_content='Draft post content' --post_status='draft' --porcelain` Then STDOUT should be a number When I run `wp post list --post_type='post' --fields=post_title,post_name,post_status --format=csv` Then STDOUT should be CSV containing: \| post_title \| post_name \| post_status \| \| Publish post \| publish-post \| publish \| \| Draft post \| \| draft \| When I run `wp post list --post_type='post' --fields=title,name,status --format=csv` Then STDOUT should be CSV containing: \| post_title \| post_name \| post_status \| \| Publish post \| publish-post \| publish \| \| Draft post \| \| draft \| When I run `wp post list --post_type='post' --fields="title, name, status" --format=csv` Then STDOUT should be CSV containing: \| post_title \| post_name \| post_status \| \| Publish post \| publish-post \| publish \| \| Draft post \| \| draft \| When I run `wp post list --post__in={POST_ID} --format=count` Then STDOUT should be: """ 1 """ When I run `wp post list --post_type='page' --field=title` Then STDOUT should contain: """ Sample Page """ When I run `wp post list --post_type=any --fields=post_title,post_name,post_status --format=csv --orderby=post_title --order=ASC` Then STDOUT should be CSV containing: \| post_title \| post_name \| post_status \| \| Draft post \| \| draft \| \| Hello world! \| hello-world \| publish \| \| Publish post \| publish-post \| publish \| \| Sample Page \| sample-page \| publish \| Scenario: List posts with date query When I run `wp post create --post_title='old post' --post_date='2023-01-24T09:52:00.000Z'` And I run `wp post create --post_title='new post' --post_date='2025-01-24T09:52:00.000Z'` And I run `wp post list --field=post_title --date_query='{"before":{"year":"2024"}}'` Then STDOUT should contain: """ old post """ And STDOUT should not contain: """ new post """ Scenario: List posts with tax query When I run `wp term create category "First Category" --porcelain` And I run `wp term create category "Second Category" --porcelain` And I run `wp post create --post_title='post-1' --post_category="First Category"` And I run `wp post create --post_title='post-2' --post_category="Second Category"` And I run `wp post create --post_title='new post' --post_date='2025-01-24T09:52:00.000Z'` And I run `wp post list --field=post_title --tax_query='[{"taxonomy":"category","field":"slug","terms":"first-category"}]'` Then STDOUT should contain: """ post-1 """ And STDOUT should not contain: """ post-2 """ Scenario: Update categories on a post When I run `wp term create category "Test Category" --porcelain` Then save STDOUT as {TERM_ID} When I run `wp post update 1 --post_category={TERM_ID}` And I run `wp post term list 1 category --format=json --fields=name` Then STDOUT should be: """ [{"name":"Test Category"}] """ Scenario: Make sure WordPress receives the slashed data it expects When I run `wp post create --post_title='My\Post' --porcelain` Then save STDOUT as {POST_ID} When I run `wp post get {POST_ID} --field=title` Then STDOUT should be: """ My\Post """ When I run `wp post update {POST_ID} --post_content='var isEmailValid = /^\S+@\S+.\S+$/.test(email);'` Then STDOUT should not be empty When I run `wp post get {POST_ID} --field=content` Then STDOUT should be: """ var isEmailValid = /^\S+@\S+.\S+$/.test(email); """ @require-wp-4.4 Scenario: Creating/updating posts with meta keys When I run `wp post create --post_title='Test Post' --post_content='Test post content' --meta_input='{"key1":"value1","key2":"value2"}' --porcelain` Then STDOUT should be a number And save STDOUT as {POST_ID} When I run `wp post meta list {POST_ID} --format=table` Then STDOUT should be a table containing rows: \| post_id \| meta_key \| meta_value \| \| {POST_ID} \| key1 \| value1 \| \| {POST_ID} \| key2 \| value2 \| When I run `wp post update {POST_ID} --meta_input='{"key2":"value2b","key3":"value3"}'` And I run `wp post meta list {POST_ID} --format=table` Then STDOUT should be a table containing rows: \| post_id \| meta_key \| meta_value \| \| {POST_ID} \| key1 \| value1 \| \| {POST_ID} \| key2 \| value2b \| \| {POST_ID} \| key3 \| value3 \| When I run `wp post list --field=post_title --meta_query='[{"key":"key2","value":"value2b"}]'` Then STDOUT should contain: """ Test Post """ @less-than-wp-4.4 Scenario: Creating/updating posts with meta keys for WP < 4.4 has no effect so should give warning When I try `wp post create --post_title='Test Post' --post_content='Test post content' --meta_input='{"key1":"value1","key2":"value2"}' --porcelain` Then the return code should be 0 And STDOUT should be a number And save STDOUT as {POST_ID} And STDERR should be: """ Warning: The 'meta_input' field was only introduced in WordPress 4.4 so will have no effect. """ When I run `wp post meta list {POST_ID} --format=count` Then STDOUT should be: """ 0 """ When I try `wp post update {POST_ID} --meta_input='{"key2":"value2b","key3":"value3"}'` Then the return code should be 0 And STDERR should be: """ Warning: The 'meta_input' field was only introduced in WordPress 4.4 so will have no effect. """ And STDOUT should be: """ Success: Updated post {POST_ID}. """ When I run `wp post meta list {POST_ID} --format=count` Then STDOUT should be: """ 0 """ Scenario: Publishing a post and setting a date fails if the edit_date flag is not passed. Given a WP install When I run `wp post create --post_title='test' --porcelain` Then save STDOUT as {POST_ID} When I run `wp post update {POST_ID} --post_date='2005-01-24T09:52:00.000Z' --post_status='publish'` Then STDOUT should contain: """ Success: """ When I run `wp post get {POST_ID} --field=post_date` Then STDOUT should not contain: """ 2005-01-24 09:52:00 """ @require-mysql Scenario: Publishing a post and setting a date succeeds if the edit_date flag is passed. Given a WP install When I run `wp post create --post_title='test' --porcelain` Then save STDOUT as {POST_ID} When I run `wp post update {POST_ID} --post_date='2005-01-24T09:52:00.000Z' --post_status='publish' --edit_date=1` Then STDOUT should contain: """ Success: """ When I run `wp post get {POST_ID} --field=post_date` Then STDOUT should contain: """ 2005-01-24 09:52:00 """ # Separate test because of a known bug in the SQLite plugin. # See https://github.com/WordPress/sqlite-database-integration/issues/52. # Once the bug is resolved, this separate test can be removed again. @require-sqlite Scenario: Publishing a post and setting a date succeeds if the edit_date flag is passed. Given a WP install When I run `wp post create --post_title='test' --porcelain` Then save STDOUT as {POST_ID} When I run `wp post update {POST_ID} --post_date='2005-01-24T09:52:00.000Z' --post_status='publish' --edit_date=1` Then STDOUT should contain: """ Success: """ When I run `wp post get {POST_ID} --field=post_date` Then STDOUT should contain: """ 2005-01-24T09:52:00.000Z """	16.49 KB	2025-09-06 07:07
📄 signup.feature Feature: Manage signups in a multisite installation Scenario: Not applicable in single installation site Given a WP install When I try `wp user signup list` Then STDERR should be: """ Error: This is not a multisite installation. """ Scenario: List signups Given a WP multisite install And I run `wp eval 'wpmu_signup_user( "bobuser", "bobuser@example.com" );'` And I run `wp eval 'wpmu_signup_user( "johnuser", "johnuser@example.com" );'` When I run `wp user signup list --fields=signup_id,user_login,user_email,active --format=csv` Then STDOUT should be: """ signup_id,user_login,user_email,active 1,bobuser,bobuser@example.com,0 2,johnuser,johnuser@example.com,0 """ When I run `wp user signup list --format=count --active=1` Then STDOUT should be: """ 0 """ When I run `wp user signup activate bobuser` Then STDOUT should contain: """ Success: Activated 1 of 1 signups. """ When I run `wp user signup list --fields=signup_id,user_login,user_email,active --format=csv --active=1` Then STDOUT should be: """ signup_id,user_login,user_email,active 1,bobuser,bobuser@example.com,1 """ When I run `wp user signup list --fields=signup_id,user_login,user_email,active --format=csv --per_page=1` Then STDOUT should be: """ signup_id,user_login,user_email,active 1,bobuser,bobuser@example.com,1 """ Scenario: Get signup Given a WP multisite install And I run `wp eval 'wpmu_signup_user( "bobuser", "bobuser@example.com" );'` When I run `wp user signup get 1 --field=user_login` Then STDOUT should be: """ bobuser """ When I run `wp user signup get bobuser --fields=signup_id,user_login,user_email,active --format=csv` Then STDOUT should be: """ signup_id,user_login,user_email,active 1,bobuser,bobuser@example.com,0 """ Scenario: Activate signup Given a WP multisite install And I run `wp eval 'wpmu_signup_user( "bobuser", "bobuser@example.com" );'` When I run `wp user signup get bobuser --field=active` Then STDOUT should be: """ 0 """ When I run `wp user signup activate bobuser` Then STDOUT should contain: """ Success: Activated 1 of 1 signups. """ When I try the previous command again Then STDERR should contain: """ Warning: Failed activating signup 1. """ When I run `wp user signup get bobuser --field=active` Then STDOUT should be: """ 1 """ When I run `wp user get bobuser --field=user_email` Then STDOUT should be: """ bobuser@example.com """ Scenario: Activate multiple signups Given a WP multisite install And I run `wp eval 'wpmu_signup_user( "bobuser", "bobuser@example.com" );'` And I run `wp eval 'wpmu_signup_user( "johnuser", "johnuser@example.com" );'` When I run `wp user signup list --active=0 --format=count` Then STDOUT should be: """ 2 """ When I run `wp user signup activate bobuser johnuser` Then STDOUT should contain: """ Success: Activated 2 of 2 signups. """ When I run `wp user signup list --active=1 --format=count` Then STDOUT should be: """ 2 """ Scenario: Activate blog signup entry Given a WP multisite install And I run `wp eval 'wpmu_signup_blog( "example.com", "/bobsite/", "My Awesome Title", "bobuser", "bobuser@example.com" );'` When I run `wp user signup get bobuser --fields=user_login,domain,path,active --format=csv` Then STDOUT should be: """ user_login,domain,path,active bobuser,example.com,/bobsite/,0 """ When I run `wp user signup activate bobuser` Then STDOUT should contain: """ Success: Activated 1 of 1 signups. """ When I run `wp site list --fields=domain,path` Then STDOUT should be a table containing rows: \| domain \| path \| \| example.com \| / \| \| example.com \| /bobsite/ \| Scenario: Delete signups Given a WP multisite install And I run `wp eval 'wpmu_signup_user( "bobuser", "bobuser@example.com" );'` And I run `wp eval 'wpmu_signup_user( "johnuser", "johnuser@example.com" );'` When I run `wp user signup get bobuser --field=user_email` Then STDOUT should be: """ bobuser@example.com """ When I run `wp user signup get johnuser --field=user_email` Then STDOUT should be: """ johnuser@example.com """ When I run `wp user signup delete bobuser@example.com johnuser@example.com` Then STDOUT should contain: """ Success: Deleted 2 of 2 signups. """ When I try `wp user signup get bobuser` Then STDERR should be: """ Error: Invalid signup ID, email, login, or activation key: 'bobuser' """ Scenario: Delete all signups Given a WP multisite install And I run `wp eval 'wpmu_signup_user( "bobuser", "bobuser@example.com" );'` And I run `wp eval 'wpmu_signup_user( "johnuser", "johnuser@example.com" );'` When I try `wp user signup delete` Then STDERR should be: """ Error: You need to specify either one or more signups or provide the --all flag. """ When I run `wp user signup delete --all` Then STDOUT should contain: """ Success: Deleted all signups. """ When I run `wp user signup list --format=count` Then STDOUT should be: """ 0 """	5.52 KB	2025-09-06 07:07
📄 site-create.feature Feature: Create a new site on a WP multisite Scenario: Respect defined `$base` in wp-config Given an empty directory And WP files And a database And a extra-config file: """ define( 'WP_ALLOW_MULTISITE', true ); define( 'MULTISITE', true ); define( 'SUBDOMAIN_INSTALL', false ); $base = '/dev/'; define( 'DOMAIN_CURRENT_SITE', 'localhost' ); define( 'PATH_CURRENT_SITE', '/dev/' ); define( 'SITE_ID_CURRENT_SITE', 1 ); define( 'BLOG_ID_CURRENT_SITE', 1 ); """ When I run `wp config create {CORE_CONFIG_SETTINGS} --skip-check --extra-php < extra-config` Then STDOUT should be: """ Success: Generated 'wp-config.php' file. """ # Old versions of WP can generate wpdb database errors if the WP tables don't exist, so STDERR may or may not be empty When I try `wp core multisite-install --url=localhost/dev/ --title=Test --admin_user=admin --admin_email=admin@example.org` Then STDOUT should contain: """ Success: Network installed. Don't forget to set up rewrite rules """ And the return code should be 0 When I run `wp site list --fields=blog_id,url` Then STDOUT should be a table containing rows: \| blog_id \| url \| \| 1 \| http://localhost/dev/ \| When I run `wp site create --slug=newsite` Then STDOUT should be: """ Success: Site 2 created: http://localhost/dev/newsite/ """ When I run `wp site list --fields=blog_id,url` Then STDOUT should be a table containing rows: \| blog_id \| url \| \| 1 \| http://localhost/dev/ \| \| 2 \| http://localhost/dev/newsite/ \| Scenario: Create new site with custom `$super_admins` global Given an empty directory And WP files And a database And a extra-config file: """ define( 'WP_ALLOW_MULTISITE', true ); define( 'MULTISITE', true ); define( 'SUBDOMAIN_INSTALL', false ); define( 'DOMAIN_CURRENT_SITE', 'localhost' ); define( 'PATH_CURRENT_SITE', '/' ); define('SITE_ID_CURRENT_SITE', 1); define('BLOG_ID_CURRENT_SITE', 1); $super_admins = array( 1 => 'admin' ); """ When I run `wp core config {CORE_CONFIG_SETTINGS} --skip-check --extra-php < extra-config` Then STDOUT should be: """ Success: Generated 'wp-config.php' file. """ # Old versions of WP can generate wpdb database errors if the WP tables don't exist, so STDERR may or may not be empty When I try `wp core multisite-install --url=localhost --title=Test --admin_user=admin --admin_email=admin@example.org` Then STDOUT should contain: """ Success: Network installed. Don't forget to set up rewrite rules """ And the return code should be 0 When I run `wp site list --fields=blog_id,url` Then STDOUT should be a table containing rows: \| blog_id \| url \| \| 1 \| http://localhost/ \| When I run `wp site create --slug=newsite` Then STDOUT should be: """ Success: Site 2 created: http://localhost/newsite/ """ When I run `wp site list --fields=blog_id,url` Then STDOUT should be a table containing rows: \| blog_id \| url \| \| 1 \| http://localhost/ \| \| 2 \| http://localhost/newsite/ \|	3.36 KB	2025-09-06 07:07
📄 site-empty.feature Feature: Empty a WordPress site of its data @require-mysql Scenario: Empty a site Given a WP installation And I run `wp option update uploads_use_yearmonth_folders 0` And download: \| path \| url \| \| {CACHE_DIR}/large-image.jpg \| http://wp-cli.org/behat-data/large-image.jpg \| And a insert_link_data.sql file: """ INSERT INTO `wp_links` (`link_url`, `link_name`, `link_image`, `link_target`, `link_description`, `link_visible`, `link_owner`, `link_rating`, `link_rel`, `link_notes`, `link_rss`) VALUES ('http://wordpress.org/', 'test', '', '', 'test', 'Y', 1, 0, '', '', '') """ When I run `wp db query "SOURCE insert_link_data.sql;"` Then STDERR should be empty When I run `wp db query "SELECT COUNT(link_id) FROM wp_links;"` Then STDOUT should be: """ COUNT(link_id) 1 """ When I run `wp media import {CACHE_DIR}/large-image.jpg --post_id=1` Then the wp-content/uploads/large-image.jpg file should exist When I try `wp site url 1` Then STDERR should be: """ Error: This is not a multisite installation. """ And the return code should be 1 When I run `wp post create --post_title='Test post' --post_content='Test content.'` Then STDOUT should contain: """ Success: Created post """ When I run `wp term create post_tag 'Test term' --slug=test --description='This is a test term'` Then STDOUT should be: """ Success: Created post_tag 2. """ When I run `wp post create --post_type=page --post_title='Sample Privacy Page' --post_content='Sample Privacy Terms' --porcelain` Then save STDOUT as {PAGE_ID} When I run `wp option set wp_page_for_privacy_policy {PAGE_ID}` Then STDOUT should be: """ Success: Updated 'wp_page_for_privacy_policy' option. """ When I run `wp option get wp_page_for_privacy_policy` Then STDOUT should be: """ {PAGE_ID} """ When I run `wp post create --post_title='Sticky Post' --post_content='This is just a sticky post' --porcelain` Then save STDOUT as {STICKY_POST_ID} When I run `wp option set sticky_posts '[{STICKY_POST_ID}]' --format=json` Then STDOUT should be: """ Success: Updated 'sticky_posts' option. """ When I run `wp site empty --yes` Then STDOUT should be: """ Success: The site at 'https://example.com' was emptied. """ And the wp-content/uploads/large-image.jpg file should exist When I run `wp post list --format=ids` Then STDOUT should be empty When I run `wp term list post_tag --format=ids` Then STDOUT should be empty When I run `wp option get wp_page_for_privacy_policy` Then STDOUT should be: """ 0 """ When I run `wp option get sticky_posts --format=json` Then STDOUT should be: """ [] """ When I run `wp db query "SELECT COUNT(link_id) FROM wp_links;"` Then STDOUT should be: """ COUNT(link_id) 0 """ Scenario: Empty a site and its uploads directory Given a WP multisite installation And I run `wp site create --slug=foo` And I run `wp --url=example.com/foo option update uploads_use_yearmonth_folders 0` And download: \| path \| url \| \| {CACHE_DIR}/large-image.jpg \| http://wp-cli.org/behat-data/large-image.jpg \| When I run `wp --url=example.com/foo media import {CACHE_DIR}/large-image.jpg --post_id=1` Then the wp-content/uploads/sites/2/large-image.jpg file should exist When I run `wp site empty --uploads --yes` Then STDOUT should not be empty And the wp-content/uploads/sites/2/large-image.jpg file should exist When I run `wp post list --format=ids` Then STDOUT should be empty When I run `wp --url=example.com/foo site empty --uploads --yes` Then STDOUT should contain: """ ://example.com/foo' was emptied. """ And the wp-content/uploads/sites/2/large-image.jpg file should not exist When I run `wp --url=example.com/foo post list --format=ids` Then STDOUT should be empty	4.2 KB	2025-05-25 12:40
📄 site-generate.feature Feature: Generate new WordPress sites Scenario: Generate on single site Given a WP install When I try `wp site generate` Then STDERR should contain: """ This is not a multisite installation. """ And STDOUT should be empty And the return code should be 1 Scenario: Generate a specific number of sites Given a WP multisite install When I run `wp site generate --count=10` And I run `wp site list --format=count` Then STDOUT should be: """ 11 """ Scenario: Generate sites assigned to a specific network Given a WP multisite install When I try `wp site generate --count=4 --network_id=2` Then STDERR should contain: """ Network with id 2 does not exist. """ And STDOUT should be empty And the return code should be 1 Scenario: Generate sites and output ids Given a WP multisite install When I run `wp site generate --count=3 --format=ids` And I run `wp site list --format=ids` Then STDOUT should be: """ 1 2 3 4 """ And STDERR should be empty And the return code should be 0 Scenario: Generate subdomain sites Given a WP multisite subdomain install When I run `wp site generate --count=1` Then STDOUT should be empty When I run `wp site list --fields=blog_id,url` Then STDOUT should be a table containing rows: \| blog_id \| url \| \| 1 \| https://example.com/ \| \| 2 \| http://site1.example.com/ \| When I run `wp site list --format=ids` Then STDOUT should be: """ 1 2 """ Scenario: Generate subdirectory sites Given a WP multisite subdirectory install When I run `wp site generate --count=1` Then STDOUT should be empty And I run `wp site list --site__in=2 --field=url \| sed -e's,^$.$://.,\1,g'` And save STDOUT as {SCHEME} When I run `wp site list --fields=blog_id,url` Then STDOUT should be a table containing rows: \| blog_id \| url \| \| 1 \| https://example.com/ \| \| 2 \| {SCHEME}://example.com/site1/ \| When I run `wp site list --format=ids` Then STDOUT should be: """ 1 2 """ Scenario: Generate sites with a slug Given a WP multisite subdirectory install When I run `wp site generate --count=2 --slug=subsite` Then STDOUT should be empty And I run `wp site list --site__in=2 --field=url \| sed -e's,^$.$://.,\1,g'` And save STDOUT as {SCHEME1} And I run `wp site list --site__in=3 --field=url \| sed -e's,^$.$://.,\1,g'` And save STDOUT as {SCHEME2} When I run `wp site list --fields=blog_id,url` Then STDOUT should be a table containing rows: \| blog_id \| url \| \| 1 \| https://example.com/ \| \| 2 \| {SCHEME1}://example.com/subsite1/ \| \| 3 \| {SCHEME2}://example.com/subsite2/ \| When I run `wp site list --format=ids` Then STDOUT should be: """ 1 2 3 """ Scenario: Generate sites with reserved slug Given a WP multisite subdirectory install When I try `wp site generate --count=2 --slug=page` Then STDERR should contain: """ The following words are reserved and cannot be used as blog names: page, comments, blog, files, feed """ And STDOUT should be empty And the return code should be 1	3.38 KB	2025-09-06 07:07
📄 site-meta.feature Feature: Manage site custom fields @require-wp-5.1 Scenario: Site meta CRUD Given a WP multisite installation When I run `wp site meta add 1 foo 'bar'` Then STDOUT should not be empty When I run `wp site meta get 1 foo` Then STDOUT should be: """ bar """ When I try `wp site meta get 999999 foo` Then STDERR should be: """ Error: Could not find the site with ID 999999. """ And the return code should be 1 When I run `wp site meta set 1 foo '[ "1", "2" ]' --format=json` Then STDOUT should not be empty When I run `wp site meta get 1 foo --format=json` Then STDOUT should be: """ ["1","2"] """ When I run `wp site meta delete 1 foo` Then STDOUT should not be empty When I try `wp site meta get 1 foo` Then the return code should be 1	864 B	2025-05-25 12:40
📄 site-option-pluck-patch.feature Feature: Site option commands have pluck and patch. @pluck Scenario: Nested values can be retrieved. Given a WP multisite install And an input.json file: """ { "foo": "bar" } """ And I run `wp site option update option_name --format=json < input.json` When I run `wp site option pluck option_name foo` Then STDOUT should be: """ bar """ @pluck @pluck-deep Scenario: A nested value can be retrieved at any depth. Given a WP multisite install And an input.json file: """ { "foo": { "bar": { "baz": "some value" } }, "foo.com": { "visitors": 999 } } """ And I run `wp site option update option_name --format=json < input.json` When I run `wp site option pluck option_name foo bar baz` Then STDOUT should be: """ some value """ When I run `wp site option pluck option_name foo.com visitors` Then STDOUT should be: """ 999 """ @pluck @pluck-fail Scenario: Attempting to pluck a non-existent nested value fails. Given a WP multisite install And I run `wp site option update option_name '{ "key": "value" }' --format=json` When I run `wp site option pluck option_name key` Then STDOUT should be: """ value """ When I try `wp site option pluck option_name foo` Then STDOUT should be empty And the return code should be 1 @pluck @pluck-fail Scenario: Attempting to pluck from a primitive value fails. Given a WP multisite install And I run `wp site option update option_name simple-value` When I try `wp site option pluck option_name foo` Then STDOUT should be empty And the return code should be 1 @pluck @pluck-numeric Scenario: A nested value can be retrieved from an integer key. Given a WP multisite install And I run `wp site option update option_name '[ "foo", "bar" ]' --format=json` When I run `wp site option pluck option_name 0` Then STDOUT should be: """ foo """ @patch @patch-update @patch-arg Scenario: Nested values can be changed. Given a WP multisite install And an input.json file: """ { "foo": "bar" } """ And I run `wp site option update option_name --format=json < input.json` When I run `wp site option patch update option_name foo baz` Then STDOUT should be: """ Success: Updated 'option_name' site option. """ When I run `wp site option get option_name --format=json` Then STDOUT should be JSON containing: """ { "foo": "baz" } """ @patch @patch-update @patch-stdin Scenario: Nested values can be set with a value from STDIN. Given a WP multisite install And an input.json file: """ { "foo": { "bar": "baz" }, "bar": "bad" } """ And a patch file: """ new value """ And I run `wp site option update option_name --format=json < input.json` When I run `wp site option patch update option_name foo bar < patch` Then STDOUT should be: """ Success: Updated 'option_name' site option. """ When I run `wp site option get option_name --format=json` Then STDOUT should be JSON containing: """ { "foo": { "bar": "new value" }, "bar": "bad" } """ @patch @patch-update @patch-fail Scenario: Attempting to update a nested value fails if a parent's key does not exist. Given a WP multisite install And an input.json file: """ { "foo": { "bar": "baz" }, "bar": "bad" } """ And I run `wp site option update option_name --format=json < input.json` When I try `wp site option patch update option_name foo not-a-key new-value` Then STDOUT should be empty And STDERR should contain: """ No data exists for key "not-a-key" """ And the return code should be 1 @patch @patch-delete Scenario: A key can be deleted from a nested value. Given a WP multisite install And an input.json file: """ { "foo": { "bar": "baz", "abe": "lincoln" } } """ And I run `wp site option update option_name --format=json < input.json` When I run `wp site option patch delete option_name foo bar` Then STDOUT should be: """ Success: Updated 'option_name' site option. """ When I run `wp site option get option_name --format=json` Then STDOUT should be JSON containing: """ { "foo": { "abe": "lincoln" } } """ @patch @patch-fail @patch-delete @patch-delete-fail Scenario: A key cannot be deleted from a nested value from a non-existent key. Given a WP multisite install And an input.json file: """ { "foo": { "bar": "baz" } } """ And I run `wp site option update option_name --format=json < input.json` When I try `wp site option patch delete option_name foo not-a-key` Then STDOUT should be empty And STDERR should contain: """ No data exists for key "not-a-key" """ And the return code should be 1 @patch @patch-insert Scenario: A new key can be inserted into a nested value. Given a WP multisite install And I run `wp site option update option_name '{}' --format=json` When I run `wp site option patch insert option_name foo bar` Then STDOUT should be: """ Success: Updated 'option_name' site option. """ When I run `wp site option get option_name --format=json` Then STDOUT should be JSON containing: """ { "foo": "bar" } """ @patch @patch-fail @patch-insert @patch-insert-fail Scenario: A new key cannot be inserted into a non-nested value. Given a WP multisite install And I run `wp site option update option_name 'a simple value'` When I try `wp site option patch insert option_name foo bar` Then STDOUT should be empty And STDERR should contain: """ Cannot create key "foo" """ And the return code should be 1 When I run `wp site option get option_name` Then STDOUT should be: """ a simple value """ @patch @patch-numeric Scenario: A nested value can be updated using an integer key. Given a WP multisite install And I run `wp site option update option_name '[ "foo", "bar" ]' --format=json` When I run `wp site option patch update option_name 0 new` Then STDOUT should be: """ Success: Updated 'option_name' site option. """ When I run `wp site option get option_name --format=json` Then STDOUT should be JSON containing: """ [ "new", "bar" ] """	6.83 KB	2025-05-25 12:40
📄 site-option.feature Feature: Manage WordPress site options Scenario: Site Option CRUD Given a WP multisite installation # String values When I run `wp site option add str_opt 'bar'` Then STDOUT should not be empty When I run `wp site option get str_opt` Then STDOUT should be: """ bar """ When I run `wp site option list` Then STDOUT should not be empty When I run `wp site option list` Then STDOUT should contain: """ str_opt bar """ When I run `wp site option list --search='str_o'` Then STDOUT should be a table containing rows: \| meta_key \| meta_value \| \| str_opt \| bar \| When I run `wp site option list --search='str_o' --format=total_bytes` Then STDOUT should be: """ 3 """ When I run `wp site option list` Then STDOUT should contain: """ admin_user_id 1 """ When I run `wp site option delete str_opt` Then STDOUT should not be empty When I run `wp site option list` Then STDOUT should not contain: """ str_opt bar """ When I try `wp site option get str_opt` Then the return code should be 1 # Integer values When I run `wp site option update admin_user_id 2` Then STDOUT should not be empty When I run `wp site option get admin_user_id` Then STDOUT should be: """ 2 """ When I run `wp site option update admin_user_id 1` Then STDOUT should contain: """ Success: Updated 'admin_user_id' site option. """ When I run the previous command again Then STDOUT should contain: """ Success: Value passed for 'admin_user_id' site option is unchanged. """ When I run `wp site option get admin_user_id` Then STDOUT should be: """ 1 """ # JSON values When I run `wp site option set json_opt '[ 1, 2 ]' --format=json` Then STDOUT should not be empty When I run the previous command again Then STDOUT should not be empty When I run `wp site option get json_opt --format=json` Then STDOUT should be: """ [1,2] """ # Reading from files Given a value.json file: """ { "foo": "bar", "list": [1, 2, 3] } """ When I run `wp site option set foo --format=json < value.json` And I run `wp site option get foo --format=json` Then STDOUT should be JSON containing: """ { "foo": "bar", "list": [1, 2, 3] } """ Scenario: Error on single install Given a WP installation When I try `wp site option get str_opt` Then STDERR should be: """ Error: This is not a multisite installation. """ And the return code should be 1 When I try `wp site option add str_opt 'bar'` Then STDERR should be: """ Error: This is not a multisite installation. """ And the return code should be 1 @require-mysql Scenario: Filter options by `--site_id` Given a WP multisite installation When I run `wp db query "INSERT INTO wp_sitemeta (site_id,meta_key,meta_value) VALUES (2,'wp_cli_test_option','foobar');"` Then the return code should be 0 When I run `wp site option list` Then STDOUT should contain: """ wp_cli_test_option """ And STDERR should be empty When I run `wp site option list --site_id=1` Then STDOUT should not contain: """ wp_cli_test_option """ And STDERR should be empty When I run `wp site option list --site_id=2` Then STDOUT should contain: """ wp_cli_test_option """ And STDERR should be empty	3.64 KB	2025-05-25 12:40
📄 site.feature Feature: Manage sites in a multisite installation Scenario: Create a site Given a WP multisite install When I try `wp site create --slug=first --network_id=1000` Then STDERR should contain: """ Network with id 1000 does not exist. """ And STDOUT should be empty And the return code should be 1 Scenario: Create a subdomain site Given a WP multisite subdomain install When I run `wp site create --slug=first` Then STDOUT should not be empty When I run `wp site list --fields=blog_id,url` Then STDOUT should be a table containing rows: \| blog_id \| url \| \| 1 \| https://example.com/ \| \| 2 \| http://first.example.com/ \| When I run `wp site list --format=ids` Then STDOUT should be: """ 1 2 """ When I run `wp site list --site_id=2 --format=ids` Then STDOUT should be empty When I run `wp --url=first.example.com option get home` Then STDOUT should be: """ http://first.example.com """ Scenario: Delete a site by id Given a WP multisite subdirectory install When I run `wp site create --slug=first --porcelain` Then STDOUT should be a number And save STDOUT as {SITE_ID} And I run `wp site list --site__in={SITE_ID} --field=url \| sed -e's,^$.$://.,\1,g'` And save STDOUT as {SCHEME} When I run `wp site list --fields=blog_id,url` Then STDOUT should be a table containing rows: \| blog_id \| url \| \| 1 \| https://example.com/ \| \| 2 \| {SCHEME}://example.com/first/ \| When I run `wp site list --field=url` Then STDOUT should be: """ https://example.com/ {SCHEME}://example.com/first/ """ When I try `wp site delete 1` Then STDERR should be: """ Error: You cannot delete the root site. """ And STDOUT should be empty And the return code should be 1 When I run `wp site delete {SITE_ID} --yes` Then STDOUT should be: """ Success: The site at '{SCHEME}://example.com/first/' was deleted. """ When I try the previous command again Then the return code should be 1 Scenario: Filter site list Given a WP multisite install When I run `wp site create --slug=first --porcelain` Then STDOUT should be a number And save STDOUT as {SITE_ID} And I run `wp site list --site__in={SITE_ID} --field=url \| sed -e's,^$.$://.,\1,g'` And save STDOUT as {SCHEME} When I run `wp site list --fields=blog_id,url` Then STDOUT should be a table containing rows: \| blog_id \| url \| \| 1 \| https://example.com/ \| \| 2 \| {SCHEME}://example.com/first/ \| When I run `wp site list --field=url --blog_id=2` Then STDOUT should be: """ {SCHEME}://example.com/first/ """ Scenario: Filter site list by user Given a WP multisite install When I run `wp site create --slug=first --porcelain` Then STDOUT should be a number And save STDOUT as {SITE_ID} And I run `wp site list --blog_id={SITE_ID} --field=url` And save STDOUT as {SITE_URL} When I run `wp user create newuser newuser@example.com --porcelain --url={SITE_URL}` Then STDOUT should be a number And save STDOUT as {USER_ID} And I run `wp user get {USER_ID} --field=user_login` And save STDOUT as {USER_LOGIN} When I run `wp site list --field=url --site_user={USER_LOGIN}` Then STDOUT should be: """ {SITE_URL} """ When I try `wp site list --site_user=invalid_user` Then the return code should be 1 And STDERR should be: """ Error: Invalid user ID, email or login: 'invalid_user' """ When I run `wp user remove-role {USER_LOGIN} --url={SITE_URL}` Then STDOUT should contain: """ Success: Removed """ When I run `wp site list --field=url --site_user={USER_LOGIN}` Then STDOUT should be empty Scenario: Delete a site by slug Given a WP multisite install When I run `wp site create --slug=first` Then STDOUT should contain: """ Success: Site 2 created: http """ And STDOUT should contain: """ ://example.com/first/ """ When I run `wp site delete --slug=first --yes` Then STDOUT should contain: """ ://example.com/first/' was deleted. """ When I try the previous command again Then the return code should be 1 When I run `wp site create --slug=42` Then STDOUT should contain: """ Success: Site 3 created: http """ And STDOUT should contain: """ ://example.com/42/ """ When I run `wp site delete --slug=42 --yes` Then STDOUT should contain: """ ://example.com/42/' was deleted. """ When I try the previous command again Then STDERR should contain: """ Error: Could not find site with slug '42'. """ And the return code should be 1 Scenario: Archive a site by a numeric slug Given a WP multisite install When I run `wp site create --slug=42` Then STDOUT should contain: """ Success: Site 2 created: http """ And STDOUT should contain: """ ://example.com/42/ """ When I run `wp site archive --slug=42` Then STDOUT should contain: """ Success: Site 2 archived. """ When I try `wp site archive --slug=43` Then STDERR should contain: """ Error: Could not find site with slug '43'. """ And the return code should be 1 Scenario: Get site info Given a WP multisite install When I run `wp site create --slug=first --porcelain` Then STDOUT should be a number And save STDOUT as {SITE_ID} And I run `wp site list --site__in={SITE_ID} --field=url \| sed -e's,^$.$://.,\1,g'` And save STDOUT as {SCHEME} When I run `wp site url {SITE_ID}` Then STDOUT should be: """ {SCHEME}://example.com/first/ """ When I run `wp site create --slug=second --porcelain` Then STDOUT should be a number And save STDOUT as {SECOND_ID} And I run `wp site list --site__in={SECOND_ID} --field=url \| sed -e's,^$.$://.,\1,g'` And save STDOUT as {SECOND_SCHEME} When I run `wp site url {SECOND_ID} {SITE_ID}` Then STDOUT should be: """ {SECOND_SCHEME}://example.com/second/ {SCHEME}://example.com/first/ """ Scenario: Not providing a site ID or slug when running an update blog status command should throw an error Given a WP multisite install When I try `wp site private` Then the return code should be 1 And STDERR should be: """ Error: Please specify one or more IDs of sites, or pass the slug for a single site using --slug. """ And STDOUT should be empty Scenario: Site IDs or a slug can be provided, but not both. Given a WP multisite install And I run `wp site create --slug=first --porcelain` When I try `wp site private 1 --slug=first` Then the return code should be 1 And STDERR should be: """ Error: Please specify one or more IDs of sites, or pass the slug for a single site using --slug. """ Scenario: Errors for an invalid slug Given a WP multisite install When I try `wp site private --slug=first` Then the return code should be 1 And STDERR should be: """ Error: Could not find site with slug 'first'. """ Scenario: Archive/unarchive a site Given a WP multisite install And I run `wp site create --slug=first --porcelain` And save STDOUT as {FIRST_SITE} And I run `wp site create --slug=second --porcelain` And save STDOUT as {SECOND_SITE} When I run `wp site archive {FIRST_SITE}` Then STDOUT should be: """ Success: Site {FIRST_SITE} archived. """ When I run `wp site list --fields=blog_id,archived` Then STDOUT should be a table containing rows: \| blog_id \| archived \| \| {FIRST_SITE} \| 1 \| When I try `wp site archive {FIRST_SITE} {SECOND_SITE}` Then STDERR should be: """ Warning: Site {FIRST_SITE} already archived. """ And STDOUT should be: """ Success: Site {SECOND_SITE} archived. """ And the return code should be 0 When I run `wp site list --fields=blog_id,archived` Then STDOUT should be a table containing rows: \| blog_id \| archived \| \| {FIRST_SITE} \| 1 \| When I run `wp site unarchive {FIRST_SITE}` Then STDOUT should be: """ Success: Site {FIRST_SITE} unarchived. """ When I run `wp site list --fields=blog_id,archived` Then STDOUT should be a table containing rows: \| blog_id \| archived \| \| {FIRST_SITE} \| 0 \| When I try `wp site archive 1` Then STDERR should be: """ Warning: You are not allowed to change the main site. """ And STDOUT should be empty And the return code should be 0 Scenario: Activate/deactivate a site Given a WP multisite install And I run `wp site create --slug=first --porcelain` And save STDOUT as {FIRST_SITE} And I run `wp site create --slug=second --porcelain` And save STDOUT as {SECOND_SITE} When I run `wp site deactivate {FIRST_SITE}` Then STDOUT should be: """ Success: Site {FIRST_SITE} deactivated. """ When I run `wp site list --fields=blog_id,deleted` Then STDOUT should be a table containing rows: \| blog_id \| deleted \| \| {FIRST_SITE} \| 1 \| When I try `wp site deactivate {FIRST_SITE} {SECOND_SITE}` Then STDERR should be: """ Warning: Site {FIRST_SITE} already deactivated. """ And STDOUT should be: """ Success: Site {SECOND_SITE} deactivated. """ And the return code should be 0 When I run `wp site list --fields=blog_id,deleted` Then STDOUT should be a table containing rows: \| blog_id \| deleted \| \| {FIRST_SITE} \| 1 \| When I run `wp site activate {FIRST_SITE}` Then STDOUT should be: """ Success: Site {FIRST_SITE} activated. """ When I run `wp site list --fields=blog_id,deleted` Then STDOUT should be a table containing rows: \| blog_id \| deleted \| \| {FIRST_SITE} \| 0 \| When I try `wp site deactivate 1` Then STDERR should be: """ Warning: You are not allowed to change the main site. """ And STDOUT should be empty And the return code should be 0 Scenario: Mark/remove a site from spam Given a WP multisite install And I run `wp site create --slug=first --porcelain` And save STDOUT as {FIRST_SITE} And I run `wp site create --slug=second --porcelain` And save STDOUT as {SECOND_SITE} When I run `wp site spam {FIRST_SITE}` Then STDOUT should be: """ Success: Site {FIRST_SITE} marked as spam. """ When I run `wp site list --fields=blog_id,spam` Then STDOUT should be a table containing rows: \| blog_id \| spam \| \| {FIRST_SITE} \| 1 \| When I try `wp site spam {FIRST_SITE} {SECOND_SITE}` Then STDERR should be: """ Warning: Site {FIRST_SITE} already marked as spam. """ And STDOUT should be: """ Success: Site {SECOND_SITE} marked as spam. """ And the return code should be 0 When I run `wp site list --fields=blog_id,spam` Then STDOUT should be a table containing rows: \| blog_id \| spam \| \| {FIRST_SITE} \| 1 \| When I run `wp site unspam {FIRST_SITE}` Then STDOUT should be: """ Success: Site {FIRST_SITE} removed from spam. """ When I run `wp site list --fields=blog_id,spam` Then STDOUT should be a table containing rows: \| blog_id \| spam \| \| {FIRST_SITE} \| 0 \| When I try `wp site spam 1` Then STDERR should be: """ Warning: You are not allowed to change the main site. """ And STDOUT should be empty And the return code should be 0 Scenario: Mark/remove a site as mature Given a WP multisite install And I run `wp site create --slug=first --porcelain` And save STDOUT as {FIRST_SITE} And I run `wp site create --slug=second --porcelain` And save STDOUT as {SECOND_SITE} When I run `wp site mature {FIRST_SITE}` Then STDOUT should be: """ Success: Site {FIRST_SITE} marked as mature. """ When I run `wp site list --fields=blog_id,mature` Then STDOUT should be a table containing rows: \| blog_id \| mature \| \| {FIRST_SITE} \| 1 \| When I try `wp site mature {FIRST_SITE} {SECOND_SITE}` Then STDERR should be: """ Warning: Site {FIRST_SITE} already marked as mature. """ And STDOUT should be: """ Success: Site {SECOND_SITE} marked as mature. """ And the return code should be 0 When I run `wp site list --fields=blog_id,mature` Then STDOUT should be a table containing rows: \| blog_id \| mature \| \| {FIRST_SITE} \| 1 \| When I run `wp site unmature {FIRST_SITE}` Then STDOUT should be: """ Success: Site {FIRST_SITE} marked as unmature. """ When I run `wp site list --fields=blog_id,mature` Then STDOUT should be a table containing rows: \| blog_id \| mature \| \| {FIRST_SITE} \| 0 \| When I try `wp site unmature 1` Then STDERR should be: """ Warning: You are not allowed to change the main site. """ And STDOUT should be empty And the return code should be 0 Scenario: Set/Unset a site as public Given a WP multisite install And I run `wp site create --slug=first --porcelain` And save STDOUT as {FIRST_SITE} And I run `wp site create --slug=second --porcelain` And save STDOUT as {SECOND_SITE} When I run `wp site private {FIRST_SITE}` Then STDOUT should be: """ Success: Site {FIRST_SITE} marked as private. """ When I run `wp site list --fields=blog_id,public` Then STDOUT should be a table containing rows: \| blog_id \| public \| \| {FIRST_SITE} \| 0 \| When I try `wp site private {FIRST_SITE} {SECOND_SITE}` Then STDERR should be: """ Warning: Site {FIRST_SITE} already marked as private. """ And STDOUT should be: """ Success: Site {SECOND_SITE} marked as private. """ And the return code should be 0 When I run `wp site list --fields=blog_id,public` Then STDOUT should be a table containing rows: \| blog_id \| public \| \| {FIRST_SITE} \| 0 \| When I run `wp site public {FIRST_SITE}` Then STDOUT should be: """ Success: Site {FIRST_SITE} marked as public. """ When I run `wp site list --fields=blog_id,public` Then STDOUT should be a table containing rows: \| blog_id \| public \| \| {FIRST_SITE} \| 1 \| When I try `wp site private 1` Then STDERR should be: """ Warning: You are not allowed to change the main site. """ And STDOUT should be empty And the return code should be 0 Scenario: Permit CLI operations against archived and suspended sites Given a WP multisite install And I run `wp site create --slug=first --porcelain` And save STDOUT as {FIRST_SITE} When I run `wp site archive {FIRST_SITE}` Then STDOUT should be: """ Success: Site {FIRST_SITE} archived. """ When I run `wp --url=example.com/first option get home` Then STDOUT should contain: """ ://example.com/first """ Scenario: Create site with title containing slash Given a WP multisite install And I run `wp site create --slug=mysite --title="My\Site"` Then STDOUT should not be empty When I run `wp option get blogname --url=example.com/mysite` Then STDOUT should be: """ My\Site """ Scenario: Activate/deactivate a site by slug Given a WP multisite install When I run `wp site create --slug=first` Then STDOUT should contain: """ Success: Site 2 created: http """ And STDOUT should contain: """ ://example.com/first/ """ When I run `wp site deactivate --slug=first` Then STDOUT should contain: """ Success: Site 2 deactivated. """ When I run `wp site list --fields=blog_id,deleted` Then STDOUT should be a table containing rows: \| blog_id \| deleted \| \| 2 \| 1 \| When I try `wp site deactivate --slug=first` Then STDERR should be: """ Warning: Site 2 already deactivated. """ When I run `wp site activate --slug=first` Then STDOUT should be: """ Success: Site 2 activated. """ When I run `wp site list --fields=blog_id,deleted` Then STDOUT should be a table containing rows: \| blog_id \| deleted \| \| 2 \| 0 \| Scenario: Archive/unarchive a site by slug Given a WP multisite install When I run `wp site create --slug=first` Then STDOUT should contain: """ Success: Site 2 created: http """ And STDOUT should contain: """ ://example.com/first/ """ When I run `wp site archive --slug=first` Then STDOUT should contain: """ Success: Site 2 archived. """ When I run `wp site list --fields=blog_id,archived` Then STDOUT should be a table containing rows: \| blog_id \| archived \| \| 2 \| 1 \| When I try `wp site archive --slug=first` Then STDERR should be: """ Warning: Site 2 already archived. """ When I run `wp site unarchive --slug=first` Then STDOUT should be: """ Success: Site 2 unarchived. """ When I run `wp site list --fields=blog_id,archived` Then STDOUT should be a table containing rows: \| blog_id \| archived \| \| 2 \| 0 \| Scenario: Mark/remove a site by slug from spam Given a WP multisite install When I run `wp site create --slug=first` Then STDOUT should contain: """ Success: Site 2 created: http """ And STDOUT should contain: """ ://example.com/first/ """ When I run `wp site spam --slug=first` Then STDOUT should contain: """ Success: Site 2 marked as spam. """ When I run `wp site list --fields=blog_id,spam` Then STDOUT should be a table containing rows: \| blog_id \| spam \| \| 2 \| 1 \| When I try `wp site spam --slug=first` Then STDERR should be: """ Warning: Site 2 already marked as spam. """ When I run `wp site unspam --slug=first` Then STDOUT should be: """ Success: Site 2 removed from spam. """ When I run `wp site list --fields=blog_id,spam` Then STDOUT should be a table containing rows: \| blog_id \| spam \| \| 2 \| 0 \| Scenario: Mark/remove a site by slug as mature Given a WP multisite install When I run `wp site create --slug=first` Then STDOUT should contain: """ Success: Site 2 created: http """ And STDOUT should contain: """ ://example.com/first/ """ When I run `wp site mature --slug=first` Then STDOUT should contain: """ Success: Site 2 marked as mature. """ When I run `wp site list --fields=blog_id,mature` Then STDOUT should be a table containing rows: \| blog_id \| mature \| \| 2 \| 1 \| When I try `wp site mature --slug=first` Then STDERR should be: """ Warning: Site 2 already marked as mature. """ When I run `wp site unmature --slug=first` Then STDOUT should be: """ Success: Site 2 marked as unmature. """ When I run `wp site list --fields=blog_id,mature` Then STDOUT should be a table containing rows: \| blog_id \| mature \| \| 2 \| 0 \| Scenario: Set/Unset a site by slug as public Given a WP multisite install When I run `wp site create --slug=first` Then STDOUT should contain: """ Success: Site 2 created: http """ And STDOUT should contain: """ ://example.com/first/ """ When I run `wp site private --slug=first` Then STDOUT should contain: """ Success: Site 2 marked as private. """ When I run `wp site list --fields=blog_id,public` Then STDOUT should be a table containing rows: \| blog_id \| public \| \| 2 \| 0 \| When I try `wp site private --slug=first` Then STDERR should be: """ Warning: Site 2 already marked as private. """ When I run `wp site public --slug=first` Then STDOUT should be: """ Success: Site 2 marked as public. """ When I run `wp site list --fields=blog_id,public` Then STDOUT should be a table containing rows: \| blog_id \| public \| \| 2 \| 1 \|	20.81 KB	2025-09-06 07:07
📄 taxonomy.feature Feature: Manage WordPress taxonomies Background: Given a WP install @require-wp-3.7 Scenario: Listing taxonomies When I run `wp taxonomy list --format=csv` Then STDOUT should be CSV containing: \| name \| label \| description \| object_type \| show_tagcloud \| hierarchical \| public \| \| category \| Categories \| \| post \| 1 \| 1 \| 1 \| \| post_tag \| Tags \| \| post \| 1 \| \| 1 \| When I run `wp taxonomy list --object_type=nav_menu_item --format=csv` Then STDOUT should be CSV containing: \| name \| label \| description \| object_type \| show_tagcloud \| hierarchical \| public \| \| nav_menu \| Navigation Menus \| \| nav_menu_item \| \| \| \| @require-wp-5.0 Scenario: Listing taxonomies with counts When I run `wp taxonomy list --fields=name,count --format=csv` Then STDOUT should be CSV containing: \| name \| count \| \| category \| 1 \| \| post_tag \| 0 \| Scenario: Get taxonomy When I try `wp taxonomy get invalid-taxonomy` Then STDERR should be: """ Error: Taxonomy invalid-taxonomy doesn't exist. """ And the return code should be 1 When I run `wp taxonomy get category` Then STDOUT should be a table containing rows: \| Field \| Value \| \| name \| category \| \| object_type \| ["post"] \| \| label \| Categories \| @require-wp-5.0 Scenario: Get taxonomy with count When I run `wp taxonomy get category --fields=name,count` Then STDOUT should be a table containing rows: \| Field \| Value \| \| name \| category \| \| count \| 1 \| @require-wp-5.1 Scenario: Listing taxonomies with strict/no-strict mode Given a WP installation And a wp-content/mu-plugins/test-taxonomy-list.php file: """ <?php // Plugin Name: Test Taxonomy Strict/No-Strict Mode add_action( 'init', function() { $args = array( 'hierarchical' => true, 'show_ui' => true, 'show_admin_column' => true, 'update_count_callback' => '_update_post_term_count', 'query_var' => true, 'labels' => array( 'name' => _x( 'Genres', 'taxonomy general name', 'textdomain' ), ), ); register_taxonomy( 'genres', array( 'post','page' ), $args ); } ); """ When I run `wp taxonomy list --object_type=post --strict` Then STDOUT should be a table containing rows: \| name \| label \| description \| object_type \| show_tagcloud \| hierarchical \| public \| \| category \| Categories \| \| post \| 1 \| 1 \| 1 \| \| post_tag \| Tags \| \| post \| 1 \| \| 1 \| \| post_format \| Formats \| \| post \| \| \| 1 \| When I run `wp taxonomy list --object_type=post --no-strict` Then STDOUT should be a table containing rows: \| name \| label \| description \| object_type \| show_tagcloud \| hierarchical \| public \| \| category \| Categories \| \| post \| 1 \| 1 \| 1 \| \| post_tag \| Tags \| \| post \| 1 \| \| 1 \| \| post_format \| Formats \| \| post \| \| \| 1 \| \| genres \| Genres \| \| post, page \| 1 \| 1 \| 1 \| @less-than-wp-5.1 Scenario: Listing taxonomies with strict/no-strict mode (for WP < 5.1) Given a WP installation And a wp-content/mu-plugins/test-taxonomy-list.php file: """ <?php // Plugin Name: Test Taxonomy Strict/No-Strict Mode add_action( 'init', function() { $args = array( 'hierarchical' => true, 'show_ui' => true, 'show_admin_column' => true, 'update_count_callback' => '_update_post_term_count', 'query_var' => true, 'labels' => array( 'name' => _x( 'Genres', 'taxonomy general name', 'textdomain' ), ), ); register_taxonomy( 'genres', array( 'post','page' ), $args ); } ); """ When I run `wp taxonomy list --object_type=post --strict` Then STDOUT should be a table containing rows: \| name \| label \| description \| object_type \| show_tagcloud \| hierarchical \| public \| \| category \| Categories \| \| post \| 1 \| 1 \| 1 \| \| post_tag \| Tags \| \| post \| 1 \| \| 1 \| \| post_format \| Format \| \| post \| \| \| 1 \| When I run `wp taxonomy list --object_type=post --no-strict` Then STDOUT should be a table containing rows: \| name \| label \| description \| object_type \| show_tagcloud \| hierarchical \| public \| \| category \| Categories \| \| post \| 1 \| 1 \| 1 \| \| post_tag \| Tags \| \| post \| 1 \| \| 1 \| \| post_format \| Format \| \| post \| \| \| 1 \| \| genres \| Genres \| \| post, page \| 1 \| 1 \| 1 \|	5.6 KB	2025-05-25 12:40
📄 term-generate.feature Feature: Generate WP terms Background: Given a WP install Scenario: Generating terms When I run `wp term generate category --count=10` And I run `wp term list category --format=count` Then STDOUT should be: """ 11 """ Scenario: Generating terms when terms already exist When I run `wp term generate category --count=10` And I run `wp term generate category --count=10` And I run `wp term list category --format=count` Then STDOUT should be: """ 21 """ Scenario: Generating terms and outputting ids When I run `wp term generate category --count=1 --format=ids` Then save STDOUT as {TERM_ID} When I run `wp term update category {TERM_ID} --name="foo"` Then STDOUT should contain: """ Success: """	810 B	2025-05-25 12:40
📄 term-meta.feature Feature: Manage term custom fields @require-wp-4.4 Scenario: Term meta CRUD Given a WP install When I run `wp term meta add 1 foo 'bar'` Then STDOUT should not be empty When I run `wp term meta get 1 foo` Then STDOUT should be: """ bar """ When I try `wp term meta get 999999 foo` Then STDERR should be: """ Error: Could not find the term with ID 999999. """ And the return code should be 1 When I run `wp term meta set 1 foo '[ "1", "2" ]' --format=json` Then STDOUT should not be empty When I run `wp term meta get 1 foo --format=json` Then STDOUT should be: """ ["1","2"] """ When I run `wp term meta delete 1 foo` Then STDOUT should not be empty When I try `wp term meta get 1 foo` Then the return code should be 1	849 B	2025-05-25 12:40
📄 term-migrate.feature Feature: Migrate term custom fields @require-wp-4.4 Scenario: Migrate an existing term by slug Given a WP install When I run `wp term create category apple` Then STDOUT should not be empty When I run `wp post create --post_title='Test post' --porcelain` Then STDOUT should be a number And save STDOUT as {POST_ID} When I run `wp post term set {POST_ID} category apple` Then STDOUT should not be empty When I run `wp term migrate apple --by=slug --from=category --to=post_tag` Then STDOUT should be: """ Term 'apple' assigned to post {POST_ID}. Term 'apple' migrated. Old instance of term 'apple' removed from its original taxonomy. Success: Migrated the term 'apple' from taxonomy 'category' to taxonomy 'post_tag' for 1 post. """ @require-wp-4.4 Scenario: Migrate an existing term by ID Given a WP install When I run `wp term create category apple --porcelain` Then STDOUT should be a number And save STDOUT as {TERM_ID} When I run `wp post create --post_title='Test post' --porcelain` Then STDOUT should be a number And save STDOUT as {POST_ID} When I run `wp post term set {POST_ID} category {TERM_ID}` Then STDOUT should not be empty When I run `wp term migrate {TERM_ID} --by=slug --from=category --to=post_tag` Then STDOUT should be: """ Term '{TERM_ID}' assigned to post {POST_ID}. Term '{TERM_ID}' migrated. Old instance of term '{TERM_ID}' removed from its original taxonomy. Success: Migrated the term '{TERM_ID}' from taxonomy 'category' to taxonomy 'post_tag' for 1 post. """ @require-wp-4.4 Scenario: Migrate a term in multiple posts Given a WP install When I run `wp term create category orange` Then STDOUT should not be empty When I run `wp post create --post_title='Test post' --porcelain` Then STDOUT should be a number And save STDOUT as {POST_ID} When I run `wp post term set {POST_ID} category orange` Then STDOUT should not be empty When I run `wp post create --post_title='Test post 2' --porcelain` Then STDOUT should be a number And save STDOUT as {POST_ID_2} When I run `wp post term set {POST_ID_2} category orange` Then STDOUT should not be empty When I run `wp term migrate orange --by=slug --from=category --to=post_tag` Then STDOUT should be: """ Term 'orange' assigned to post {POST_ID}. Term 'orange' assigned to post {POST_ID_2}. Term 'orange' migrated. Old instance of term 'orange' removed from its original taxonomy. Success: Migrated the term 'orange' from taxonomy 'category' to taxonomy 'post_tag' for 2 posts. """ @require-wp-4.4 Scenario: Try to migrate a term that does not exist Given a WP install When I try `wp term migrate peach --by=slug --from=category --to=post_tag` Then STDERR should be: """ Error: Taxonomy term 'peach' for taxonomy 'category' doesn't exist. """	2.97 KB	2025-09-06 07:07
📄 term-recount.feature Feature: Recount terms on a taxonomy Background: Given a WP install Scenario: Term recount with an invalid taxonomy When I try `wp term recount some-fake-taxonomy` Then STDERR should be: """ Warning: Taxonomy some-fake-taxonomy does not exist. """ And the return code should be 0 Scenario: Term recount with a valid taxonomy When I run `wp term recount category` Then STDOUT should be: """ Success: Updated category term count. """ Scenario: Term recount with a multiple taxonomies When I run `wp term recount category post_tag` Then STDOUT should be: """ Success: Updated category term count. Success: Updated post_tag term count. """ Scenario: Fixes an invalid term count for a taxonomy When I run `wp term create category "Term Recount Category" --porcelain` Then STDOUT should be a number And save STDOUT as {TERM_ID} When I run `wp post create --post_title='Term Recount Test' --post_status=publish --post_category={TERM_ID} --porcelain` Then STDOUT should be a number And save STDOUT as {POST_ID} When I run `wp term get category {TERM_ID} --field=count` Then STDOUT should be: """ 1 """ When I run `wp eval 'global $wpdb; $wpdb->update( $wpdb->term_taxonomy, array( "count" => 3 ), array( "term_id" => {TERM_ID} ) );'` And I run `wp term get category {TERM_ID} --field=count` Then STDOUT should be: """ 3 """ When I run `wp term recount category` And I run `wp term get category {TERM_ID} --field=count` """ 1 """	1.6 KB	2025-09-06 07:07
📄 term.feature Feature: Manage WordPress terms Background: Given a WP install Scenario: Creating/listing a term When I run `wp term create post_tag 'Test term' --slug=test --description='This is a test term' --porcelain` Then STDOUT should be a number And save STDOUT as {TERM_ID} When I try the previous command again Then STDERR should not be empty And the return code should be 1 When I run `wp term list post_tag --format=json` Then STDOUT should be JSON containing: """ [{ "name": "Test term", "slug":"test", "description":"This is a test term", "parent":0, "count":0 }] """ When I run `wp term list post_tag --fields=name,slug --format=csv` Then STDOUT should be CSV containing: \| name \| slug \| \| Test term \| test \| When I run `wp term create category 'Test category' --slug=test-category --description='This is a test category'` Then STDOUT should not be empty When I run `wp term list post_tag category --fields=name,slug --format=csv` Then STDOUT should be CSV containing: \| name \| slug \| \| Test term \| test \| \| Test category \| test-category \| When I run `wp term get post_tag {TERM_ID}` Then STDOUT should be a table containing rows: \| Field \| Value \| \| term_id \| {TERM_ID} \| \| name \| Test term \| When I run `wp term get post_tag {TERM_ID} --format=csv --fields=name,taxonomy` Then STDOUT should be CSV containing: \| Field \| Value \| \| name \| Test term \| \| taxonomy \| post_tag \| When I try `wp term list nonexistent_taxonomy` Then STDERR should be: """ Error: Taxonomy nonexistent_taxonomy doesn't exist. """ And the return code should be 1 Scenario: Updating an invalid term should exit with an error Given a WP install When I try `wp term update category 22 --name=Foo` Then the return code should be 1 And STDERR should contain: """ Error: Term doesn't exist. """ Scenario: Creating/deleting a term When I run `wp term create post_tag 'Test delete term' --slug=test-delete --description='This is a test term to be deleted' --porcelain` Then STDOUT should be a number And save STDOUT as {TERM_ID} When I run `wp term create post_tag 'Test delete term 2' --slug=test-two --description='This is a test term to be deleted' --porcelain` Then STDOUT should be a number And save STDOUT as {TERM_ID_TWO} When I run `wp term get post_tag {TERM_ID} --field=slug --format=json` Then STDOUT should be: """ "test-delete" """ When I run `wp term delete post_tag {TERM_ID}` Then STDOUT should be: """ Deleted post_tag {TERM_ID}. Success: Deleted 1 of 1 terms. """ And the return code should be 0 When I try the previous command again Then STDOUT should be: """ Success: Term already deleted. """ And STDERR should be: """ Warning: post_tag {TERM_ID} doesn't exist. """ And the return code should be 0 When I try `wp term delete post_tag {TERM_ID} {TERM_ID_TWO}` Then STDOUT should be: """ Deleted post_tag {TERM_ID_TWO}. Success: Deleted 1 of 2 terms. """ And STDERR should be: """ Warning: post_tag {TERM_ID} doesn't exist. """ And the return code should be 0 Scenario: Term with a non-existent parent When I try `wp term create category Apple --parent=99 --porcelain` Then STDERR should be: """ Error: Parent term does not exist. """ And the return code should be 1 Scenario: Filter terms by term_id When I run `wp term generate category --count=10` And I run `wp term create category "My Test Category" --porcelain` Then save STDOUT as {TERM_ID} When I run `wp term list category --term_id={TERM_ID} --field=name` Then STDOUT should be: """ My Test Category """ Scenario: Fetch term url When I run `wp term create category "First Category" --porcelain` Then save STDOUT as {TERM_ID} When I run `wp term create category "Second Category" --porcelain` Then save STDOUT as {SECOND_TERM_ID} When I run `wp term url category {TERM_ID}` Then STDOUT should be: """ https://example.com/?cat=2 """ When I run `wp term url category {TERM_ID} {SECOND_TERM_ID}` Then STDOUT should be: """ https://example.com/?cat=2 https://example.com/?cat=3 """ When I run `wp term url category {SECOND_TERM_ID} {TERM_ID}` Then STDOUT should be: """ https://example.com/?cat=3 https://example.com/?cat=2 """ When I run `wp term get category 1 --field=url` Then STDOUT should be: """ https://example.com/?cat=1 """ Scenario: Make sure WordPress receives the slashed data it expects When I run `wp term create category 'My\Term' --description='My\Term\Description' --porcelain` Then save STDOUT as {TERM_ID} When I run `wp term get category {TERM_ID} --field=name` Then STDOUT should be: """ My\Term """ When I run `wp term get category {TERM_ID} --field=description` Then STDOUT should be: """ My\Term\Description """ When I run `wp term update category {TERM_ID} --name='My\New\Term' --description='var isEmailValid = /^\S+@\S+.\S+$/.test(email);'` Then STDOUT should not be empty When I run `wp term get category {TERM_ID} --field=name` Then STDOUT should be: """ My\New\Term """ When I run `wp term get category {TERM_ID} --field=description` Then STDOUT should be: """ var isEmailValid = /^\S+@\S+.\S+$/.test(email); """ Scenario: Deleting a term by slug or ID When I run `wp term create category Apple --description="A type of fruit"` Then STDOUT should be: """ Success: Created category 2. """ When I run `wp term create category Orange --description="A type of fruit"` Then STDOUT should be: """ Success: Created category 3. """ When I run `wp term create category Mango --description="A type of fruit"` Then STDOUT should be: """ Success: Created category 4. """ When I run `wp term get category 2 --field=slug --format=json` Then STDOUT should be: """ "apple" """ When I run `wp term delete category apple --by=slug` Then STDOUT should be: """ Deleted category 2. Success: Deleted 1 of 1 terms. """ When I run `wp term delete category 3 --by=id` Then STDOUT should be: """ Deleted category 3. Success: Deleted 1 of 1 terms. """ When I run `wp term delete category 4` Then STDOUT should be: """ Deleted category 4. Success: Deleted 1 of 1 terms. """ @require-wp-4.7 Scenario: Fetch term by slug or ID When I run `wp term create category Apple --description="A type of fruit"` Then STDOUT should be: """ Success: Created category 2. """ When I run `wp term get category 2 --by=id --format=json --fields=term_id,name,slug,count` Then STDOUT should be: """ {"term_id":2,"name":"Apple","slug":"apple","count":0} """ When I run `wp term get category apple --by=slug --format=json --fields=term_id,name,slug,count` Then STDOUT should be: """ {"term_id":2,"name":"Apple","slug":"apple","count":0} """ Scenario: Update term by slug or ID When I run `wp term create category Apple --description="A type of fruit"` Then STDOUT should be: """ Success: Created category 2. """ When I run `wp term update category apple --by=slug --name=PineApple` Then STDOUT should be: """ Success: Term updated. """ When I run `wp term update category 2 --by=id --description="This is testing description"` Then STDOUT should be: """ Success: Term updated. """	8 KB	2025-09-06 07:07
📄 user-application-password.feature Feature: Manage user custom fields # SQLite requires WordPress 6.0+. @less-than-php-8.0 @require-mysql Scenario: User application passwords are disabled for WordPress lower than 5.6 Given a WP install And I try `wp theme install twentytwenty --activate` And I run `wp core download --version=5.5 --force` When I try `wp user application-password create 1 myapp` Then STDERR should contain: """ Error: Requires WordPress 5.6 or greater. """ When I try `wp user application-password list 1` Then STDERR should contain: """ Error: Requires WordPress 5.6 or greater. """ When I try `wp user application-password get 1 123` Then STDERR should contain: """ Error: Requires WordPress 5.6 or greater. """ When I try `wp user application-password delete 1 123` Then STDERR should contain: """ Error: Requires WordPress 5.6 or greater. """ @require-wp-5.6 Scenario: User application password CRUD Given a WP install When I run `wp user application-password create 1 myapp` Then STDOUT should not be empty When I run `wp user application-password list 1` Then STDOUT should contain: """ myapp """ When I run `wp user application-password list 1 --name=myapp --field=uuid` And save STDOUT as {UUID} And I run `wp user application-password get 1 {UUID}` Then STDOUT should contain: """ myapp """ When I try `wp user application-password get 2 {UUID}` Then STDERR should be: """ Error: Invalid user ID, email or login: '2' """ And the return code should be 1 When I try `wp user application-password get 1 123` Then STDERR should be: """ Error: No application password found for this user ID and UUID. """ And the return code should be 1 When I run `wp user application-password update 1 {UUID} --name=anotherapp` Then STDOUT should not be empty When I run `wp user application-password get 1 {UUID}` Then STDOUT should contain: """ anotherapp """ And STDOUT should not contain: """ myapp """ When I run `wp user application-password delete 1 {UUID}` Then STDOUT should contain: """ Success: Deleted 1 of 1 application password. """ When I try `wp user application-password get 1 {UUID}` Then the return code should be 1 When I run `wp user application-password create 1 myapp1` And I run `wp user application-password create 1 myapp2` And I run `wp user application-password create 1 myapp3` And I run `wp user application-password create 1 myapp4` And I run `wp user application-password create 1 myapp5` Then STDOUT should not be empty When I run `wp user application-password list 1 --format=count` Then STDOUT should be: """ 5 """ When I run `wp user application-password list 1 --name=myapp1 --field=uuid` Then save STDOUT as {UUID1} When I run `wp user application-password list 1 --name=myapp2 --field=uuid` Then save STDOUT as {UUID2} When I try `wp user application-password delete 1 {UUID1} {UUID2} nonsense` Then STDERR should contain: """ Warning: Failed to delete UUID nonsense """ And STDOUT should contain: """ Success: Deleted 2 of 3 application passwords. """ When I run `wp user application-password list 1 --format=count` Then STDOUT should be: """ 3 """ When I run `wp user application-password delete 1 --all` And I run `wp user application-password list 1 --format=count` Then STDOUT should be: """ 0 """ @require-wp-5.6 Scenario: List user application passwords Given a WP install When I run `wp user application-password create 1 myapp1` Then STDOUT should not be empty When I run `wp user application-password create 1 myapp2 --app-id=42` Then STDOUT should not be empty When I run `wp user application-password list 1 --name=myapp1 --field=uuid` Then save STDOUT as {UUID1} When I run `wp user application-password list 1 --name=myapp2 --field=uuid` Then save STDOUT as {UUID2} When I run `wp user application-password list 1 --name=myapp1 --field=password` Then save STDOUT as {HASH1} When I run `wp user application-password list 1 --name=myapp1 --field=password \| sed 's#/#\\\/#g'` Then save STDOUT as {JSONHASH1} When I run `wp user application-password list 1 --name=myapp2 --field=password` Then save STDOUT as {HASH2} When I run `wp user application-password list 1 --name=myapp2 --field=password \| sed 's#/#\\\/#g'` Then save STDOUT as {JSONHASH2} When I run `wp user application-password list 1 --name=myapp1 --field=created` Then save STDOUT as {CREATED1} When I run `wp user application-password list 1 --name=myapp2 --field=created` Then save STDOUT as {CREATED2} When I run `wp user application-password list 1 --format=json` Then STDOUT should contain: """ {"uuid":"{UUID1}","app_id":"","name":"myapp1","password":"{JSONHASH1}","created":{CREATED1},"last_used":null,"last_ip":null} """ And STDOUT should contain: """ {"uuid":"{UUID2}","app_id":"42","name":"myapp2","password":"{JSONHASH2}","created":{CREATED2},"last_used":null,"last_ip":null} """ When I run `wp user application-password list 1 --format=json --fields=uuid,name` Then STDOUT should contain: """ {"uuid":"{UUID1}","name":"myapp1"} """ And STDOUT should contain: """ {"uuid":"{UUID2}","name":"myapp2"} """ When I run `wp user application-password list 1` Then STDOUT should be a table containing rows: \| uuid \| app_id \| name \| password \| created \| last_used \| last_ip \| \| {UUID2} \| 42 \| myapp2 \| {HASH2} \| {CREATED2} \| \| \| \| {UUID1} \| \| myapp1 \| {HASH1} \| {CREATED1} \| \| \| When I run `wp user application-password list 1 --fields=uuid,app_id,name` Then STDOUT should be a table containing rows: \| uuid \| app_id \| name \| \| {UUID2} \| 42 \| myapp2 \| \| {UUID1} \| \| myapp1 \| When I run `wp user application-password list admin` Then STDOUT should be a table containing rows: \| uuid \| app_id \| name \| password \| created \| last_used \| last_ip \| \| {UUID2} \| 42 \| myapp2 \| {HASH2} \| {CREATED2} \| \| \| \| {UUID1} \| \| myapp1 \| {HASH1} \| {CREATED1} \| \| \| When I run `wp user application-password list admin --orderby=created --order=asc` Then STDOUT should be a table containing rows: \| uuid \| app_id \| name \| password \| created \| last_used \| last_ip \| \| {UUID1} \| \| myapp1 \| {HASH1} \| {CREATED1} \| \| \| \| {UUID2} \| 42 \| myapp2 \| {HASH2} \| {CREATED2} \| \| \| When I run `wp user application-password list admin --orderby=name --order=asc` Then STDOUT should be a table containing rows: \| uuid \| app_id \| name \| password \| created \| last_used \| last_ip \| \| {UUID1} \| \| myapp1 \| {HASH1} \| {CREATED1} \| \| \| \| {UUID2} \| 42 \| myapp2 \| {HASH2} \| {CREATED2} \| \| \| When I run `wp user application-password list admin --orderby=name --order=desc` Then STDOUT should be a table containing rows: \| uuid \| app_id \| name \| password \| created \| last_used \| last_ip \| \| {UUID2} \| 42 \| myapp2 \| {HASH2} \| {CREATED2} \| \| \| \| {UUID1} \| \| myapp1 \| {HASH1} \| {CREATED1} \| \| \| When I run `wp user application-password list admin --name=myapp2 --format=json` Then STDOUT should contain: """ myapp2 """ And STDOUT should not contain: """ myapp1 """ When I run `wp user application-password list admin --field=name` Then STDOUT should contain: """ myapp1 """ And STDOUT should contain: """ myapp2 """ When I run `wp user application-password list 1 --field=name --app-id=42` Then STDOUT should be: """ myapp2 """ When I run `wp user application-password list 1 --format=ids --orderby=name --order=asc` Then STDOUT should be: """ {UUID1} {UUID2} """ # WordPress 6.8 uses BLAKE2b with wp_fast_hash() / wp_verify_fast_hash() for hashing application passwords. # See https://make.wordpress.org/core/2025/02/17/wordpress-6-8-will-use-bcrypt-for-password-hashing/ @require-wp-5.6 @less-than-wp-6.8 Scenario: Get particular user application password hash Given a WP install When I run `wp user create testuser testuser@example.com --porcelain` Then STDOUT should be a number And save STDOUT as {USER_ID} When I try the previous command again Then the return code should be 1 When I run `wp user application-password create {USER_ID} someapp --porcelain` Then save STDOUT as {PASSWORD} When I run `wp user application-password list {USER_ID} --name=someapp --field=uuid` Then save STDOUT as {UUID} When I run `wp user application-password get {USER_ID} {UUID} --field=password \| sed 's/\$/\\\$/g'` Then save STDOUT as {HASH} When I run `wp eval "var_export( wp_check_password( '{PASSWORD}', '{HASH}', {USER_ID} ) );"` Then STDOUT should contain: """ true """ @require-wp-6.8 Scenario: Get particular user application password hash Given a WP install When I run `wp user create testuser testuser@example.com --porcelain` Then STDOUT should be a number And save STDOUT as {USER_ID} When I try the previous command again Then the return code should be 1 When I run `wp user application-password create {USER_ID} someapp --porcelain` Then save STDOUT as {PASSWORD} When I run `wp user application-password list {USER_ID} --name=someapp --field=uuid` Then save STDOUT as {UUID} When I run `wp user application-password get {USER_ID} {UUID} --field=password \| sed 's/\$/\\\$/g'` Then save STDOUT as {HASH} When I run `wp eval "var_export( wp_verify_fast_hash( '{PASSWORD}', '{HASH}', {USER_ID} ) );"` Then STDOUT should contain: """ true """	10.26 KB	2025-09-06 07:07
📄 user-generate.feature Feature: Generate WP users Background: Given a WP install Scenario: Generating and deleting users When I run `wp user list --role=editor --format=count` Then STDOUT should be: """ 0 """ When I run `wp user generate --count=10 --role=editor` And I run `wp user list --role=editor --format=count` Then STDOUT should be: """ 10 """ When I try `wp user list --field=ID \| xargs wp user delete invalid-user --yes` Then STDOUT should contain: """ Success: Removed user """ And STDERR should be: """ Warning: Invalid user ID, email or login: 'invalid-user' """ And the return code should be 0 When I run `wp user list --format=count` Then STDOUT should be: """ 0 """ Scenario: Generating users and outputting ids When I run `wp user generate --count=1 --format=ids` Then save STDOUT as {USER_ID} When I run `wp user update {USER_ID} --display_name="foo"` Then STDOUT should contain: """ Success: """	1.05 KB	2025-05-25 12:40
📄 user-import-csv.feature Feature: Import users from CSV Scenario: Importing users from a CSV file Given a WP install And a users.csv file: """ user_login,user_email,display_name,role bobjones,bobjones@example.com,Bob Jones,contributor newuser1,newuser1@example.com,New User,author admin,admin@example.com,Existing User,administrator """ When I try `wp user import-csv users-incorrect.csv --skip-update` Then STDERR should be: """ Error: Missing file: users-incorrect.csv """ And the return code should be 1 When I run `wp user import-csv users.csv` Then STDOUT should not be empty And an email should not be sent When I run `wp user list --format=count` Then STDOUT should be: """ 3 """ When I run `wp user list --format=json` Then STDOUT should be JSON containing: """ [{ "user_login":"admin", "display_name":"Existing User", "user_email":"admin@example.com", "roles":"administrator" }] """ Scenario: Import new users on multisite Given a WP multisite install And a user-invalid.csv file: """ user_login,user_email,display_name,role bob-jones,bobjones@example.com,Bob Jones,contributor """ And a user-valid.csv file: """ user_login,user_email,display_name,role bobjones,bobjones@example.com,Bob Jones,contributor """ When I try `wp user import-csv user-invalid.csv` # Message changed from "Only lowercase..." to "Usernames can contain only lowercase..." in `wpmu_validate_user_signup()` WP 4.4 https://core.trac.wordpress.org/ticket/33336 Then STDERR should contain: """ lowercase letters (a-z) and numbers """ And the return code should be 0 When I run `wp user import-csv user-valid.csv` Then STDOUT should not be empty And an email should not be sent When I run `wp user get bobjones --field=display_name` Then STDOUT should be: """ Bob Jones """ Scenario: Import new users but don't update existing Given a WP install And a users.csv file: """ user_login,user_email,display_name,role bobjones,bobjones@example.com,Bob Jones,contributor newuser1,newuser1@example.com,New User,author admin,admin@example.com,Existing User,administrator """ When I run `wp user create bobjones bobjones@example.com --display_name="Robert Jones" --role=administrator` Then STDOUT should not be empty When I run `wp user import-csv users.csv --skip-update --send-email` Then STDOUT should not be empty And an email should be sent When I run `wp user list --format=count` Then STDOUT should be: """ 3 """ When I run `wp user get bobjones --fields=user_login,display_name,user_email,roles --format=json` Then STDOUT should be JSON containing: """ { "user_login":"bobjones", "display_name":"Robert Jones", "user_email":"bobjones@example.com", "roles":"administrator" } """ Scenario: Import users from a CSV file generated by `wp user list` Given a WP install When I run `wp user delete 1 --yes` And I run `wp user create bobjones bobjones@example.com --display_name="Bob Jones" --role=contributor` And I run `wp user create billjones billjones@example.com --display_name="Bill Jones" --role=administrator` And I run `wp user add-role billjones author` Then STDOUT should not be empty When I run `wp user list --field=user_login \| wc -l \| tr -d ' '` Then STDOUT should be: """ 2 """ When I run `wp user list --format=csv > users.csv` Then the users.csv file should exist When I run `wp user delete $(wp user list --format=ids) --yes` Then STDOUT should not be empty When I run `wp user list --field=user_login \| wc -l \| tr -d ' '` Then STDOUT should be: """ 0 """ When I run `wp user import-csv users.csv` Then STDOUT should not be empty When I run `wp user list --fields=display_name,roles` Then STDOUT should be a table containing rows: \| display_name \| roles \| \| Bob Jones \| contributor \| \| Bill Jones \| administrator,author \| @broken Scenario: Importing users from STDIN Given a WP install And a users.csv file: """ user_login,user_email,display_name,role bobjones,bobjones@example.com,Bob Jones,contributor newuser1,newuser1@example.com,New User,author admin,admin@example.com,Existing User,administrator """ When I try `wp user import-csv -` Then STDERR should be: """ Error: Unable to read content from STDIN. """ And the return code should be 1 When I run `cat users.csv \| wp user import-csv -` Then STDOUT should be: """ Success: bobjones created. Success: newuser1 created. Success: admin updated. """ And an email should not be sent When I run `wp user list --format=count` Then STDOUT should be: """ 3 """ When I run `wp user list --format=json` Then STDOUT should be JSON containing: """ [{ "user_login":"admin", "display_name":"Existing User", "user_email":"admin@example.com", "roles":"administrator" }] """	5.32 KB	2025-05-25 12:40
📄 user-list.feature Feature: List WordPress users @require-wp-4.4 Scenario: List users of specific roles Given a WP install And I run `wp user create bobjones bob@example.com --role=author` And I run `wp user create sally sally@example.com --role=editor` When I run `wp user list --field=user_login` Then STDOUT should be: """ admin bobjones sally """ When I run `wp user list --role__in=administrator,editor --field=user_login` Then STDOUT should be: """ admin sally """ When I run `wp user list --role__not_in=administrator,editor --field=user_login` Then STDOUT should be: """ bobjones """ @require-wp-4.9 Scenario: List users without roles Given a WP install When I run `wp user create bili bili@example.com --porcelain` Then save STDOUT as {USER_ID} And I run `wp user create sally sally@example.com --role=editor` And I run `wp user remove-role {USER_ID} subscriber` When I run `wp user list --role=none --field=user_login` Then STDOUT should be: """ bili """	1.09 KB	2025-05-25 12:40
📄 user-meta.feature Feature: Manage user custom meta fields Scenario: Usermeta CRUD Given a WP install When I run `wp user-meta add 1 foo 'bar'` Then STDOUT should not be empty When I run `wp user-meta get 1 foo` Then STDOUT should be: """ bar """ When I try `wp user-meta get 2 foo` Then STDERR should be: """ Error: Invalid user ID, email or login: '2' """ And the return code should be 1 When I run `wp user-meta set admin foo '[ "1", "2" ]' --format=json` Then STDOUT should not be empty When I run `wp user-meta get admin foo --format=json` Then STDOUT should be: """ ["1","2"] """ When I run `wp user-meta delete 1 foo` Then STDOUT should not be empty When I try `wp user-meta get 1 foo` Then the return code should be 1 When I run `wp user meta add 1 foo bar` And I run `wp user meta add 1 foo bar2` And I run `wp user meta add 1 foo bar3` Then STDOUT should not be empty When I run `wp user meta delete 1 foo bar2` And I run `wp user meta list 1 --keys=foo --format=count` Then STDOUT should be: """ 2 """ When I run `wp user meta delete 1 foo` And I run `wp user meta list 1 --keys=foo --format=count` Then STDOUT should be: """ 0 """ Scenario: List user meta Given a WP install When I run `wp user meta set 1 foo '[ "1", "2" ]' --format=json` Then STDOUT should not be empty When I run `wp user meta list 1 --format=json --keys=nickname,foo --fields=meta_key,meta_value` Then STDOUT should be JSON containing: """ [{"meta_key":"nickname","meta_value":"admin"},{"meta_key":"foo","meta_value":"a:2:{i:0;s:1:\"1\";i:1;s:1:\"2\";}"}] """ When I run `wp user meta list 1 --format=json --keys=nickname,foo --fields=meta_key,meta_value --unserialize` Then STDOUT should be JSON containing: """ [{"meta_key":"nickname","meta_value":"admin"},{"meta_key":"foo","meta_value":["1","2"]}] """ When I run `wp user meta list 1 --keys=nickname,foo` Then STDOUT should be a table containing rows: \| user_id \| meta_key \| meta_value \| \| 1 \| nickname \| admin \| \| 1 \| foo \| a:2:{i:0;s:1:"1";i:1;s:1:"2";} \| When I run `wp user meta list 1 --keys=nickname,foo --unserialize` Then STDOUT should be a table containing rows: \| user_id \| meta_key \| meta_value \| \| 1 \| nickname \| admin \| \| 1 \| foo \| ["1","2"] \| When I run `wp user meta list admin --keys=nickname,foo` Then STDOUT should be a table containing rows: \| user_id \| meta_key \| meta_value \| \| 1 \| nickname \| admin \| \| 1 \| foo \| a:2:{i:0;s:1:"1";i:1;s:1:"2";} \| When I run `wp user meta list admin --keys=nickname,foo --unserialize` Then STDOUT should be a table containing rows: \| user_id \| meta_key \| meta_value \| \| 1 \| nickname \| admin \| \| 1 \| foo \| ["1","2"] \| When I run `wp user meta list admin --keys=nickname,foo --orderby=id --order=asc` Then STDOUT should be a table containing rows: \| user_id \| meta_key \| meta_value \| \| 1 \| nickname \| admin \| \| 1 \| foo \| a:2:{i:0;s:1:"1";i:1;s:1:"2";} \| When I run `wp user meta list admin --keys=nickname,foo --orderby=id --order=asc --unserialize` Then STDOUT should be a table containing rows: \| user_id \| meta_key \| meta_value \| \| 1 \| nickname \| admin \| \| 1 \| foo \| ["1","2"] \| When I run `wp user meta list admin --keys=nickname,foo --orderby=id --order=desc` Then STDOUT should be a table containing rows: \| user_id \| meta_key \| meta_value \| \| 1 \| foo \| a:2:{i:0;s:1:"1";i:1;s:1:"2";} \| \| 1 \| nickname \| admin \| When I run `wp user meta list admin --keys=nickname,foo --orderby=id --order=desc --unserialize` Then STDOUT should be a table containing rows: \| user_id \| meta_key \| meta_value \| \| 1 \| foo \| ["1","2"] \| \| 1 \| nickname \| admin \| When I run `wp user meta list admin --keys=nickname,foo --orderby=meta_key --order=asc` Then STDOUT should be a table containing rows: \| user_id \| meta_key \| meta_value \| \| 1 \| foo \| a:2:{i:0;s:1:"1";i:1;s:1:"2";} \| \| 1 \| nickname \| admin \| When I run `wp user meta list admin --keys=nickname,foo --orderby=meta_key --order=asc --unserialize` Then STDOUT should be a table containing rows: \| user_id \| meta_key \| meta_value \| \| 1 \| foo \| ["1","2"] \| \| 1 \| nickname \| admin \| When I run `wp user meta list admin --keys=nickname,foo --orderby=meta_key --order=desc` Then STDOUT should be a table containing rows: \| user_id \| meta_key \| meta_value \| \| 1 \| nickname \| admin \| \| 1 \| foo \| a:2:{i:0;s:1:"1";i:1;s:1:"2";} \| When I run `wp user meta list admin --keys=nickname,foo --orderby=meta_key --order=desc --unserialize` Then STDOUT should be a table containing rows: \| user_id \| meta_key \| meta_value \| \| 1 \| nickname \| admin \| \| 1 \| foo \| ["1","2"] \| When I run `wp user meta list admin --keys=nickname,foo --orderby=meta_value --order=asc` Then STDOUT should be a table containing rows: \| user_id \| meta_key \| meta_value \| \| 1 \| nickname \| admin \| \| 1 \| foo \| a:2:{i:0;s:1:"1";i:1;s:1:"2";} \| When I run `wp user meta list admin --keys=nickname,foo --orderby=meta_value --order=asc --unserialize` Then STDOUT should be a table containing rows: \| user_id \| meta_key \| meta_value \| \| 1 \| nickname \| admin \| \| 1 \| foo \| ["1","2"] \| When I run `wp user meta list admin --keys=nickname,foo --orderby=meta_value --order=desc` Then STDOUT should be a table containing rows: \| user_id \| meta_key \| meta_value \| \| 1 \| foo \| a:2:{i:0;s:1:"1";i:1;s:1:"2";} \| \| 1 \| nickname \| admin \| When I run `wp user meta list admin --keys=nickname,foo --orderby=meta_value --order=desc --unserialize` Then STDOUT should be a table containing rows: \| user_id \| meta_key \| meta_value \| \| 1 \| foo \| ["1","2"] \| \| 1 \| nickname \| admin \| Scenario: Get particular user meta Given a WP install When I run `wp user create testuser testuser@example.com --description='This is description' --porcelain` Then STDOUT should be a number And save STDOUT as {USER_ID} When I try the previous command again Then the return code should be 1 When I try `wp user-meta get {USER_ID} description` Then STDOUT should be: """ This is description """	7.31 KB	2025-09-06 07:07
📄 user-reset-password.feature Feature: Reset passwords for one or more WordPress users. @require-wp-4.3 Scenario: Reset the password of a WordPress user Given a WP installation When I run `wp user get 1 --field=user_pass` Then save STDOUT as {ORIGINAL_PASSWORD} When I run `wp user reset-password 1` Then STDOUT should contain: """ Reset password for admin. Success: Password reset for 1 user. """ And an email should be sent When I run `wp user get 1 --field=user_pass` Then STDOUT should not contain: """ {ORIGINAL_PASSWORD} """ @require-wp-4.3 Scenario: Reset the password of a WordPress user, but skip emailing them Given a WP installation When I run `wp user get 1 --field=user_pass` Then save STDOUT as {ORIGINAL_PASSWORD} When I run `wp user reset-password 1 --skip-email` Then STDOUT should contain: """ Reset password for admin. Success: Password reset for 1 user. """ And an email should not be sent When I run `wp user get 1 --field=user_pass` Then STDOUT should not contain: """ {ORIGINAL_PASSWORD} """ @require-wp-4.3 Scenario: Reset the password of a WordPress user, and show the new password Given a WP installation When I run `wp user get 1 --field=user_pass` Then save STDOUT as {ORIGINAL_PASSWORD} When I run `wp user reset-password 1 --skip-email --show-password` Then STDOUT should contain: """ Password: """ And an email should not be sent When I run `wp user get 1 --field=user_pass` Then STDOUT should not contain: """ {ORIGINAL_PASSWORD} """ @require-wp-4.3 Scenario: Reset the password of a WordPress user, and show only the new password Given a WP installation When I run `wp user get 1 --field=user_pass` Then save STDOUT as {ORIGINAL_PASSWORD} When I run `wp user reset-password 1 --skip-email --porcelain` Then STDOUT should not be empty And an email should not be sent When I run `wp user get 1 --field=user_pass` Then STDOUT should not contain: """ {ORIGINAL_PASSWORD} """	2.12 KB	2025-05-25 12:40
📄 user-session.feature Feature: Manage user session Background: Given a WP install @require-wp-4.0 Scenario: Destroy user sessions When I run `wp eval 'wp_set_current_user(1);'` And I run `wp eval 'wp_set_auth_cookie(1);'` And I run `wp eval 'wp_set_current_user(1);'` And I run `wp eval 'wp_set_auth_cookie(1);'` And I run `wp user session list admin --format=count` Then STDOUT should be: """ 2 """ When I run `wp user session destroy admin` Then STDOUT should be: """ Success: Destroyed session. 1 remaining. """ When I run `wp user session list admin --format=count` Then STDOUT should be: """ 1 """ When I run `wp user session destroy admin --all` Then STDOUT should be: """ Success: Destroyed all sessions. """ When I run `wp user session list admin --format=count` Then STDOUT should be: """ 0 """	944 B	2025-09-06 07:07
📄 user-term.feature Feature: Manage user term Scenario: Userterm CRUD Given a WP install And a wp-content/plugins/test-add-tax/plugin.php file: """ <?php // Plugin Name: Test Add Tax function add_cli_tax(){ register_taxonomy( 'user_type', 'user' ); } add_action('init','add_cli_tax'); """ And I run `wp plugin activate test-add-tax` When I run `wp user term add 1 user_type foo` Then STDOUT should be: """ Success: Added term. """ When I run `wp user term list 1 user_type --fields=name,slug,taxonomy` Then STDOUT should be a table containing rows: \| name \| slug \| taxonomy \| \| foo \| foo \| user_type \| When I run `wp user term add 1 user_type bar` Then STDOUT should be: """ Success: Added term. """ When I run `wp user term list 1 user_type --fields=name,slug,taxonomy` Then STDOUT should be a table containing rows: \| name \| slug \| taxonomy \| \| foo \| foo \| user_type \| \| bar \| bar \| user_type \| When I run `wp user term list 1 user_type --format=ids` Then STDOUT should be: """ 3 2 """ When I run `wp user term set 1 user_type new` Then STDOUT should be: """ Success: Set term. """ When I run `wp user term list 1 user_type --fields=name,slug,taxonomy --format=count` Then STDOUT should be: """ 1 """ When I run `wp user term remove 1 user_type new` Then STDOUT should be: """ Success: Removed term. """ When I run `wp user term list 1 user_type --fields=name,slug,taxonomy --format=count` Then STDOUT should be: """ 0 """ Scenario: Multiple user term Given a WP install And a wp-content/plugins/test-add-tax/plugin.php file: """ <?php // Plugin Name: Test Add Tax function add_cli_tax(){ register_taxonomy( 'user_type', 'user' ); } add_action('init','add_cli_tax'); """ And I run `wp plugin activate test-add-tax` When I run `wp user term add 1 user_type apple` And I run `wp user term add 1 user_type apple` Then STDOUT should contain: """ Success: Added term. """ When I run `wp user term set 1 user_type apple1 apple2` Then STDOUT should contain: """ Success: Set terms. """ When I run `wp user term list 1 user_type --format=json --fields=name,slug,taxonomy` Then STDOUT should contain: """ [{"name":"apple1","slug":"apple1","taxonomy":"user_type"},{"name":"apple2","slug":"apple2","taxonomy":"user_type"}] """ Scenario: Userterm Add invalid tax Given a WP install When I try `wp user term add 1 boo foo2` Then the return code should be 1 And STDERR should be: """ Error: Invalid taxonomy boo. """	2.82 KB	2025-09-06 07:07
📄 user.feature Feature: Manage WordPress users Scenario: User CRUD operations Given a WP install When I try `wp user get bogus-user` Then the return code should be 1 And STDOUT should be empty When I run `wp user create testuser2 testuser2@example.com --first_name=test --last_name=user --role=author --porcelain` Then STDOUT should be a number And save STDOUT as {USER_ID} When I run `wp user get {USER_ID}` Then STDOUT should be a table containing rows: \| Field \| Value \| \| ID \| {USER_ID} \| \| roles \| author \| When I run `wp user exists {USER_ID}` Then STDOUT should be: """ Success: User with ID {USER_ID} exists. """ And the return code should be 0 When I try `wp user exists 1000` Then STDOUT should be empty And the return code should be 1 When I run `wp user get {USER_ID} --field=user_registered` Then STDOUT should not contain: """ 0000-00-00 00:00:00 """ When I run `wp user meta get {USER_ID} first_name` Then STDOUT should be: """ test """ When I run `wp user list --fields=user_login,roles` Then STDOUT should be a table containing rows: \| user_login \| roles \| \| testuser2 \| author \| When I run `wp user meta get {USER_ID} last_name` Then STDOUT should be: """ user """ When I run `wp user delete {USER_ID} --yes` Then STDOUT should not be empty When I try `wp user create testuser2 testuser2@example.com --role=wrongrole --porcelain` Then the return code should be 1 And STDOUT should be empty When I run `wp user create testuser testuser@example.com --porcelain` Then STDOUT should be a number And save STDOUT as {USER_ID} When I try the previous command again Then the return code should be 1 When I run `wp user update {USER_ID} --display_name=Foo` And I run `wp user get {USER_ID}` Then STDOUT should be a table containing rows: \| Field \| Value \| \| ID \| {USER_ID} \| \| display_name \| Foo \| When I run `wp user get testuser@example.com` Then STDOUT should be a table containing rows: \| Field \| Value \| \| ID \| {USER_ID} \| \| display_name \| Foo \| When I run `wp user delete {USER_ID} --yes` Then STDOUT should not be empty When I run `wp user create testuser3 testuser3@example.com --user_pass=testuser3pass` Then STDOUT should not contain: """ Password: """ # Check with valid password. When I run `wp user check-password testuser3 testuser3pass` Then the return code should be 0 # Check with invalid password. When I try `wp user check-password testuser3 invalidpass` Then the return code should be 1 When I try `wp user check-password invaliduser randomstring` Then STDERR should contain: """ Invalid user ID, email or login: 'invaliduser' """ And the return code should be 1 When I run `wp user create testuser3b testuser3b@example.com --user_pass="test\"user3b's\pass\!"` Then STDOUT should not contain: """ Password: """ # Check password without the `--escape-chars` option. When I try `wp user check-password testuser3b "test\"user3b's\pass\!"` Then STDERR should be: """ Warning: Password contains characters that need to be escaped. Please escape them manually or use the `--escape-chars` option. """ And the return code should be 1 # Check password with the `--escape-chars` option. When I try `wp user check-password testuser3b "test\"user3b's\pass\!" --escape-chars` Then the return code should be 0 # Check password with manually escaped characters. When I try `wp user check-password testuser3b "test\\\"user3b\'s\\\pass\\\!"` Then the return code should be 0 Scenario: Reassigning user posts Given a WP multisite install When I run `wp user create bobjones bob@example.com --role=author --porcelain` Then save STDOUT as {BOB_ID} When I run `wp user create sally sally@example.com --role=editor --porcelain` Then save STDOUT as {SALLY_ID} When I run `wp post generate --count=3 --post_author=bobjones` And I run `wp post list --author={BOB_ID} --format=count` Then STDOUT should be: """ 3 """ When I run `wp user delete bobjones --reassign={SALLY_ID}` And I run `wp post list --author={SALLY_ID} --format=count` Then STDOUT should be: """ 3 """ When I try `wp user update 9999 --user_pass=securepassword` Then the return code should be 1 And STDERR should contain: """ Error: No valid users found. """ Scenario: Delete user with invalid reassign Given a WP install And a session_no file: """ n """ And a session_yes file: """ y """ When I run `wp user create bobjones bob@example.com --role=author --porcelain` Then save STDOUT as {BOB_ID} When I run `wp post list --format=count` Then save STDOUT as {TOTAL_POSTS} When I run `wp post generate --count=3 --format=ids --post_author=bobjones` And I run `wp post list --author={BOB_ID} --format=count` Then STDOUT should be: """ 3 """ When I run `wp user delete bobjones < session_no` Then STDOUT should contain: """ --reassign parameter not passed. All associated posts will be deleted. Proceed? [y/n] """ When I run `wp user delete bobjones --reassign=99999 < session_no` Then STDOUT should contain: """ --reassign parameter is invalid. All associated posts will be deleted. Proceed? [y/n] """ When I run `wp user delete bobjones < session_yes` And I run `wp post list --format=count` Then STDOUT should be: """ {TOTAL_POSTS} """ Scenario: Deleting user from the whole network Given a WP multisite install When I run `wp user create bobjones bob@example.com --role=author --porcelain` Then save STDOUT as {BOB_ID} When I run `wp user get bobjones` Then STDOUT should not be empty When I run `wp user delete bobjones --network --yes` Then STDOUT should not be empty When I try `wp user get bobjones` Then STDERR should not be empty And the return code should be 1 Scenario: Trying to delete existing user with no roles from a subsite Given a WP multisite install When I run `wp user create bobjones bob@example.com --role=author --url=https://example.com --porcelain` Then save STDOUT as {BOB_ID} When I run `wp user delete bobjones --yes` Then STDOUT should contain: """ Success: Removed user """ And STDERR should be empty When I try `wp user delete bobjones --yes` Then STDERR should be: """ Warning: No roles found for user {BOB_ID} on https://example.com, no users deleted. """ And the return code should be 1 @require-wp-4.0 Scenario: Trying to delete super admin Given a WP multisite install When I run `wp user create bobjones bob@example.com --role=author --porcelain` Then save STDOUT as {BOB_ID} When I run `wp super-admin add {BOB_ID}` And I try `wp user delete bobjones --network --yes` Then STDERR should be: """ Warning: Failed deleting user {BOB_ID}. The user is a super admin. """ And the return code should be 1 Scenario: Create new users on multisite Given a WP multisite install When I try `wp user create bob-jones bobjones@example.com` Then STDERR should contain: """ lowercase letters (a-z) and numbers """ And the return code should be 1 When I run `wp user create bobjones bobjones@example.com --display_name="Bob Jones"` Then STDOUT should not be empty When I run `wp user get bobjones --field=display_name` Then STDOUT should be: """ Bob Jones """ Scenario: Managing user roles Given a WP install When I try `wp user add-role 1` Then the return code should be 1 And STDERR should be: """ Error: Please specify at least one role to add. """ And STDOUT should be empty When I run `wp user add-role 1 editor` Then STDOUT should be: """ Success: Added 'editor' role for admin (1). """ When I run `wp user get 1 --field=roles` Then STDOUT should be: """ administrator, editor """ When I run `wp user add-role 1 editor contributor` Then STDOUT should be: """ Success: Added 'editor', 'contributor' roles for admin (1). """ When I run `wp user get 1 --field=roles` Then STDOUT should be: """ administrator, editor, contributor """ When I run `wp user remove-role 1 editor contributor` Then STDOUT should be: """ Success: Removed 'editor', 'contributor' roles from admin (1). """ When I run `wp user get 1 --field=roles` Then STDOUT should be: """ administrator """ When I try `wp user add-role 1 edit` Then STDERR should contain: """ Role doesn't exist """ And the return code should be 1 When I try `wp user set-role 1 edit` Then STDERR should contain: """ Role doesn't exist """ And the return code should be 1 When I try `wp user remove-role 1 edit` Then STDERR should contain: """ Role doesn't exist """ And the return code should be 1 When I run `wp user set-role 1 author` Then STDOUT should not be empty When I run `wp user get 1` Then STDOUT should be a table containing rows: \| Field \| Value \| \| roles \| author \| When I run `wp user remove-role 1 editor` Then STDOUT should not be empty When I run `wp user get 1` Then STDOUT should be a table containing rows: \| Field \| Value \| \| roles \| author \| When I run `wp user remove-role 1` Then STDOUT should not be empty When I run `wp user get 1` Then STDOUT should be a table containing rows: \| Field \| Value \| \| roles \| \| Scenario: Invalid User Role Given a WP install When I run `wp user create testuser4 testemail4@example.com` And I try `wp user update testuser4 --role=banana` Then STDERR should be: """ Warning: Role doesn't exist: banana """ And STDOUT should contain: """ Success: """ And the return code should be 0 When I run `wp user get admin --field=roles` Then STDOUT should be: """ administrator """ Scenario: Managing user capabilities Given a WP install When I run `wp user add-cap 1 edit_vip_product` Then STDOUT should be: """ Success: Added 'edit_vip_product' capability for admin (1). """ When I run `wp user list-caps 1 \| tail -n 1` Then STDOUT should be: """ edit_vip_product """ When I run `wp user remove-cap 1 edit_vip_product` Then STDOUT should be: """ Success: Removed 'edit_vip_product' cap for admin (1). """ When I try the previous command again Then the return code should be 1 And STDERR should be: """ Error: No such 'edit_vip_product' cap for admin (1). """ And STDOUT should be empty When I run `wp user list-caps 1` Then STDOUT should not contain: """ edit_vip_product """ And STDOUT should contain: """ publish_posts """ When I try `wp user remove-cap 1 publish_posts` Then the return code should be 1 And STDERR should be: """ Error: The 'publish_posts' cap for admin (1) is inherited from a role. """ And STDOUT should be empty When I run `wp user list-caps 1` Then STDOUT should contain: """ publish_posts """ Scenario: Show error when trying to remove capability same as role Given a WP install When I run `wp user create testuser2 testuser2@example.com --first_name=test --last_name=user --role=contributor --porcelain` Then STDOUT should be a number And save STDOUT as {USER_ID} When I run `wp user list-caps {USER_ID}` Then STDOUT should contain: """ contributor """ When I run `wp user get {USER_ID} --field=roles` Then STDOUT should contain: """ contributor """ When I try `wp user remove-cap {USER_ID} contributor` Then the return code should be 1 And STDERR should be: """ Error: Aborting because a role has the same name as 'contributor'. Use `wp user remove-cap {USER_ID} contributor --force` to proceed with the removal. """ And STDOUT should be empty When I run `wp user remove-cap {USER_ID} contributor --force` Then STDOUT should be: """ Success: Removed 'contributor' cap for testuser2 ({USER_ID}). """ Scenario: Show password when creating a user Given a WP install When I run `wp user create testrandompass testrandompass@example.com` Then STDOUT should contain: """ Password: """ When I run `wp user create testsuppliedpass testsuppliedpass@example.com --user_pass=suppliedpass` Then STDOUT should not contain: """ Password: """ Scenario: List network users Given a WP multisite install When I run `wp user create testsubscriber testsubscriber@example.com` Then STDOUT should contain: """ Success: Created user """ When I run `wp user list --field=user_login` Then STDOUT should contain: """ testsubscriber """ When I run `wp user delete testsubscriber --yes` Then STDOUT should contain: """ Success: Removed user """ When I run `wp user list --field=user_login` Then STDOUT should not contain: """ testsubscriber """ When I run `wp user list --field=user_login --network` Then STDOUT should contain: """ testsubscriber """ Scenario: Listing user capabilities Given a WP install When I run `wp user create bob bob@gmail.com --role=contributor` And I run `wp user list-caps bob` Then STDOUT should be: """ edit_posts read level_1 level_0 delete_posts contributor """ When I run `wp user list-caps bob --format=json` Then STDOUT should be: """ [{"name":"edit_posts"},{"name":"read"},{"name":"level_1"},{"name":"level_0"},{"name":"delete_posts"},{"name":"contributor"}] """ When I run `wp user list-caps bob --format=count` Then STDOUT should be: """ 6 """ When I run `wp user list-caps bob --exclude-role-names` Then STDOUT should be: """ edit_posts read level_1 level_0 delete_posts """ When I run `wp user add-cap bob newcap` And I run `wp user list-caps bob --origin=role` Then STDOUT should be: """ edit_posts read level_1 level_0 delete_posts contributor """ When I run `wp user list-caps bob --origin=user` Then STDOUT should be: """ newcap """ Scenario: Make sure WordPress receives the slashed data it expects Given a WP install When I run `wp user create slasheduser slasheduser@example.com --display_name='My\User' --porcelain` Then save STDOUT as {USER_ID} When I run `wp user get {USER_ID} --field=display_name` Then STDOUT should be: """ My\User """ When I run `wp user update {USER_ID} --display_name='My\New\User'` Then STDOUT should not be empty When I run `wp user get {USER_ID} --field=display_name` Then STDOUT should be: """ My\New\User """ Scenario: Don't send user creation emails by default Given a WP multisite install When I run `wp user create testuser2 testuser2@example.com` Then an email should not be sent When I run `wp user create testuser3 testuser3@example.com --send-email` Then an email should be sent Scenario: List URLs of one or more users Given a WP install And I run `wp user create bob bob@gmail.com --role=contributor` When I run `wp user list --include=1,2 --field=url` Then STDOUT should be: """ https://example.com/?author=1 https://example.com/?author=2 """ Scenario: Get user with email as login Given a WP install And I run `wp user create testuser4@example.com testemail4@example.com` When I run `wp user get testemail4@example.com --field=user_login` Then STDOUT should be: """ testuser4@example.com """ When I run `wp user get testuser4@example.com --field=user_login` Then STDOUT should be: """ testuser4@example.com """ Scenario: Mark/remove a user from spam Given a WP multisite install And I run `wp user create bumblebee bbee@example.com --role=author --porcelain` And save STDOUT as {BBEE_ID} And I run `wp user create oprime oprime@example.com --role=author --porcelain` And save STDOUT as {OP_ID} And I run `wp user get bumblebee` And STDOUT should not be empty And I run `wp user get oprime` And STDOUT should not be empty When I run `wp site create --slug=foo --porcelain` Then save STDOUT as {SPAM_SITE_ID} When I run `wp --url=example.com/foo user set-role {BBEE_ID} administrator` Then STDOUT should contain: """ Success: """ When I run `wp user spam {BBEE_ID}` Then STDOUT should be: """ User {BBEE_ID} marked as spam. Success: Spammed 1 of 1 users. """ When I try the previous command again Then STDERR should be: """ Warning: User {BBEE_ID} already marked as spam. """ And STDOUT should be: """ Success: User already spammed. """ And the return code should be 0 When I run `wp site list --site__in=1 --field=spam` Then STDOUT should be: """ 0 """ When I run `wp site list --site__in={SPAM_SITE_ID} --field=spam` Then STDOUT should be: """ 1 """ When I try `wp user spam {OP_ID} 9999` Then STDOUT should be: """ User {OP_ID} marked as spam. """ And STDERR should be: """ Warning: Invalid user ID, email or login: '9999' Error: Only spammed 1 of 2 users. """ And the return code should be 1 When I run `wp user unspam {BBEE_ID}` Then STDOUT should contain: """ Success: """ When I run `wp site list --site__in=1 --field=spam` Then STDOUT should be: """ 0 """ When I run `wp site list --site__in={SPAM_SITE_ID} --field=spam` Then STDOUT should be: """ 0 """ @require-wp-4.3 Scenario: Sending emails on update Given a WP install When I run `wp user get 1 --field=user_email` Then save STDOUT as {ORIGINAL_EMAIL} When I run `wp user update 1 --user_email=different.mail@example.com` Then STDOUT should contain: """ Success: Updated user 1. """ And an email should be sent When I run `wp user update 1 --user_email={ORIGINAL_EMAIL} --skip-email` Then STDOUT should contain: """ Success: Updated user 1. """ And an email should not be sent When I run `wp user get 1 --field=user_pass` Then save STDOUT as {ORIGINAL_PASSWORD} When I run `wp user update 1 --user_pass=different_password` Then STDOUT should contain: """ Success: Updated user 1. """ And an email should be sent When I run `wp user update 1 --user_pass={ORIGINAL_PASSWORD} --skip-email` Then STDOUT should contain: """ Success: Updated user 1. """ And an email should not be sent Scenario: Set user url when creating a user Given a WP install And I run `wp user create testurl sample@email.com --user_url='http://www.testsite.com'` When I run `wp user get testurl --fields=user_url` Then STDOUT should be a table containing rows: \| Field \| Value \| \| user_url \| http://www.testsite.com \| Scenario: Support nickname creating and updating user Given a WP install When I run `wp user create testuser testuser@example.com --nickname=customtestuser --porcelain` Then STDOUT should be a number And save STDOUT as {USER_ID} When I run `wp user meta get {USER_ID} nickname` Then STDOUT should be: """ customtestuser """ When I run `wp user update {USER_ID} --nickname=newtestuser` And I run `wp user meta get {USER_ID} nickname` Then STDOUT should be: """ newtestuser """	20.52 KB	2025-09-06 07:07

Edit File:

Terminal