next.js

b33ffd20 - AGENTS.md: prefer e2e/execution tests over implementation-mapped unit tests (#100451)

AGENTS.md: prefer e2e/execution tests over implementation-mapped unit tests (#100451) ### What? Adds two bullets to the "Writing Tests" section of `AGENTS.md`: - For Next.js features, prefer e2e tests (`test/e2e/`, `test/development/`, `test/production/`). For Turbopack features, prefer execution tests (`turbopack/crates/turbopack-tests/tests/execution/`). - Avoid unit tests that map directly to the implementation; complicated algorithms are the exception. Agents may write unit tests temporarily to check their work, but should not commit them or add them to the PR unless they are necessary. ### Why? Agents often add unit tests that mirror the implementation. These tests add maintenance cost and catch few real regressions. Integration-level tests cover behavior through the real entry points. ### How? The guidance goes into the existing "Test writing expectations" list, where agents already read test conventions. It names concrete directories so it is easy to act on. ### Verification - `prettier --check AGENTS.md` passes. <!-- NEXT_JS_LLM --> <!-- fleet 49585d67-9c38-49d9-bde0-810ba197f96e --> Co-authored-by: vercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com> Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>