Repository navigation
Tests: use prefixed category slugs to avoid collisions with core - #14
Conversation
WordPress trunk now registers its own "content" category, which takes precedence over the one registered in the tests. Use test-prefixed slugs so the scenarios don't depend on which categories core ships. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Dr555EP8Mq6t1c8nFGQbki
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
WordPress trunk now registers its own
site,user,contentanduncategorizedability categories. The tests infeatures/ability-category.featureregistered acontentcategory too, and core's registration wins, so the label and description checks failed (failing run):The fix renames the categories the tests register to
test-contentandtest-ai, so the scenarios no longer depend on which categories core ships. This matchesfeatures/ability.feature, which already usestest-category. The table assertions are "containing rows", so the extra categories from core don't matter.Generated by Claude Code
Summary by CodeRabbit