Skip to content

Make Behat scenarios SQLite-compatible #138

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
swissspidy merged 4 commits into from
Apr 17, 2026
Merged

Make Behat scenarios SQLite-compatible #138

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
65f6886
Make Behat scenarios SQLite-compatible
abhi3315 Apr 13, 2026
0c60ce5
Combine wp eval calls in split-dump scenario
abhi3315 Apr 13, 2026
4a7f66f
Keep split-dump scenario MySQL-only
abhi3315 Apr 17, 2026
ec97c30
Remove @require-mysql from scenarios that work on SQLite
abhi3315 Apr 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Remove @require-mysql from scenarios that work on SQLite 
The split-dump scenario remains MySQL-only because it tests MySQL's
redo log size limit behavior, which doesn't apply to SQLite.
  • Loading branch information
@abhi3315
abhi3315 committed Apr 17, 2026
commit ec97c3011e728f89aeb98e8685a67a09a16f85de
38 changes: 19 additions & 19 deletions features/export.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ Feature: Export content.
"""
And the return code should be 1

@require-wp-5.2 @require-mysql
@require-wp-5.2
Scenario: Export with post_type and post_status argument
Given a WP install

Expand Down Expand Up @@ -79,7 +79,7 @@ Feature: Export content.
10
"""

@require-wp-5.2 @require-mysql
@require-wp-5.2
Scenario: Export a comma-separated list of post types
Given a WP install

Expand Down Expand Up @@ -132,7 +132,7 @@ Feature: Export content.
10
"""

@require-wp-5.2 @require-mysql
@require-wp-5.2
Scenario: Export only one post
Given a WP install

Expand Down Expand Up @@ -203,7 +203,7 @@ Feature: Export content.
2
"""

@require-wp-5.2 @require-mysql
@require-wp-5.2
Scenario: Export multiple posts, separated by spaces
Given a WP install

Expand Down Expand Up @@ -236,7 +236,7 @@ Feature: Export content.
2
"""

@require-wp-5.2 @require-mysql
@require-wp-5.2
Scenario: Export multiple posts, separated by comma
Given a WP install

Expand Down Expand Up @@ -269,7 +269,7 @@ Feature: Export content.
2
"""

@require-wp-5.2 @require-mysql
@require-wp-5.2
Scenario: Export posts within a given date range
Given a WP install

Expand Down Expand Up @@ -310,7 +310,7 @@ Feature: Export content.
10
"""

@require-wp-5.2 @require-mysql
@require-wp-5.2
Scenario: Export posts from a given category
Given a WP install
And I run `wp site empty --yes`
Expand Down Expand Up @@ -392,7 +392,7 @@ Feature: Export content.
Apple Post
"""

@require-wp-5.2 @require-mysql
@require-wp-5.2
Scenario: Export posts from a given author
Given a WP install
And I run `wp site empty --yes`
Expand Down Expand Up @@ -475,7 +475,7 @@ Feature: Export content.
john.doe@example.com
"""

@require-wp-5.2 @require-mysql
@require-wp-5.2
Scenario: Export posts should include user information
Given a WP install
And I run `wp plugin install wordpress-importer --activate`
Expand Down Expand Up @@ -545,7 +545,7 @@ Feature: Export content.
5
"""

@require-wp-5.2 @require-mysql
@require-wp-5.2
Scenario: Exclude a specific post type from export
Given a WP install
And I run `wp site empty --yes`
Expand Down Expand Up @@ -608,7 +608,7 @@ Feature: Export content.
0
"""

@require-mysql

Scenario: Export posts using --max_num_posts
Given a WP install
And I run `wp site empty --yes`
Expand Down Expand Up @@ -666,7 +666,7 @@ Feature: Export content.
thisisaverylongsitenamethatexceedsfiftycharactersandshouldbetruncated
"""

@require-wp-5.2 @require-mysql
@require-wp-5.2
Scenario: Export a site and skip the comments
Given a WP install
And I run `wp comment generate --post_id=1 --count=2`
Expand Down Expand Up @@ -847,7 +847,7 @@ Feature: Export content.
"""
And STDERR should be empty

@require-wp-5.2 @require-mysql
@require-wp-5.2
Scenario: Export a site to stdout
Given a WP install
And I run `wp comment generate --post_id=1 --count=1`
Expand Down Expand Up @@ -901,7 +901,7 @@ Feature: Export content.
"""
And the return code should be 1

@require-wp-5.2 @require-mysql
@require-wp-5.2
Scenario: Export individual post with attachments
Given a WP install
And I run `wp plugin install wordpress-importer --activate`
Expand Down Expand Up @@ -993,7 +993,7 @@ Feature: Export content.
white-150-square.jpg";s:
"""

@require-wp-5.2 @require-mysql
@require-wp-5.2
Scenario: Export categories, tags and terms
Given a WP install
And a wp-content/mu-plugins/register-region-taxonomy.php file:
Expand Down Expand Up @@ -1158,7 +1158,7 @@ Feature: Export content.
Europe
"""

@require-wp-5.2 @require-mysql
@require-wp-5.2
Scenario: Export posts should not include oembed_cache posts user information
Given a WP install
And I run `wp plugin install wordpress-importer --activate`
Expand Down Expand Up @@ -1190,7 +1190,7 @@ Feature: Export content.
Test User
"""

@require-wp-5.2 @require-mysql
@require-wp-5.2
Scenario: Allow export to proceed when orphaned terms are found
Given a WP install
And I run `wp term create category orphan --parent=1`
Expand Down Expand Up @@ -1245,7 +1245,7 @@ Feature: Export content.
0
"""

@require-mysql

Scenario: Throw exception when orphaned terms are found
Given a WP install
And I run `wp term create category orphan --parent=1`
Expand Down Expand Up @@ -1285,7 +1285,7 @@ Feature: Export content.
<wp:tag>
"""

@require-wp-5.2 @require-mysql
@require-wp-5.2
Scenario: Export posts with future status
Given a WP install
And I run `wp plugin install wordpress-importer --activate`
Expand Down