{"version":"2.1.292","anchor":"plugin-test-harness-reports-failures-static-scan-tightened","canonical_anchor":"plugin-test-harness-reports-failures-static-scan-tightened","heading":"Plugin tests report failures, and the code scan checks more","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/plugin-test-harness-reports-failures-static-scan-tightened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Plugin tests report failures, and the code scan checks more\n\nClosing a plugin test now reports whether it failed, and the plugin code scan catches redeclared names and the plugin's own commands\n\n**What**\n\nWhen a plugin test finishes, Claude Code now returns what the plugin said together with whether the test failed. It used to return plain text only.\n\nThe scan of a plugin's code checks two more things:\n\n- A name that is declared again over a function the plugin was handed.\n\n- When `command.run` is used to run the plugin's own commands.\n\n**Why**\n\nPlugin authors get stricter checking of their code and clearer failure reports from tests.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}