{"version":"2.1.285","anchor":"new-plugin-test-dir-subcommand","canonical_anchor":"new-plugin-test-dir-subcommand","heading":"New plugin test command runs a mod's tests","tier":"soon","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/new-plugin-test-dir-subcommand","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### New `plugin test` command runs a mod's tests\n\nA new `plugin test [dir]` command runs a mod's tests, marked as early access\n\n**Unclear.** It is not clear how the hooksModules early access is turned on.\n\n**What**\n\nThe plugin command gains a `test` subcommand, written as `plugin test [dir]`, where `[dir]` is an optional folder. It is described as \"Run a mod's tests\". It is marked as early access under `hooksModules`, so it is not available to everyone by default.\n\n**Why**\n\nPeople who write plugins (add-on packages for Claude Code) get a command for running their own tests.\n\n- Area: Plugins\n- Names: `hooksModules`\n- Tier: Nothing to try yet\n- Useful: 5\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}