Skip to content

Document test package convention #85

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
BenCodez merged 1 commit into from
Oct 16, 2026
Merged

Document test package convention #85

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
6 changes: 6 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,12 @@ mvn -B -f GraveStonesPlus/pom.xml package

Confirm current CI and POM settings. Verify the fresh shaded JAR, actual test discovery, and `git diff --check`. Do not run deployment or developer-copy profiles for routine validation.

## Test package organization

Put Java test classes and reusable test helpers under `com.bencodez.gravestonesplus.tests`, using subpackages for related areas. Match the directories below `src/test/java` to the declared package. Keep new and moved tests in this namespace and update imports, resource lookups, reflection references, and build selectors when relocating them.

Preserve every existing test assertion and test discovery. Use a narrow test-only access helper when testing package-private implementation details; do not widen production APIs merely to move a test. Before finishing, verify the package declarations and run the required test/package build so the reorganization cannot silently drop coverage.

## Architecture and data ownership

- `GraveStonesPlus` owns plugin lifecycle, listener registration, commands, and storage initialization.
Expand Down
Loading