Add Integration Test for the Register -> VerifyEmail flow with a mock DB

[codeZe-us]

User registration combined with email verification forms our primary conversion funnel. We need an integration test spanning these operations against a mocked database to guarantee transactional integrity.

Implementation Guidelines

Key Files: src/server/services/auth.service.spec.ts, src/server/test/db-utils.ts.

• Spin up the transactional DB mock configurations.
• Emulate the signup, database insertion of verification hashes, and the subsequent hash claiming process.

Expectations

What done looks like: An end-to-end service test sequentially creates an account, fetches the verification constraint, validates the email successfully, and finally clears the restriction in the DB mock.

Discord for any questions: codeze_us

[kunal-drall]

@kunal-drall has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I'll take this — core auth funnel coverage.
Will write an integration test covering register → store verification hash → claim hash → verify email → clear restriction, all against a mocked transactional DB. Assert each state transition and verify cleanup.
Experienced with TypeScript service-layer testing and mock DB patterns.

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

[idrisososanwo]

@idrisososanwo has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I’m a good fit for this task because I focus on writing reliable integration tests that validate full authentication flows and ensure transactional integrity.

My approach would be to implement an end-to-end service test that simulates user signup, persists the verification token in a mocked transactional database, and then validates the email verification flow by claiming the token. I’ll ensure the test verifies each step—user creation, token storage, successful verification, and cleanup—while handling edge cases like invalid or reused tokens. This guarantees the registration and verification pipeline works correctly and consistently.

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

[drips-wave]

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

🧑‍💻 @idrisososanwo: 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 marked as completed by a Drips Wave moderator for @idrisososanwo as part of the Stellar Wave Program's 3rd Wave 🥳

Moderator's reason: [Auto-assessed] The contributor implemented a comprehensive integration test suite and a transactional DB mock utility as requested in the issue. The PR (#404) was merged by a maintainer, indicating the solution was accepted, even though the issue remains open.

😎 @idrisososanwo: 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.

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

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.