Repository navigation
Expand file tree
/
Copy pathbootstrap.feature
More file actions
98 lines (87 loc) 路 3.14 KB
/
Copy pathbootstrap.feature
File metadata and controls
98 lines (87 loc) 路 3.14 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
Feature: Bootstrap WP-CLI
Scenario: Override command bundled with freshly built PHAR
Given an empty directory
And a new Phar with the same version
And a cli-override-command/cli.php file:
"""
<?php
if ( ! class_exists( 'WP_CLI' ) ) {
return;
}
$autoload = __DIR__ . '/vendor/autoload.php';
if ( file_exists( $autoload ) ) {
require_once $autoload;
}
WP_CLI::add_command( 'cli', 'CLI_Command', array( 'when' => 'before_wp_load' ) );
"""
And a cli-override-command/src/CLI_Command.php file:
"""
<?php
class CLI_Command extends WP_CLI_Command {
public function version() {
WP_CLI::success( 'WP-Override-CLI' );
}
}
"""
And a cli-override-command/composer.json file:
"""
{
"name": "wp-cli/cli-override",
"description": "A command that overrides the bundled 'cli' command.",
"autoload": {
"psr-4": { "": "src/" },
"files": [ "cli.php" ]
},
"extra": {
"commands": [
"cli"
]
}
}
"""
And I run `composer install --working-dir={RUN_DIR}/cli-override-command --no-interaction 2>&1`
When I run `{PHAR_PATH} cli version`
Then STDOUT should contain:
"""
WP-CLI
"""
When I run `{PHAR_PATH} --require=cli-override-command/cli.php cli version`
Then STDOUT should contain:
"""
WP-Override-CLI
"""
Scenario: Template paths should be resolved correctly when PHAR is renamed
Given an empty directory
And a new Phar with the same version
And a WP installation
And I run `wp plugin install https://github.com/wp-cli-test/generic-example-plugin/releases/download/v0.1.1/generic-example-plugin.0.1.1.zip --activate`
And I run `wp plugin deactivate generic-example-plugin`
When I run `php {PHAR_PATH} plugin get generic-example-plugin --fields=title,status --format=csv`
Then STDOUT should contain:
"""
title,"Example Plugin"
status,inactive
"""
And STDERR should be empty
When I run `cp {PHAR_PATH} wp-renamed.phar`
And I try `php wp-renamed.phar plugin get generic-example-plugin --fields=title,status --format=csv`
Then STDOUT should contain:
"""
title,"Example Plugin"
status,inactive
"""
And STDERR should be empty
Scenario: Config template resolves when the PHAR is renamed and run against another path
# Reproduces the reported failure: a Phar renamed away from `wp-cli.phar`
# (here without an extension) generating a wp-config.php for an install in a
# different directory via --path. See https://github.com/wp-cli/config-command/issues/141
Given an empty directory
And a new Phar with the same version
When I run `cp {PHAR_PATH} wp-renamed`
And I run `php wp-renamed core download --path=subfolder`
And I run `php wp-renamed config create --path=subfolder --dbname=wordpress --dbuser=root --dbpass=password --skip-check`
Then STDOUT should contain:
"""
Success: Generated 'wp-config.php' file.
"""
And STDERR should be empty