{"version":"2.1.271","anchor":"plugin-test-framework-validates-and-requires-unique-non-res","canonical_anchor":"plugin-test-framework-validates-and-requires-unique-non-res","heading":"Plugin test framework validates and requires unique, non-reserved plugin names","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/plugin-test-framework-validates-and-requires-unique-non-res","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Plugin test framework validates and requires unique, non-reserved plugin names\n\nPlugin test names must now be unique, lowercase-formatted, and can't reuse the reserved test-hook name\n\n**What**\n\nThe plugin test-declaration function `test(name, { plugins })` now enforces that each test name matches the pattern `^[a-z0-9][a-z0-9-]*$`, rejects duplicate test names, and specifically rejects a plugin reusing the reserved name that the test's own hooks load under.\n\n**Why**\n\nThis catches naming mistakes in plugin tests earlier, before they cause confusing collisions with the reserved name used internally for the test's own hooks.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}