You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: features/requests.feature
+7-1Lines changed: 7 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,7 @@
1
1
Feature: Requests integration with both v1 and v2
2
2
3
+
# This test downgrades to WordPress 5.8, but the SQLite plugin requires 6.0+
4
+
@require-mysql
3
5
Scenario: Composer stack with Requests v1
4
6
Given an empty directory
5
7
And a composer.json file:
@@ -44,6 +46,8 @@ Feature: Requests integration with both v1 and v2
44
46
"""
45
47
And STDERR should be empty
46
48
49
+
# This test downgrades to WordPress 5.8, but the SQLite plugin requires 6.0+
50
+
@require-mysql
47
51
Scenario: Current version with WordPress-bundled Requests v1
48
52
Given a WP installation
49
53
And I run `wp core update --version=5.8 --force`
@@ -99,6 +103,8 @@ Feature: Requests integration with both v1 and v2
99
103
Success: Installed 1 of 1 plugins.
100
104
"""
101
105
106
+
# Uses `wp db create` which is not yet supported in SQLite.
107
+
@require-mysql
102
108
Scenario: Composer stack with Requests v1 pulling wp-cli/wp-cli-bundle
103
109
Given an empty directory
104
110
And a composer.json file:
@@ -150,7 +156,7 @@ Feature: Requests integration with both v1 and v2
150
156
And the {RUN_DIR}/vendor/wp-cli/wp-cli/bundle/rmccue/requests directory should exist
151
157
And the {RUN_DIR}/vendor/rmccue/requests directory should not exist
152
158
153
-
When I run `vendor/bin/wp config create --dbname={DB_NAME} --dbuser={DB_USER} --dbpass={DB_PASSWORD} --dbhost={DB_HOST} --extra-php < extra-config.php`
159
+
When I run `vendor/bin/wp config create --skip-check --dbname={DB_NAME} --dbuser={DB_USER} --dbpass={DB_PASSWORD} --dbhost={DB_HOST} --extra-php < extra-config.php`
0 commit comments