Repository navigation
Use {PLUGIN_DIR} and {THEME_DIR} in tests - #564
Conversation
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Remove path lookup steps features/plugin-update.feature, features/plugin.feature, features/theme-update.feature |
Removed the wp plugin path or wp theme path commands and their variable assignments. The theme update scenario retains the empty-directory step that uses THEME_DIR. |
Estimated code review effort: 1 (Trivial) | ~5 minutes
Change: Other
Suggested reviewers: brianhenryie
Merge Risk: 
Minimal · up to c0836
-
The scenarios can use the built-in plugin and theme paths without the removed lookup steps. No actionable merge risk remains.
Pre-merge checks: 
4
Finishing Touches
-
Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fe264be to
c08364e
Compare
{PLUGIN_DIR} and {THEME_DIR} in tests
Switches the feature files to the built-in
{PLUGIN_DIR}and{THEME_DIR}variables from wp-cli/wp-cli-tests#397, and requireswp-cli/wp-cli-tests^5.4.0.Measured on this test suite: Behat time +4.5% (886.0 → 925.7 job minutes, summed over the matrix). Details in wp-cli/wp-cli-tests#397.
Summary by CodeRabbit