Conversation
|
Hello! 👋 Thanks for opening this pull request! Please check out our contributing guidelines. We appreciate you taking the initiative to contribute to this project. Contributing isn't limited to just code. We encourage you to contribute in the way that best fits your abilities, by writing tutorials, giving a demo at your local meetup, helping other users with their support questions, or revising our documentation. Here are some useful Composer commands to get you started:
To run a single Behat test, you can use the following command: # Run all tests in a single file
composer behat features/some-feature.feature
# Run only a specific scenario (where 123 is the line number of the "Scenario:" title)
composer behat features/some-feature.feature:123You can find a list of all available Behat steps in our handbook. |
There was a problem hiding this comment.
Code Review
This pull request refactors several Behat scenarios in features/post.feature to use external HTML files for post content instead of passing the content directly via the --post_content flag in the wp post create command. This change improves the readability and structure of the test scenarios. I have no feedback to provide.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
There was a problem hiding this comment.
Pull request overview
This PR updates Behat tests for the post command to be more Windows-compatible by avoiding inline HTML passed via --post_content (which can break due to shell redirection parsing of </> on Windows).
Changes:
- Write post content into temporary
.htmlfiles within the scenarios. - Create posts by passing the content file as the positional argument to
wp post createinstead of using--post_content=....
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
No description provided.