WordPress Help
Official documentation, learning resources, and contributor guides collected from WordPress.org.
-
Dann /^STDOUT sollte CSV enthalten:$/
Erwarten Sie, dass STDOUT CSV enthält, das bestimmte Werte enthält. Verwendung Scenario: My example scenario When I run `wp term list post_tag –fields=name,slug –format=csv` Then STDOUT should be CSV containing: | name | slug | | Test term | test | Die Dokumentation der Behat-Schritte wird bei jeder Veröffentlichung aus der WP-CLIWP-CLI WP-CLI ist die…
-
Alors /^STDOUT devrait être un CSV contenant:$/
S’attendre à ce que STDOUT soit un fichier CSV contenant certaines valeurs. Utilisation Scenario: My example scenario When I run `wp term list post_tag –fields=name,slug –format=csv` Then STDOUT should be CSV containing: | name | slug | | Test term | test | La documentation des étapes Behat est générée à partir de la base…
-
Entonces /^STDOUT debería ser un CSV que contenga:$/
Esperar que STDOUT sea un CSV que contenga ciertos valores. Uso Escenario: Mi escenario de ejemplo Cuando ejecuto `wp term list post_tag –fields=name,slug –format=csv` Entonces STDOUT debería ser un CSV que contenga: | name | slug | | Test term | test | La documentación de los pasos de Behat se genera a partir del…
-
Then /^STDOUT should be a table containing rows:$/
Expect STDOUT to be a table containing the given rows. Usage Scenario: My example scenario Given a WP installation When I run `wp config list –fields=name,type` Then STDOUT should be a table containing rows: | name | type | | DB_NAME | constant | | DB_USER | constant | Behat steps documentation is generated from…
-
Then /^STDOUT should be a JSON array containing:$/
Expect valid JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. array output in STDOUT. Usage Errors when some items are missing from the expected array. Scenario: My example scenario When I…
-
Then /^(STDOUT|STDERR) should be empty$/
Expect STDOUT or STDERR to be empty. Usage Scenario: My other scenario Given a WP install When I run `wp plugin install akismet` Then STDERR should be empty Behat steps documentation is generated from the WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way.…
-
Then /^(STDOUT|STDERR) should be a version string (<|<=|>|>=|==|=|!=|<>) ([+w.{}-]+)$/
Expect STDOUT or STDERR to be a version string comparing to the given version. Usage Scenario: My example scenario Given a WP install When I run `wp core version Then STDOUT should be a version string >= 6.8 Behat steps documentation is generated from the WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used…
-
Then /^(STDOUT|STDERR) should be a number$/
Expect STDOUT or STDERR to be a numeric value. Usage Scenario: My example scenario Given a WP installation When I run `wp db size –size_format=b` Then STDOUT should be a number Behat steps documentation is generated from the WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in…
-
Then /^STDOUT should end with a table containing rows:$/
Expect STDOUT to end with a table containing the given rows. Usage Useful when the table is preceded by some other output. Scenario: My example scenario Given a WP installation When I run `wp search-replace foo bar –report-changed-only` Then STDOUT should contain: “”” Success: Made 3 replacements. “”” And STDOUT should end with a table…
-
Then /^STDOUT should be YAML containing:$/
Expect STDOUT to be YAML containing certain content. Usage Scenario: My example scenario When I run `wp cli alias list` Then STDOUT should be YAML containing: “”” @all: Run command against every registered alias. @foo: path: {TEST_DIR}/foo “”” Behat steps documentation is generated from the WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used…