Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2444 from wp-cli/2383-term-meta
Manage term meta with `wp term meta`
- Loading branch information
Showing
2 changed files
with
72 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
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. | ||
""" | ||
|
||
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 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters