Test conventions for a parks monorepo must apply to test files scattered across many directories. What path rule helps?
Select an answer to reveal the explanation.
Short Explanation
Tests hide in pockets all over a monorepo—like hydrants on every block. A recursive test-file glob in the rules frontmatter covers that whole tree instead of one lonely folder.
Full Explanation
Test conventions for a parks monorepo must apply to test files scattered across many directories. A recursive test-file glob in the rules frontmatter spanning the directory tree is the path rule that covers that layout without hard-coding one folder.
Recursive globs work because monorepos commonly place tests beside packages, under __tests__, or in mirrored trees. A frontmatter path such as a recursive **/test or equivalent test-file pattern activates the same parks testing conventions—naming, fixtures, assertion style—wherever matching files are edited. One versioned rules file then serves the whole civic monorepo instead of per-folder copies.
A single hardcoded absolute path to one forgotten __tests__ folder fails when tests live elsewhere; new packages escape the rule. Omitting the path field so test rules never load for any file fails by disabling the conditional activation the team needs. User-level memory only fails because teammates cannot receive those conventions through version control; parks quality standards would depend on one person's local memory rather than shared project rules.
Exam caveat: recursive globs address cross-directory coverage; absolute single paths and missing path fields are opposite failure modes (too narrow versus never active). Operational check: edit test files in two distant parks packages and confirm the same test conventions load for both; edit a non-test source file and confirm they do not.