Unclear Which rollout setting this is has not been identified.
What
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".
Why
Tests should see the same setting the plugin would see. This mainly concerns plugin authors testing hooks modules.
Names in the bundleclaude plugin test--file
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up claude plugin test, on Claude Code changelog.
* Changed `claude plugin test`: a failed `expect` inside a hook the test registered, or a stub answer the engine refuses, now fails the test instead of passing silentlychangelog see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Which rollout setting this is has not been identified.
Anthropic's documentation agrees
Anthropic's documentation has since written up claude plugin test, on Claude Code changelog.
Anthropic's release notes agree
Fixed claude plugin test refusing to run after an upgrade because of an out-of-date saved setting