Fix ambiguity by improving regex

[swissspidy]

Follow-up to #282

[gemini-code-assist]

Summary of Changes

Hello @swissspidy, I'm Gemini Code Assist¹! 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 precision of the Behat step definition for 'Given a WP installation' by modifying its regular expression to ensure that any specified version parameter starts with a digit. This change aims to prevent potential ambiguities in test scenarios. To support and validate this improvement, new test cases have been added for both single-site and multisite WordPress installations, demonstrating the correct usage and functionality of the updated step.

Highlights

• Regex Improvement: The regular expression for the Given a WP installation Behat step has been refined to specifically match version numbers that begin with a digit, reducing ambiguity.
• New Test Scenarios: New Behat scenarios have been introduced to validate the improved Given a WP installation step, including tests for a specific WordPress version (6.8) and a WordPress multisite installation.

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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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]

Code Review

This pull request aims to fix an ambiguity in a Behat step definition regex. The change correctly prevents Given a WP multisite installation from being matched as a versioned WP installation. The added Behat scenarios are good for testing this fix and the related step for multisite installation. However, the new regex for versioned installation seems to have a minor flaw: it doesn't allow for single-digit versions (e.g., 6). I've suggested a small change to the regex to support this.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!