From 2cd86699d9904a2ab654c6b601891be082ee8961 Mon Sep 17 00:00:00 2001 From: manuzhang Date: Thu, 18 Jun 2026 23:37:58 +0800 Subject: [PATCH] Docs: Clarify test method naming guidance Generated-by: Codex Co-authored-by: Codex --- AGENTS.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index e6c771d4b482..ada467efa4ce 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -139,7 +139,8 @@ The `api/` module has the strongest stability guarantees — breaking changes ar - Test classes and methods should be package private unless required by inheritance. - Compute expected values, don't hardcode. Tests belong in the module that owns the code. - Write the most direct test for the bug. Parameterized tests for type variations. -- JUnit 5 + AssertJ: `@Test` (no `test` prefix), `assertThat`, `assertThatThrownBy`. +- JUnit 5 + AssertJ: `@Test`, `assertThat`, `assertThatThrownBy`. +- Avoid using `test` prefixes for newly added tests. - `waitUntilAfter` for time-dependent tests. Separate tests over combined. ### REST / OpenAPI Spec