Add backend integration tests for auth, invites, friends, and messages

[chthonn]

Difficulty: Advanced

Context

PiperChat has several important backend flows but no test harness yet. A focused integration test setup would make future GSSoC contributions safer and help maintainers review PRs faster.

Expected work

• Add a backend test runner suitable for an Express + Mongoose ESM project.
• Add test setup for isolated database usage.
• Cover auth signup/signin behavior at a high level.
• Cover invite acceptance behavior.
• Cover friend request accept/ignore behavior.
• Cover basic channel or direct message send/load behavior.
• Document how maintainers and contributors should run tests.

Acceptance criteria

• npm test or an equivalent backend test command exists in server/package.json.
• Tests run without requiring production credentials.
• Tests do not depend on the maintainer's real MongoDB Atlas data.
• At least four meaningful backend flows are covered.
• README or backend docs mention the test command.

Suggested files

• server/package.json
• server/routes/auth.js
• server/routes/invites.js
• server/routes/friends.js
• server/routes/chat.js
• server/routes/directMessages.js
• README.md

[JITESH-KUMAR05]

Hi @0rigin-c0de
I would like to work on this issue. Can you assign it to me?

[ronak-ravtode]

Hi @0rigin-c0de , i would like to contritube in this issue. Can you assign me?

[MdTowfikomer]

Hi @0rigin-c0de, I would like to work on this issue. Could you please assign it to me? I am ready to start working on the backend integration tests as described.

[DevalGarg129]

Hiii @0rigin-c0de would love to work on this issue, could you please assign this to me

[amritbej]

Hello @0rigin-c0de,

I would like to work on this issue. I can set up a proper backend integration testing environment for the Express + Mongoose ESM architecture and add isolated database-based tests for the major backend flows.

My approach will include:

• Setting up a backend test runner and reusable test utilities

• Configuring isolated MongoDB test instances without relying on production/Atlas data

• Adding integration tests for:

  • Auth signup/signin flows
  • Invite acceptance flow
  • Friend request accept/ignore behavior
  • Channel/direct message send and retrieval flows

• Adding a dedicated npm test workflow in server/package.json

• Documenting setup and test execution steps for contributors and maintainers

Please assign this issue to me. Thank you!

[Rachel-Mathew25]

Hi! I spent some time exploring the backend structure and issue list, and this particular issue genuinely stood out to me because it improves something that becomes extremely important as projects grow — confidence and reliability during future development.

One thing I’ve started understanding through open-source contributions is how valuable good test infrastructure is, especially in collaborative projects where multiple contributors are actively changing backend behavior. Having integration coverage for authentication, invites, friend flows, and messaging would make future contributions much safer and much easier to review/debug.

I’m especially interested in this issue because it combines several things I’ve been wanting to improve at:

• backend architecture understanding
• Express/Mongoose workflow familiarity
• testing practices for real-world applications
• API reliability and maintainability

I recently completed and merged a focused open-source contribution where I worked through rebasing, conflict resolution, regression testing, maintainer review iterations, and PR cleanup, so I’m comfortable following contribution workflows carefully and keeping changes well-scoped/documented.

Before implementing anything, I’d first spend time understanding the current backend flow and existing route structure properly so the testing setup integrates cleanly with the project instead of feeling bolted on. I’d also ensure the tests stay isolated from production credentials/data and document the setup clearly for future contributors.

If the maintainers feel this would be a good fit, I’d genuinely love the opportunity to work on it and contribute carefully to the backend quality of the project under GSSoC.

Thank you!

[jahnavi-karanwal]

can u assign me this under gssoc'26

[shivangii123]

Hii @0rigin-c0de
I would love to work on this issue, could you please assign this to me