{"version":"2.1.290","anchor":"claude-plugin-test-rollout-flag-hold-and-file-form","canonical_anchor":"claude-plugin-test-rollout-flag-hold-and-file-form","heading":"claude plugin test now waits for its rollout setting to be saved","tier":"use","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/claude-plugin-test-rollout-flag-hold-and-file-form","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### `claude plugin test` now waits for its rollout setting to be saved\n\n`claude plugin test` now waits until a rollout setting is saved for test files to read, and reports when that fails\n\n**Unclear.** Which rollout setting this is has not been identified.\n\n**What**\n\n`claude plugin test` now tells apart the `--file` form, a plain run, and other forms of the command. Before running, it waits for a rollout setting, a switch that turns a feature on or off, to be saved where the test files can read it. If that fails, it says \"the rollout switch was fetched, but its value could not be saved for the test files to read\".\n\n**Why**\n\nTests should see the same setting the plugin would see. This mainly concerns plugin authors testing hooks modules.\n\n- Area: Plugins\n- Names: `claude plugin test`, `--file`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}