Branch: refs/heads/it-scenario-fixture-rule Home: https://github.com/xwiki/xwiki-dev-llm Commit: 63d3343a254b846586abcdc75652f160c676698a https://github.com/xwiki/xwiki-dev-llm/commit/63d3343a254b846586abcdc75652f1... Author: Vincent Massol <[email protected]> Date: 2026-08-27 (Thu, 27 Aug 2026) Changed paths: M xwiki/okf/index.md M xwiki/okf/testing/strategy.md M xwiki/skills/xwiki-test-guidelines/SKILL.md Log Message: ----------- [Misc] Pivot the scenario rule from method count to duplicate fixtures * Restated the rule as "no two @Test methods build the same fixture" instead of "as few methods as possible, one if you can". The defect the rule targets is a second method paying for a fixture an existing one already builds, not method count in itself, and the previous wording read as a push towards a single method however long it grew. * Added the counterweight: a method nobody can follow end to end, or one whose failure no longer says which behaviour broke, has been merged too far. A distinct fixture justifies a distinct method, a merely distinct assertion does not. * Mirrored the change in the xwiki-test-guidelines bullet, the strategy summary and the OKF map. 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