[BE-123] Unit tests for the dispute module

[mftee]

Overview

backend/src/dispute/ has 8 files and 2 entities with no tests. Disputes are the project's stated reason for existing, and they encode who may say what about whose land.

Tasks

• Test dispute creation, including that only eligible parties may raise one against a document.
• Test the status lifecycle and rejection of invalid transitions.
• Test access control: a user must not read disputes they are not party to, except for admins.
• Test evidence attachment and its access rules.
• Test resolution recording and that a resolved dispute cannot be silently reopened or edited.
• Target ≥75% coverage.

Acceptance Criteria

• npm run test -- dispute passes at ≥75% coverage.
• A non-party is proven unable to read or modify a dispute.
• Invalid status transitions are rejected.

Notes for Contributors

Comment below to be assigned.

[Ola-Olamijuwon]

@Ola-Olamijuwon has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi there, i think i can handle this. Thank you.

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

[sadeeq6400]

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

i have thoroughly read the requirements and i am confident that i can handle this issue

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

[drips-wave]

Congratulations, @sadeeq6400! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @sadeeq6400: 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]

🎉 This issue has been marked as completed on GrantFox!

@sadeeq6400's PR #1229 was approved and merged by @mftee.

🏆 @sadeeq6400: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,265 total points). Track your full progress on GrantFox.

👏 Great work, @sadeeq6400! Keep contributing to CodeGirlsInc.

[drips-wave]

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

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