Branch: refs/heads/testing-page-object-boundary Home: https://github.com/xwiki/xwiki-dev-llm Commit: f4c48c7f6da38ea865709b045f97f55e5b98f65e https://github.com/xwiki/xwiki-dev-llm/commit/f4c48c7f6da38ea865709b045f97f5... Author: Vincent Massol <[email protected]> Date: 2026-08-13 (Thu, 13 Aug 2026) Changed paths: M .claude-plugin/marketplace.json M kimi.plugin.json M opencode.jsonc M xwiki/.claude-plugin/plugin.json M xwiki/okf/index.md M xwiki/okf/testing/strategy.md M xwiki/skills/xwiki-test-guidelines/SKILL.md Log Message: ----------- [Misc] Capture the page-object boundary rule for functional tests * okf/testing/strategy.md: new "No getDriver() in a test" durable rule. A functional test drives the UI only through page objects; needing getDriver() (or a raw findElement / By lookup / getCssValue on top of it) in the test class means an API is missing from a page object. Which page object gets it follows from what a page object is: it represents a real XWiki page and the actions that can be performed on that page. So widen or add the method on the page object of the page under test (widening an already-private helper to public counts) rather than creating a page object for a page the test itself creates as a fixture. Test-specific data, such as the wiki content given to that fixture page, stays in the test. Frontmatter summary extended, since that text decides whether the file gets read. * skills/xwiki-test-guidelines: added a one-line functional-test bullet pointing at the rule, since that skill is what gets loaded when writing a test. * okf/index.md: mentioned the rule in the testing/strategy line. * Bumped the plugin version to 1.0.26 (patch, content edit) in all five synced fields. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications