-
Notifications
You must be signed in to change notification settings - Fork 73
Expand file tree
/
Copy pathdb-export.feature
More file actions
189 lines (154 loc) · 6.04 KB
/
Copy pathdb-export.feature
File metadata and controls
189 lines (154 loc) · 6.04 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
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
Feature: Export a WordPress database
Scenario: Database exports with random hash applied
Given a WP install
When I run `wp db export --porcelain`
Then STDOUT should contain:
"""
wp_cli_test-
"""
And the wp_cli_test.sql file should not exist
Scenario: Database export to a specified file path
Given a WP install
When I run `wp db export wp_cli_test.sql --porcelain`
Then STDOUT should contain:
"""
wp_cli_test.sql
"""
And the wp_cli_test.sql file should exist
@skip-sqlite
Scenario: Exclude tables when exporting the database
Given a WP install
When I try `wp db export wp_cli_test.sql --exclude_tables=wp_users --porcelain`
Then the wp_cli_test.sql file should exist
And the contents of the wp_cli_test.sql file should not match /CREATE TABLE ["`]?wp_users["`]?/
And the contents of the wp_cli_test.sql file should match /CREATE TABLE ["`]?wp_options["`]?/
@skip-sqlite
Scenario: Include only specific tables when exporting the database
Given a WP install
When I try `wp db export wp_cli_test.sql --tables=wp_users --porcelain`
Then the wp_cli_test.sql file should exist
And the contents of the wp_cli_test.sql file should match /CREATE TABLE ["`]?wp_users["`]?/
And the contents of the wp_cli_test.sql file should not match /CREATE TABLE ["`]?wp_posts["`]?/
And the contents of the wp_cli_test.sql file should not match /CREATE TABLE ["`]?wp_options["`]?/
@require-sqlite
Scenario: Exclude tables when exporting the database
Given a WP install
When I try `wp db export wp_cli_test.sql --exclude_tables=wp_users --porcelain`
Then the wp_cli_test.sql file should exist
And the contents of the wp_cli_test.sql file should not match /_mysql_data_types_cache/
And the contents of the wp_cli_test.sql file should not match /CREATE TABLE ["`]?wp_users["`]?/
And the contents of the wp_cli_test.sql file should match /CREATE TABLE ["`]?wp_options["`]?/
@require-sqlite
Scenario: Include only specific tables when exporting the database
Given a WP install
When I try `wp db export wp_cli_test.sql --tables=wp_users --porcelain`
Then the wp_cli_test.sql file should exist
And the contents of the wp_cli_test.sql file should not match /_mysql_data_types_cache/
And the contents of the wp_cli_test.sql file should match /CREATE TABLE ["`]?wp_users["`]?/
And the contents of the wp_cli_test.sql file should not match /CREATE TABLE ["`]?wp_posts["`]?/
And the contents of the wp_cli_test.sql file should not match /CREATE TABLE ["`]?wp_options["`]?/
@require-sqlite
Scenario: Export database to STDOUT
Given a WP install
When I run `wp db export -`
Then STDOUT should contain:
"""
PRAGMA foreign_keys=OFF
"""
@skip-mariadb @skip-sqlite
Scenario: Exclude data of certain tables is not supported by MySQL
Given a WP install
When I try `wp db export wp_cli_test.sql --exclude_tables_data=wp_users`
Then the return code should be 1
And STDERR should contain:
"""
Error: The --exclude_tables_data option is only supported by MariaDB.
"""
# Only MariaDB currently supports this feature.
@require-mariadb
Scenario: Exclude data of certain tables when exporting the database
Given a WP install
When I run `wp db export wp_cli_test.sql --exclude_tables_data=wp_users --porcelain`
Then the wp_cli_test.sql file should exist
And the wp_cli_test.sql file should contain:
"""
wp_users
"""
And the wp_cli_test.sql file should not contain:
"""
INSERT INTO `wp_users`
"""
@skip-sqlite
Scenario: Export database to STDOUT
Given a WP install
When I run `wp db export -`
Then STDOUT should contain:
"""
-- Dump completed on
"""
@skip-sqlite
Scenario: Export database with mysql defaults to STDOUT
Given a WP install
When I run `wp db export --defaults -`
Then STDOUT should contain:
"""
-- Dump completed on
"""
@skip-sqlite
Scenario: Export database with mysql --no-defaults to STDOUT
Given a WP install
When I run `wp db export --no-defaults -`
Then STDOUT should contain:
"""
-- Dump completed on
"""
@skip-sqlite
Scenario: Export database with passed-in options
Given a WP install
When I run `wp db export - --dbpass=password1 --skip-comments`
Then STDOUT should not contain:
"""
-- Table structure
"""
When I try `wp db export - --dbpass=no_such_pass`
Then the return code should not be 0
And STDERR should contain:
"""
Access denied
"""
And STDOUT should be empty
@require-sqlite
Scenario: Export database with passed-in options
Given a WP install
When I run `wp db export - --skip-comments`
Then STDOUT should not contain:
"""
-- Table structure
"""
# dbpass has no effect on SQLite
When I try `wp db export - --dbpass=no_such_pass`
Then the return code should be 0
And STDERR should not contain:
"""
Access denied
"""
@skip-sqlite
Scenario: MySQL defaults are available as appropriate with --defaults flag
Given a WP install
When I try `wp db export --defaults --debug`
Then STDERR should match #Debug \(db\): Running initial shell command: /usr/bin/env (mysqldump|mariadb-dump)#
When I try `wp db export --debug`
Then STDERR should match #Debug \(db\): Running initial shell command: /usr/bin/env (mysqldump|mariadb-dump) --no-defaults#
When I try `wp db export --no-defaults --debug`
Then STDERR should match #Debug \(db\): Running initial shell command: /usr/bin/env (mysqldump|mariadb-dump) --no-defaults#
@skip-sqlite
@skip-windows
Scenario: Export database when PHP exec() is disabled
Given a WP install
When I try `{INVOKE_WP_CLI_WITH_PHP_ARGS--ddisable_functions=exec} db export wp_cli_test.sql --porcelain`
Then the return code should be 0
And STDOUT should contain:
"""
wp_cli_test.sql
"""
And the wp_cli_test.sql file should exist