Skip to content

[Backend] Add unit tests for AllExceptionsFilter #1417

Closed

Description

@BigBen-7

Found in a repository audit of main (b472e6b). The facts below were checked against that commit.

Problem

Backend/src/common/filters/all-exceptions.filter.ts has no spec, although it shapes every error response (statusCode, timestamp, path, message) and hides internal messages in production.

Fix

Test HttpException passthrough (status and message, including array messages), an unknown Error mapped to 500 with the real message in development and Internal server error when NODE_ENV=production, and that path and timestamp are set.

Acceptance criteria

  • all-exceptions.filter.spec.ts exists
  • Known exceptions, unknown exceptions and the production redaction are all asserted

Notes

Scope: Light (about half a day or less). Location: Backend/src/common/filters/.

Activity

  1. ranjeetprabhatedu-dotcom commented on Oct 14, 2026

    @ranjeetprabhatedu-dotcom

    Hello maintainers,

    I reviewed "[Backend] Add unit tests for AllExceptionsFilter" and would like to work on this.

    Technical Implementation Outline:

    1. Audit route handlers, DTO validation schemas, and database transaction boundaries.
    2. Implement resilient controller/service logic with idempotency and typed error handling.
    3. Add comprehensive API unit and integration tests.
    4. Verify database queries and schema integrity remain optimal.

    Please assign this issue to me. I will submit a clean, well-tested, and production-ready PR promptly!

  2. Davedrew77 commented on Oct 16, 2026

    @Davedrew77

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

    I’d like to work on this issue. I’ve gone through the details and I’m confident I can contribute a solid solution.

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

  3. 001marvelqueen-blip commented on Oct 16, 2026

    @001marvelqueen-blip

    @001marvelqueen-blip has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    I would like to work on this issue because I’m up to the task
    Please assign it to me .

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @001marvelqueen-blip to this issue.

  4. VeronicDev commented on Oct 16, 2026

    @VeronicDev

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

    Hello Maintainer, I can fix this please assign.

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

  5. timiturn3r commented on Oct 16, 2026

    @timiturn3r

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

    Hello @maintainer, I’d like to work on this issue. I have experience handling similar tasks and can start immediately. And I will deliver at the shortest possible time.

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

  6. PeterOche commented on Oct 16, 2026

    @PeterOche
    Contributor

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

    Hi, I'd like to work on this issue.

    I've worked on blockchain and Web3 projects, including Stellar and Soroban smart contracts, alongside traditional full-stack web development. I'm comfortable moving between frontend, backend, and on-chain work.

    I've gone through the details of this issue and I'm confident I can deliver a clean, well-tested solution that fits the codebase.

    Looking forward to contributing — please assign this issue to me.

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

  7. drips-wave commented on Oct 16, 2026

    @drips-wave

    Congratulations, @PeterOche! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

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

  8. grantfox-oss commented on Oct 17, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @PeterOche's PR #1519 was approved and merged by @BigBen-7.

    🏆 @PeterOche: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (742 total points). Track your full progress on GrantFox.

    👏 Great work, @PeterOche! Keep contributing to PinSpace-Org.

  9. drips-wave commented on Oct 17, 2026

    @drips-wave

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

    😎 @PeterOche: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions