Harden test involving sqlite db name by swissspidy · Pull Request #316 · wp-cli/db-command · GitHub
Skip to content

Harden test involving sqlite db name#316

Merged
swissspidy merged 3 commits into
mainfrom
fix-test
Mar 24, 2026
Merged

Harden test involving sqlite db name#316
swissspidy merged 3 commits into
mainfrom
fix-test

Conversation

@swissspidy

Copy link
Copy Markdown
Member

The filename was changed in the latest sqlite plugin version. Accommodate for both

The filename was changed in the latest sqlite plugin version. Accommodate for both
@swissspidy swissspidy requested a review from a team as a code owner March 24, 2026 11:57
Copilot AI review requested due to automatic review settings March 24, 2026 11:57
@github-actions

Copy link
Copy Markdown
Contributor

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the robustness of existing tests related to database size reporting for SQLite. By introducing more flexible matching patterns, the tests can now correctly validate output regardless of minor variations in the SQLite database filename, preventing potential test failures due to external plugin updates.

Highlights

  • Test Hardening for SQLite DB Name: Updated db-size.feature tests to use regular expressions instead of exact string matching for the SQLite database name. This change accommodates variations in the SQLite database filename, specifically allowing for both .ht.sqlite and .ht.sqlite.php in the output.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates Behat tests to accommodate a potential change in the SQLite database filename by using regular expressions. The changes are a good step towards making the tests more flexible. My review focuses on improving the new regular expressions to be more precise and to maintain the same level of strictness as the original tests, which helps prevent future regressions.

Comment thread features/db-size.feature Outdated
Comment thread features/db-size.feature Outdated

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the SQLite-specific wp db size Behat scenario to tolerate a database filename change introduced by a newer SQLite plugin version, ensuring the acceptance test remains compatible across versions.

Changes:

  • Replace strict string-literal assertions with regex matches to accept both .ht.sqlite and .ht.sqlite.php in CSV output.
  • Replace strict string-literal assertions with regex matches to accept both .ht.sqlite and .ht.sqlite.php in JSON output.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread features/db-size.feature Outdated
Comment thread features/db-size.feature Outdated
@codecov

codecov Bot commented Mar 24, 2026

Copy link
Copy Markdown

swissspidy and others added 2 commits March 24, 2026 13:06
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@swissspidy swissspidy added this to the 2.1.6 milestone Mar 24, 2026
@swissspidy swissspidy merged commit 52d4aff into main Mar 24, 2026
60 checks passed
@swissspidy swissspidy deleted the fix-test branch March 24, 2026 12:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants