Add docs for contributor guide on writing integration tests for new endpoints

[Chucks1093]

Summary

New contributors adding endpoints often skip integration tests because there is no documented pattern showing how the test setup, database seeding, and request execution work together in this codebase.

Scope

• Document the integration test folder structure and naming convention
• Show how to seed the database with test fixtures for a given test
• Include a minimal worked example of a complete integration test for a GET endpoint
• Note how to run just the integration tests locally

Acceptance Criteria

• Folder structure and naming convention are documented
• Database seeding pattern is explained with an example
• Worked example covers a full integration test from setup to assertion
• Local test run command is documented

ETA: 12 hours

---

Coordinate on Telegram

[wonderfulmarv01]

@wonderfulmarv01 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi! I’m a full-stack developer with a strong blockchain background. I’d love to handle this issue and can deliver a clean, reliable solution. Kindly assign it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @wonderfulmarv01 to this issue.

[olatundefay-prog]

@olatundefay-prog has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Allow me to professionally implement this task with precision and accuracy.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @olatundefay-prog to this issue.

[Tobiloba0]

@Tobiloba0 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer, can I work on this issue please?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Tobiloba0 to this issue.

[anoncon]

@anoncon has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi
I’d like to work on this issue if it’s available. I’m a full-stack Web2 & Web3 developer with solid open-source experience and can start working on it right away.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @anoncon to this issue.

[drips-wave]

Congratulations, @anoncon! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @anoncon: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🦊 GrantFox — @anoncon has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #462)
2. Your PR will be reviewed by the accesslayerorg maintainers

Good luck! Track your progress on GrantFox.