Add helper for building test requests with all required auth headers

[Chucks1093]

Summary
Integration tests that hit protected routes must manually construct auth headers each time, leading to repetitive setup code. A test helper that builds a complete authenticated request with the correct headers reduces boilerplate and keeps test setup consistent.

Scope

• add a test helper that constructs an HTTP request with all required auth headers pre-populated
• accept optional overrides for individual header values
• apply the helper in at least two existing integration tests for protected routes

Acceptance Criteria

• the helper produces a valid authenticated request for protected routes
• individual headers can be overridden for negative test cases
• at least two existing protected route tests are updated to use the helper

Contributor coordination: if you pick this up, reach out in Telegram for updates or clarification: https://t.me/accesslayerorg

[NnamdiCyber]

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

I’d like to work on this issue because reducing repetitive test setup improves maintainability, readability, and consistency across integration test suites. I have experience building reusable testing utilities for authenticated APIs, including request factories, fixture helpers, and shared test infrastructure in backend applications. For this task, I would create a helper that generates authenticated HTTP requests with all required authorization headers preconfigured, support optional header overrides for edge-case testing, and refactor at least two existing integration tests to use the new helper. This approach will reduce boilerplate, make tests easier to maintain, and ensure authentication setup remains consistent across the codebase.

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

[Opeyemi01-del]

@Opeyemi01-del has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would love to work on this issue

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

[edehvictor]

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

Can I work on this

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

[drips-wave]

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

🧑‍💻 @edehvictor: 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 🌊

[drips-wave]

This issue has been completed by @edehvictor as part of the Stellar Wave Program's 5th Wave 🥳

😎 @edehvictor: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.