Gecko [ fernandoquevedodop.com ]

Name	Size	Permission
aliases.feature	15.82 KB	-rw-r--r--
bootstrap.feature	14.43 KB	-rw-r--r--
class-wp-cli.feature	570 B	-rw-r--r--
cli-bash-completion.feature	7.13 KB	-rw-r--r--
cli-cache.feature	2.12 KB	-rw-r--r--
cli-check-update.feature	10.09 KB	-rw-r--r--
cli-info.feature	1.25 KB	-rw-r--r--
cli.feature	2.52 KB	-rw-r--r--
command.feature	37.85 KB	-rw-r--r--
config.feature	18.61 KB	-rw-r--r--
context.feature	5.68 KB	-rw-r--r--
flags.feature	9.63 KB	-rw-r--r--
formatter.feature	5.73 KB	-rw-r--r--
framework.feature	11.22 KB	-rw-r--r--
help.feature	33.66 KB	-rw-r--r--
hook.feature	6.09 KB	-rw-r--r--
prompt.feature	5.14 KB	-rw-r--r--
requests.feature	3.62 KB	-rw-r--r--
runcommand.feature	10.41 KB	-rw-r--r--
runner.feature	2.6 KB	-rw-r--r--
skip-plugins.feature	3.35 KB	-rw-r--r--
skip-themes.feature	5.52 KB	-rw-r--r--
steps.feature	1.78 KB	-rw-r--r--
utils-wp.feature	22.54 KB	-rw-r--r--
utils.feature	6.71 KB	-rw-r--r--
validation.feature	1.16 KB	-rw-r--r--
wp-config.feature	1.11 KB	-rw-r--r--

Code Editor : runner.feature

Feature: Runner WP-CLI

Scenario: Path argument should be slashed correctly
    When I try `wp no-such-command --path=/foo --debug`
    Then STDERR should contain:
      """
      ABSPATH defined: /foo/
      """

When I try `wp no-such-command --path=/foo/ --debug`
    Then STDERR should contain:
      """
      ABSPATH defined: /foo/
      """

When I try `wp no-such-command --path=/foo\\ --debug`
    Then STDERR should contain:
      """
      ABSPATH defined: /foo/
      """

Scenario: ABSPATH can be defined outside of WP-CLI
    Given an empty directory
    And a wp-cli.yml file:
      """
      require:
        - abspath.php
      """
    And a abspath.php file:
      """
      <?php
      if ( ! defined( 'ABSPATH' ) ) {
          define( 'ABSPATH', '/some_path/' );
      }
      """

When I try `wp no-such-command --debug`
    Then STDERR should not contain:
      """
      Constant ABSPATH already defined in
      """
    And STDERR should contain:
      """
      ABSPATH defined: /some_path/
      """

When I try `wp no-such-command --path=/foo --debug`
    Then STDERR should contain:
      """
      The --path parameter cannot be used when ABSPATH is already defined elsewhere
      """

Scenario: Empty path argument should be handled correctly
    When I try `wp no-such-command --path`
    Then STDERR should contain:
      """
      The --path parameter cannot be empty when provided
      """

When I try `wp no-such-command --path=`
    Then STDERR should contain:
      """
      The --path parameter cannot be empty when provided
      """

When I try `wp no-such-command --path= some_path`
    Then STDERR should contain:
      """
      The --path parameter cannot be empty when provided
      """

Scenario: Suggest 'meta' when 'option' subcommand is run
    Given a WP install

When I try `wp network option`
    Then STDERR should contain:
      """
      Error: 'option' is not a registered subcommand of 'network'. See 'wp help network' for available subcommands.
      Did you mean 'meta'?
      """
    And the return code should be 1

Scenario: Suggest 'wp term <command>' when an invalid taxonomy command is run
    Given a WP install

When I try `wp category list`
    Then STDERR should contain:
      """
      Did you mean 'wp term <command>'?
      """
    And the return code should be 1

Scenario: Suggest 'wp post <command>' when an invalid post type command is run
    Given a WP install

When I try `wp page create`
    Then STDERR should contain:
      """
      Did you mean 'wp post --post_type=page <command>'?
      """
    And the return code should be 1

${this.title}

Code Editor : runner.feature