Skip to content

Docs: Clarify test method naming guidance #16866

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kevinjqliu merged 1 commit into from
Jun 21, 2026
Merged

Docs: Clarify test method naming guidance #16866

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down