Branch: refs/heads/misc-page-object-boundary-routing Home: https://github.com/xwiki/xwiki-dev-llm Commit: de7da456ff94b728598574c6d7183bf2f41b87da https://github.com/xwiki/xwiki-dev-llm/commit/de7da456ff94b728598574c6d7183b... Author: Vincent Massol <[email protected]> Date: 2026-09-07 (Mon, 07 Sep 2026) Changed paths: M xwiki/okf/testing/strategy.md M xwiki/skills/xwiki-fix-flickering-docker-test/SKILL.md Log Message: ----------- [Misc] Route the flickering-test skill to the rules its steps depend on * Two rules that the OKF already carries failed to reach a session fixing a flickering IT, because xwiki-fix-flickering-docker-test reads as a self-contained checklist and referenced neither: the page-object boundary (okf/testing/strategy.md) and the JDK-on-PATH prerequisite (okf/testing/running-docker-its.md). Point at both up front, and repeat the page-object constraint on the step that authors the fix, where it applies. * State in the page-object boundary rule that getDriver() calls already in a test class are not a precedent. Most classes predate the rule, so matching the surrounding code is what breaks it, and the rule was silent about that. * Fix the step 7 command, which omitted compiler:testCompile and so silently re-ran the previously compiled test, and note that start_xwiki.sh must run from its own directory. * Note that Develocity holds no data for xwiki-contrib repos, and that the archived Jenkins video, run through scene detection, localises a failure to the frame. 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