OXIESEC PANEL

Name	Size	Modified	Perms
📁 ..	-	09/06/2025 12:29:47 PM	rwxr-xr-x
📄 comment-generate.feature	905 bytes	03/20/2024 11:17:27 AM	rw-r--r--
📄 comment-list.feature	1.04 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 comment-meta.feature	2.33 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 comment-recount.feature	877 bytes	05/14/2024 01:45:25 PM	rw-r--r--
📄 comment.feature	13.17 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 menu-item.feature	7.68 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 menu-location.feature	1.88 KB	05/14/2024 01:45:25 PM	rw-r--r--
📄 menu.feature	2.05 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 network-meta.feature	418 bytes	03/20/2024 11:17:27 AM	rw-r--r--
📄 option-get-autoload.feature	826 bytes	05/14/2024 01:45:25 PM	rw-r--r--
📄 option-list.feature	5.89 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 option-pluck-patch.feature	7.73 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 option-set-autoload.feature	1.96 KB	05/14/2024 01:45:25 PM	rw-r--r--
📄 option.feature	8.17 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 post-create-duplicate.feature	2.79 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 post-generate.feature	5.71 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 post-meta-clean-duplicates.feature	1.67 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 post-meta.feature	14.7 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 post-term.feature	5.37 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 post-type.feature	1.46 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 post-url-to-id.feature	564 bytes	05/14/2024 01:45:25 PM	rw-r--r--
📄 post.feature	16.49 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 signup.feature	5.52 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 site-create.feature	3.36 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 site-empty.feature	4.2 KB	05/14/2024 01:45:25 PM	rw-r--r--
📄 site-generate.feature	3.38 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 site-meta.feature	864 bytes	03/20/2024 11:17:27 AM	rw-r--r--
📄 site-option-pluck-patch.feature	6.83 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 site-option.feature	3.64 KB	05/14/2024 01:45:25 PM	rw-r--r--
📄 site.feature	20.81 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 taxonomy.feature	5.6 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 term-generate.feature	810 bytes	03/20/2024 11:17:27 AM	rw-r--r--
📄 term-meta.feature	849 bytes	03/20/2024 11:17:27 AM	rw-r--r--
📄 term-migrate.feature	2.97 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 term-recount.feature	1.6 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 term.feature	8 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 user-application-password.feature	10.26 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 user-generate.feature	1.05 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 user-import-csv.feature	5.32 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 user-list.feature	1.09 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 user-meta.feature	7.31 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 user-reset-password.feature	2.12 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 user-session.feature	944 bytes	09/06/2025 12:29:47 PM	rw-r--r--
📄 user-term.feature	2.82 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 user.feature	20.52 KB	09/06/2025 12:29:47 PM	rw-r--r--

Editing: 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 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 --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=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_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=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_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=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                               |

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
      """