[xwiki/xwiki-dev-llm] 57d4c0: [Misc] Cover granting Programming Rights to a func...
Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-dev-llm Commit: 57d4c005c8cbc04e971c3351e47d460caa47be54 https://github.com/xwiki/xwiki-dev-llm/commit/57d4c005c8cbc04e971c3351e47d46... Author: Vincent Massol <[email protected]> Date: 2026-09-17 (Thu, 17 Sep 2026) Changed paths: M xwiki/okf/testing/strategy.md Log Message: ----------- [Misc] Cover granting Programming Rights to a functional test's own content * The PRChecker bullet only explained how to READ a `PRChecker: Block programming right` log line, so nothing in the OKF answered the authoring question: my test creates content that needs the right, how do I grant it? Add that direction to the same bullet, keyed on the symptoms actually seen (the rendered "You need Programming Rights to execute the script macro [groovy]" error), with the concrete `@UITest(properties = {"xwikiPropertiesAdditionalProperties=test.prchecker.excludePattern=..."})` form, the fact that the exclusion really grants the right rather than only silencing the log, and the whole-reference match trap. * Tighten the probe clause that the addition made longer. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Commit: 9aadf69ee9a6e8d64e9653f8ae5ea079f6b9e753 https://github.com/xwiki/xwiki-dev-llm/commit/9aadf69ee9a6e8d64e9653f8ae5ea0... Author: Vincent Massol <[email protected]> Date: 2026-09-17 (Thu, 17 Sep 2026) Changed paths: M xwiki/instructions/xwiki-org.md M xwiki/skills/xwiki-test-guidelines/SKILL.md Log Message: ----------- [Misc] Make the test-guidelines skill claim the act of writing a test * The skill's description described its contents instead of naming its trigger, and the always-on instruction called it "deeper testing guidance", so a small test change (one added @Test method in an existing class) routed to nothing and the rules were never loaded. Turn the description into a trigger that names the action, covers functional @UITest tests, and closes the "it's only one method / the class already exists / this one is simple" escape, and make the always-on line an obligation rather than an invitation. * Drop the *Test.java / *IT.java naming rule from the always-on file: it is stated verbatim in okf/testing/strategy.md, which is its home, and the budget is better spent on the routing rule. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Commit: 6ffdb5b4a73b1164b9c16c036e36277e0b74d687 https://github.com/xwiki/xwiki-dev-llm/commit/6ffdb5b4a73b1164b9c16c036e3627... Author: Vincent Massol <[email protected]> Date: 2026-09-17 (Thu, 17 Sep 2026) Changed paths: M xwiki/instructions/xwiki-org.md M xwiki/okf/testing/strategy.md M xwiki/skills/xwiki-test-guidelines/SKILL.md Log Message: ----------- Merge pull request #147 from xwiki/okf-prchecker-grant [Misc] Route test authoring to the test rules, and cover granting Programming Rights to a test's own content Compare: https://github.com/xwiki/xwiki-dev-llm/compare/5492f4e5a923...6ffdb5b4a73b To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications
participants (1)
-
XWiki Notifications